Axiomatic

Architecture

How Axiomatic cloud is structured — security, data isolation, and billing at a high level.

One application

Axiomatic is delivered as a single cloud application: the web UI and REST API (/api/...) run together. Modules such as Ledger, CRM, Invoicing, and Cortex are part of the same product — not separate servers you integrate yourself.

You sign in once, pick an entity (company, fund, or personal workspace), and work in that context. Most actions apply to the active entity; some settings apply to the whole workspace.

Your data

Each customer workspace has its own isolated database for operational and financial data (entities, ledger, CRM, documents, and so on). Login accounts, billing balance, and workspace membership are stored separately so access and billing stay consistent when you switch entities.

Sensitive fields (bank details, tax IDs, and similar) are encrypted before they are stored. See Encryption for what that means for you.

Authentication and API access

  • Sign-in — Passkeys and other credentials tied to your user account.
  • API keys — For automation, use Authorization: Bearer with a key created under Settings → API keys. Keys are scoped to one entity and optional module permissions.

Billing (cloud)

Each workspace maintains a prepaid USD credit balance. Billable usage debits that balance; when it is empty, writes pause until you add credits. Workspaces with multiple entities share one balance. Details and rates are in Billing and credits.

Reliability

When something cannot be completed safely, the product returns an error instead of silently doing the wrong thing — so you can fix the issue before data gets out of sync.

See also

On this page