Managed hosting is a Preview. There are no published prices; terms, region and retention are agreed with you before activation. Request hosting to ask for an instance.
What you get
Your organization gets its own instance: an application, a PostgreSQL 18 database, document storage, secrets, backups and a domain such as https://client.analyticalledger.com. Your entities and books live inside that one database.
We run it. The operator manages updates, backups, monitoring and infrastructure. Your owner manages users, access and accounting decisions.
The software is the same Fair Source software you can run yourself. What you pay for, if you choose hosting, is the operation and support.
How isolation works
There is no shared tenant database. Every client has a separate app, database, document store, secrets and backups. Images can be shared between clients; state and secrets are never shared.
The strongest isolation is one small Linux virtual machine per client. A stack per client on a shared machine costs less but shares the kernel, the Docker daemon, root administrators, disk and resource pool, and the operator should agree to that risk with you explicitly.
The stack is Docker Compose with Caddy terminating TLS. Only Caddy publishes ports 80 and 443. PostgreSQL is reachable only on the stack's internal network, and the app runs as a non-root, read-only image.
Entities inside your database are accounting scopes for your books, not separate security domains. See Architecture overview.
First owner setup
- The operator creates your instance and gives your owner a one-time setup link through a private channel.
- Your owner opens the link and creates a strong password.
- Onboarding follows: the first entity, a template chart of accounts and open periods. First-run setup shows each step.
- After setup, the link stops working.
Do not forward the setup link, and do not paste it into an AI chat. If you lose access later, ask your operator about recovery. Do not share passwords.
Your keys and your agents
Enter your own API keys in Settings for the integrations you use, such as Anthropic, OpenAI or a bank connection. The instance encrypts stored credentials with its own credentials key, and your operator never needs your values in email or chat. A matching server environment credential takes precedence, so ask the operator if a saved setting seems ineffective. Bring your own API keys has the detail. Preview
You can connect your own AI agents to your instance over HTTPS, including from your phone. Sign in and authorize each connection with your own account; grants follow the app's roles, scopes and approval controls. Never share an owner's session, and revoke agent access you no longer use. Connect your agent and Your agent in your pocket cover the steps.
Ask your operator to demonstrate an authorized read and an unauthorized rejection when they hand the instance over.
Taking your data with you
You can request your full SQL database and your documents when you leave. Agree secure delivery and retention with your operator in advance.
They should provide:
- checksum verification for what they send
- the application release your data belongs to
- restore guidance
- the credentials encryption key, transferred separately, which saved integrations need
Confirm that you received a copy and can restore it before you authorize deletion of the hosted instance.