Security & data
Your work is org-scoped
Section titled “Your work is org-scoped”Projects belong to an organization, and access is gated by org membership. People outside your org can’t see your projects, and roles control who can change billing and members.
Credentials never touch your codebase in the clear
Section titled “Credentials never touch your codebase in the clear”The CLI authenticates to CubeDot with a project token written into .mcp.json during cubedot init. You never paste API keys into your coding agent, it signs in through the CLI. Keep your .mcp.json and project token out of public repos.
Payments
Section titled “Payments”Payments run through hosted checkout and a merchant-of-record flow, card data never touches CubeDot’s servers. Manage cards and invoices in the billing portal.
Isolation
Section titled “Isolation”Staging and production are fully separate environments with separate data. Testing on one never touches the other.
Data you can export
Section titled “Data you can export”Your generated documents live in your repo under .cubedot/docs/ once connected, so the core of your blueprint is always in your own hands.