Headless is a trust accounting system the trust company owns outright. The books of record live in a database you control. Your fee schedules, principal-and-income conventions, and processing rules are written down as your own governed library. The software that operates on them is built and maintained by governed rAgents — under human approval, with every change recorded.
The vendor's licence, the vendor's release calendar, and the vendor's change-request invoice are no longer part of the operating model.
A trust company's fee schedules, its principal-and-income conventions, its distribution standards, and thirty years of account history are the firm's own intellectual property. Yet in the prevailing model that property is stored inside a vendor's platform, expressed in the vendor's proprietary configuration, and accessible only through the vendor's screens, the vendor's nightly cycle, and the vendor's professional-services desk.
The consequences are familiar to every trust executive:
Every trust accounting system is the same three things stacked together. Headless separates them, puts the trust company in ownership of each, and treats the top layer — the software — as something to be regenerated rather than rented.
Accounts, positions, tax lots, principal and income, beneficiaries, the general ledger — held in an enterprise transactional database that runs inside your own isolated environment. Open, documented, and queryable by you at any hour, with no extract fee.
Fee schedules, allocation conventions, corporate-action treatment, reconciliation tolerances, reporting calendars — written in plain, reviewable language with worked examples. Versioned, approved by your officers, and readable by auditors. This is your Interpretation Governance made tangible.
Posting, statements, fee runs, custodian interfaces, reporting. Generated against your rules, tested against your worked examples, promoted to production only on a human decision. When a rule changes, the software is regenerated to match — not change-requested.
A fiduciary system cannot run on good intentions. Headless is designed so that the controls an examiner, an internal auditor, or a beneficiary's counsel would ask about are structural — they cannot be bypassed by a busy operator or an eager agent.
rAgents write the software; they never do the accounting at run time. Every posting, allocation, and fee is produced by fixed, tested code. The same inputs yield the same results, every time, with no model in the path.
Every proposed change is generated, tested against your worked examples, and run in parallel against live data. Promotion requires an officer's recorded approval. The agent proposes; the operator decides.
Headless runs beside your current system of record and reconciles to it — daily, to the penny — until the firm is satisfied. You do not leave your vendor on faith. You leave when the breaks are zero.
Rule versions, generated code, test results, parallel-run outcomes, and the approving officer are written to a hash-chained record. Years later, who changed what, when, and why is arithmetic — not recollection.
rAgents have no authority to move cash, execute trades, send a wire, or release a distribution. Those remain human acts, recorded as such. Headless extends reach; it does not transfer discretion.
Each trust company runs in its own isolated environment with its own keys, its own database, and its own record. No shared tenancy, no commingled data, and an architecture that answers vendor due-diligence questions on its face.
The licence, the uplift, the hourly change requests, the extract fees, and the exit penalty are removed from the operating model. What remains is infrastructure you control and a governed service that maintains the rules and the loop. Cost tracks your book, not a vendor's price list.
An enterprise transactional database with a native knowledge graph of your accounts, instruments, and relationships. Intraday posting. Immediate reconciliation. Your officers see a true position when they need it, not after tonight's cycle.
Per-firm isolation on a global edge network. Zero-trust access to every screen and every interface. Hash-chained records that make tampering visible. Continuous inside-the-boundary monitoring through Inside Guard. The attack surface of a shared vendor platform is simply not present.
No batch window, no cut-off, no maintenance weekend. Your data and your rules are available to your people, your custodians, your advisors, and your Reasoning Engine at any hour — through documented, governed interfaces rather than a vendor's professional-services queue.
| Capability | Legacy vendor platform | Headless |
|---|---|---|
| Who owns the rules | Vendor configuration, proprietary format | The trust company, in a reviewable governed library |
| Who owns the data | Vendor-hosted, extract on request, fee on exit | The trust company, in its own isolated environment |
| Pace of change | Vendor release calendar; hourly change requests | Rule approved today, software regenerated and tested today |
| Processing model | Nightly batch, cut-off times | Intraday, continuous reconciliation |
| Audit trail of system changes | Vendor ticket history | Hash-chained record: rule, code, tests, approver |
| Isolation | Shared, multi-tenant platform | One firm, one environment, own keys |
| Exit | De-conversion project, priced to deter | You already hold the data and the rules |
Trust administration is consolidating around the firms that can take on more accounts per officer, respond to a client or an examiner the same day, and price with confidence because they know their own cost to serve. None of that is possible while the system of record belongs to someone else.
When the rules are explicit and the software keeps itself aligned to them, exceptions fall, officers carry larger books, and growth no longer means a proportional rise in operations staff.
Reg 9 reviews, fee verification, principal-and-income tie-outs — produced from your own data, against your own written rules, with a record that proves what was decided and when.
With cost to serve known and vendor margin removed, fee schedules can be set to win mandates rather than to cover someone else's licence.
“The vendor sells you software. What you actually own is the data and the rules. Headless returns both to the trust company and makes the software the cheapest part of the system.”
— r.Team product principle
Headless is not a big-bang conversion. It is a governed migration that begins with a single bounded module and proves itself against your current system before the next module follows.
Working with your officers, we capture one module's rules — fee calculation is the usual first choice — as a governed library with worked examples drawn from your real schedules.
rAgents generate the module's software against the library and test it against every worked example. Failures are visible; nothing proceeds until the examples pass.
The module runs beside your current platform on live data. Every break is examined; most are undocumented rules you have just discovered and can now write down.
When breaks reach zero and your officers approve, the module becomes the system of record for that function. The decision is hashed. The next module begins.
Firms that compete on service and responsiveness and cannot afford to wait for a vendor's roadmap. Headless gives a boutique the operating model of a much larger institution.
Institutions with mature books, complex fee arrangements, and an examiner relationship that rewards demonstrable control. Headless makes the controls visible and the costs predictable.
Headless connects to your custodians, your advisors, and your remaining systems through the Bridge, and works alongside rAgent, Keep, Verified Client Messaging, and Inside Guard as part of the r.Team platform.
A Headless briefing is a working session with your operations and compliance leads: we select the first module, review what a governed rules library would look like for your firm, and outline the parallel-run plan. No conversion is proposed. No data leaves your boundary.
Headless is a product of r.Team by Got-Data Inc. Availability, first module, and scope are set per firm. No customer logos, case studies, pricing, or compliance certifications are implied.
