Your data stays yours
Your ledger, bank and payroll stay yours.
A trial balance, a bank statement and a payroll register are the most private records a company keeps. Orion keeps them in a database that belongs to your company alone, records every change and every sign-off, and never hands a key to a model.
- The ledgerChart of accounts, trial balance, journals
- Bank linesEvery account, as the bank sent them
- PayrollBy department, for the roles you allow
- Sign-offsWho signed, when, and what they saw
- Login opens
- This database only
- Audit
- Append-only
- Keys
- Never shown to a model
What stays private
The records a close is made of.
The ledger
Chart of accounts, trial balance, journals and entities.
Bank lines
Every statement line for every account, as the bank sent it.
Payroll
Each run by department, seen only by the roles you allow.
Sign-offs
Who signed what, when, and what was on the page.
How it is kept
One company, one database, one record of every change.
- One database per company
- Your company's data sits in its own database, behind its own login. That login cannot open any other company's database.
- Append-only audit
- Every change and sign-off is recorded with who made it and when, in the same transaction as the change itself.
- Keys never shown to a model
- Keys your Owner enters are encrypted in your database. Models never see them.
- Scoped access
- People see what their role and record scope allow. Tokens for outside tools are scoped, read only and rotatable.
- Ferrata staff
- Ferrata's admin console runs on counts, never on your records, and cannot open your database.
Shared or yours
Shared software, private records.
| A shared multi-tenant table | Orion | |
|---|---|---|
| Where your rows live | Beside every other customer's, filtered by an ID | In your own database |
| Who can open it | Any query that forgets the filter | Only your company's login |
| What changed | An activity feed, if kept | An append-only audit, per record |
| Secrets | Often stored beside settings | Encrypted, and never in a model's view |
What Orion works out, and what is yours
Orion does the arithmetic. People sign.
Isolation and the audit run on their own. Who sees what is your company's decision.
Orion matches, ties and calculates on its own, from the records already in your foundation. Every journal posted, every difference written off, every reconciliation signed off and every period locked is a person's decision, recorded with their name. Orion never moves money.
Orion works it out
- Keeps your records in your own database
- Writes every change to an append-only audit
- Encrypts every key your Owner enters
Always a person
- Who can see payroll and bank lines
- Every token for an outside tool
- Turning external access on
FAQ
Your data stays yours, run end to end.
Where are our ledger and bank lines stored?
In your company's own database, behind its own login. That login cannot open any other company's database.
Who can see our payroll?
The people your roles allow, and no one else. Ferrata's admin console works from counts, never from your records, and cannot open your database.
How is a sign-off recorded?
In an append-only audit, written in the same transaction as the sign-off: who signed, when, and what was on the page. Nothing in the audit is edited or deleted afterwards.
What happens to keys we enter?
A key your Owner enters is encrypted in your database, checked when it is entered, and never shown to a model. Ferrata's staff see only whether it is entered, active or failing.
Can outside tools read our close data?
Only through tokens your company creates. Each token is scoped to what it may read, follows the same roles and record scope as a person, and can be rotated or revoked at any time.
Related in Orion
- One foundationOrion reads what Atlas, Apex and Cortex already hold, with your GL, bank and payroll, in your company's own database.View
- Roles and sign-offThe same four roles as every Ferrata product, preparers and reviewers on every task, and a sign-off order you set.View
- MCP and API accessRead the close, cash and the overview from your own tools through scoped, rotatable, read-only tokens.View
- Payroll in the closePayroll read from your payroll register or your ERP's journals, by department, tied to the bank and the GL.View
See Orion work on your own close.
Bring last month's close: the checklist, the reconciliations and the trial balance. We run it through Orion beside your team and show you where it would have tied, and give you an honest answer if the close is slow for a reason upstream that you should fix first.
Your close calendar, chart of accounts, thresholds, reviewers and sign-off order are yours, and they stay yours. Orion is configured to the way your team closes. You are not handing over a playbook or fitting into a template.