Full export, on a schedule
Nightly or weekly to S3, Google Cloud Storage, Azure Blob, or SFTP that you own. Not a support request, not an offboarding process — a setting.
Platform · platform & data
Every vendor says you own your data. The question that separates the claim from the fact is whether you can get all of it, in a usable form, today, without asking anyone — and whether what comes out includes the parts that are inconvenient to export.
184 consecutive days tied · variance $0.00
What it does
Nightly or weekly to S3, Google Cloud Storage, Azure Blob, or SFTP that you own. Not a support request, not an offboarding process — a setting.
CSV and Parquet for records, JSON for structured objects, original files for documents, with a published schema so a competent team can load it elsewhere.
Chart of accounts, journals at line level, all subledgers, dimensions, customers, vendors, contracts, projects, and attachments — not a reporting summary.
Including reasoning on automated actions. It is the most awkward thing to export and the one you would most need if you ever had to prove something without us.
Direct sync to Snowflake or BigQuery where you would rather query it than store it, refreshed on the same schedule.
On termination, data is deleted from live systems within 30 days and from backups within 90, with written confirmation and the dates.
We are a young company selling software that would run your finance function. The honest risk in buying from us is not a security breach — it is that we do not make it, and you are left holding a system nobody maintains.
No promise about our prospects addresses that. What addresses it is a complete, current copy of your data sitting in storage you control, produced automatically, in formats that do not depend on us existing. That is the mitigation we can actually offer and it is why the export is a first-class feature rather than a clause.
We would rather you exercised the export before signing than discovered its limits later. Ask for a sample against a demo tenant, load it somewhere, and see whether it is what you would need. Any vendor confident in their export will let you do that; the reluctance itself is informative.
It contains your data, not our software. The policy engine, the agents, the reconciliation logic, and the interfaces do not come with it. What you get is a complete and structured dataset — accounts, transactions, relationships, documents, and history — that a competent team can load into another system.
Source code escrow is available on Enterprise. We say plainly that escrowed code is less useful than most buyers assume: it arrives without the infrastructure, the operational knowledge, or anyone who understands it. The data is the asset worth protecting.
Your data is not used to train models — not ours, not a provider’s. Provider agreements prohibit training on customer content and we do not fine-tune on your records. Where we improve agent behaviour, it is through prompts, policies, and evaluation sets built from our own test data, not yours.
Aggregated benchmarks published in our research are computed from customers who opted in, with figures aggregated so no single customer is identifiable. Opting out changes nothing about your service.
Limits
The export contains records and history. The policy engine and agents are not portable, and no export makes them so.
A structured dataset is a much better starting point than a set of PDFs, and it is still a migration project rather than an import button.
Escrowed code arrives without infrastructure or operational knowledge. We offer it and would rather you relied on the data.
Questions
Ask for a sample against a demo tenant. Load it somewhere and judge it yourself.