The decision register
Every decision with the evidence it stood on, who signed it, the band the model gave and what happened. One calibration score across all of them, and a board pack the software assembles.
The registerEnterprise
Run the whole thing inside your own building
A company that cannot send its financial statements to a hosted service can still use this. On Enterprise the whole application runs as a private deployment on infrastructure you control: your server, your database, your own model keys or none, and nothing leaves.
The simulation is arithmetic on your own server. The network is arithmetic on your own server. The only thing that can ever leave your building is text you choose to send to a language model, and that can be turned off entirely without losing the product.
Most software that claims to be private is private except for the part that matters. This is the part that matters.
The governance layer
What a board asks for, built in
The portfolio
Every company in one book: totals from the ledgers, the attention list ranked by every reason, a house view of the world applied to any twin, and one question asked of all of them.
The portfolioRules that raise a hand
Eight questions asked every few hours, with thresholds you set, delivered in the application, by email, in a digest and to your hooks.
AlertsA second signature on every number
Changes to the ledger become proposals with the impact computed first; a reviewer signs or refuses; a snapshot is taken before every approval.
Four eyesOwner, reviewer, analyst, viewer
A viewer's seat is read only on every route. Approving needs a reviewer or the owner. Keys and hooks are the owner's alone.
Roles and the recordThe twin, frozen at every approval
And on demand. A diff between any two moments says what moved, how far, and which numbers came off a default.
SnapshotsThe forecast against what happened
The band pinned, the months laid on it, drift called after two misses on one side, and the ledger row behind it named.
MonitoringFourteen shocks, one resilience score
Demand, the largest customer, suppliers, rates, inflation, a key person, credit, terms, freight, reputation, currency, a recession. The weakest point named.
Stress testsKeys in, hooks out
Post files and actuals from the finance system with a key. Have the twin call your systems, signed, when something happens.
IntegrationsWhat enterprise means here
Six things, and none of them is a badge
Your server, your database
The whole application on a server you control. No outbound connection is required for the engine, the graph or the network. A twin can be built on a machine with no internet access at all.
Your own model provider
Point the language model features at your own account, your own endpoint, or a model you run yourself. Or turn them off and use the rule based extraction and the numbered evidence view. Where a model is used.
Signed, by a person who read it
A data processing addendum, security questionnaires answered rather than deflected, and a sub-processor list that is short because the architecture is.
A twin per holding
For a group or a fund, every company gets its own twin with its own files, its own graph and its own trained network. Nothing is pooled and nothing is compared without you asking for it.
Wire it into what you already run
Every route the app uses is available to you: sources, facts, assumptions, graph, runs, sweeps, network scores and full explanation chains. The API. A key lets your finance system post its monthly export and its actuals straight to the twin, and signed hooks call your systems when an analysis finishes, a decision is approved, a stress test completes or the actuals drift. Integrations.
Help building the first twins
The hard part is never the software, it is deciding which files count. Getting the first two or three twins built from your actual record is included rather than sold as a separate engagement.
The honest version
What you should ask before buying this
Counterfirm is new and the build status page lists what is not finished. An enterprise conversation that skips that is a conversation that ends badly later, so here are the questions worth asking, with the answers.
Is this in production anywhere at your scale? Probably not. Ask, and you will get a straight answer rather than a logo wall.
What happens if you stop working on it? On a private deployment the software is on your own server and it keeps running, under an agreement that says so. That is a real answer that most hosted software cannot give.
Who supports it? A small team, answering directly, without a ticket queue between you and the person who wrote the code. That is better than it sounds for the first year and worse than it sounds at large scale, and both of those are true.
Can we audit the model? Yes, and it is one file of readable arithmetic rather than a set of trained weights nobody can interpret. That was a design decision made with this question in mind.
- The source available to you under a private deployment agreement
- No outbound calls required for the simulation or the network
- Every assumption, score and sentence traceable to a file
- Invoiced rather than charged to a card
Against the listed plans
What changes at enterprise
| Question | Listed plans | Enterprise |
|---|---|---|
| Where does it run? | Hosted by us | Your infrastructure, or hosted, your choice |
| Limits | As listed on the pricing page | Agreed, and written into the contract |
| Language model | Shared allowance or your own key | Your own provider, your own endpoint, or off |
| Paperwork | Standard terms | Signed addendum, questionnaires answered by a person |
| Support | Email, same person | Named contact, agreed response times |
| Billing | Card, monthly or yearly | Invoice, annual |
| Getting started | Documentation and a readiness screen | Help building the first twins from your record |
| Price | Published | Quoted, based on what you need |
There is no invented enterprise price list on this site. What it costs depends on how many twins, whether it runs on your own server, and how much setup help you want, and it will be quoted at the real price the first time.
If you are a regulated firm, start with the security page and the data processing addendum rather than with a demonstration. They are written to be read by the person who will say no, and it is faster to find out early whether they will.
Enterprise questions
What does a private deployment need?
An ordinary web server with a database and enough memory to run the engine, which is modest. No queue, no worker, no graphics card, no external service. A diagnostics screen runs the engine on your own server and reports the timings, and we set it up with you.
Can we run it with no internet access at all?
Yes, with the language model features off. Extraction falls back to the rules, briefs are assembled from the numbers without prose, and Ask prints the numbered evidence. The simulation, the graph and the network are unaffected because they never needed a connection.
Do you see our data?
On a private deployment, no, by construction. On a hosted plan, nobody looks at a customer's files as a matter of course; the security page says exactly who can reach what and under which circumstances.
Can we get the source?
On a private deployment, yes: it runs on your server and the source is there. What the agreement covers is your right to modify it and what happens to that right if you stop paying, and that is written down rather than left implied.
How do seats work across a group?
A seat holder inherits the plan of the owner who granted it, and twins are owned rather than shared by default. For a portfolio, that usually means one owner per holding and analysts seated across several.
Will you answer a security questionnaire?
Yes, by a person, in prose, without pretending to hold certifications that do not exist yet. If the answer to a question is not yet, it will say not yet.
What about single sign on?
On Boardroom and Enterprise, your company proves its domain and connects its identity provider over OpenID Connect, and people are added and removed over SCIM. If you require it, a password is then refused for everybody else on that domain. On a private deployment, sign in can also be whatever that server already uses.
Start with one decision
The most useful first conversation is not a demonstration. Bring a decision you are weighing and one file that bears on it, and you will find out in an hour whether this is worth a procurement process.