Your data has
a defined boundary.
The public demo and a private Costex deployment are different environments. Here is what each does, and what it does not do.
The public demo
Every calculation uses fictional billing and inventory fixtures. Each request starts an isolated in-memory workspace, replays the current visitor's bounded sample changes and disposes of that workspace. There is no shared customer database or cloud connection.
Sample assignments remain in browser local storage. Downloaded sample exports are retained in this browser's IndexedDB, up to the displayed demo limits. Reset removes that browser's demo changes and history. Avoid entering personal, customer or confidential information into the sample forms.
A customer-hosted workspace
The application is designed to read an explicitly configured normalized billing source and keep assignment/export state in operational storage. Cloud identities, authentication, deployment region and retention are deployment responsibilities. Do not expose a private writable workspace by disabling its authentication.
AI and machine access
The private API and MCP gateway use a separate machine token and expose named read tools. The optional private assistant sends selected cost context to the administrator's configured model provider only when a user chooses to send. The public sample assistant does not use a model provider or accept credentials. See connection options and limits.
Findings are not execution
Resource scans identify review candidates. Decisions and change proposals are records, not proof that a resource was deleted or a merge request was submitted. Live remediation requires a separately implemented and authorized integration.
Current limits
This development preview does not claim a security certification, compliance accreditation, customer SLA or independently certified provider integration. Its public API accepts only a narrow set of bounded synthetic operations. It has no real billing importer, provider credentials or resource execution endpoint.
Report a concern
Use the author's existing contact route on the personal portfolio. Share a minimal reproduction rather than passwords, account keys or billing exports.