Deploying TRANXACT: the map
The five phases of a customer deployment, who leads each one, the documents that define it, and which of these guides to read for what.
A TRANXACT deployment is one standardised architecture, built from infrastructure-as-code on the customer’s chosen cloud — Amazon Web Services, Microsoft Azure or Google Cloud — in the region the customer chooses. Each customer gets its own cloud account, network, Kubernetes cluster and database. No ledger or database is shared between customers.
Most of the work in these guides happens outside the product. Nobody can open a TRANXACT screen until an address range has been agreed, a DNS record published, a certificate issued and an identity provider federated — and none of those is a setting inside TRANXACT.
Five phases
| Phase | What happens | Led by |
|---|---|---|
| Proposal | The configurator proposal, sizing, the continuity tier, the bill of materials, and the architecture sign-off. | Ledger Architect |
| Onboarding & build | Audited revenue and contract, onboarding form, kick-off, environments built from code, connectivity, handover. | AI Deployment Orchestrator, with the Data Migration Conductor from the build onwards |
| Configure & migrate | Configuration, the migration cockpit, trial loads, reconciliation, cutover and go-live. | Data Migration Conductor |
| Operate & advise | Hypercare, then steady-state operations: monitoring, incidents, requests, releases, drills and restores. | Autonomous Operations Pilot |
| Renew | Adoption, ASK usage, the renewal sizing review. | AI Adoption Navigator |
The AI Deployment Orchestrator runs across all five, from contract to steady state, and is the customer’s single point of contact.
The milestones, in order: configurator proposal → audited revenue and contract → onboarding form → kick-off → environment build and connectivity → handover → configuration and migration cockpit → go-live → hypercare → continuous improvement.
The documents that define a deployment
The order form sits at the centre, and eight documents hang off it:
| Document | What it fixes |
|---|---|
| Master terms | The essential legal terms. |
| Licence schedule | The licence, priced as a share of annual audited revenue. |
| Service level agreement | Availability tier, RPO and RTO, the maintenance window, service credits. |
| Infrastructure & AI usage | Cloud billed at the provider’s list rates; ASK priced per use. |
| Support policy | Support scope, priorities and hours. |
| Data processing agreement | Personal data, technical and organisational measures, sub-processors. |
| Roles & responsibilities | The R&R workbook: every task, its category and its owner. |
| Service description | Usage metrics, eligibility and sizing tiers. |
Revenue-based licensing needs audited figures before the contract. Infrastructure is a separate cloud bill, so which account the cluster runs in has to be agreed before signature too.
Which guide answers which question
| Question | Guide |
|---|---|
| Who does this task, is it included, and how is it ordered? | Who does what: roles and responsibilities |
| How do I read and scope the R&R workbook for one customer? | Reading and scoping the R&R workbook |
| What is actually built in the cloud? | Reference architecture and runtime |
| Whose account is it, which environments exist, and is it reachable from the internet? | Staging the tenant |
| How do the customer’s networks reach it? | Network topologies |
| What happens when a zone or a region fails, or the data is corrupted? | Availability, Live DR, backup and the vault |
| Who is responsible for which security control? | Security, compliance and data residency |
| What has to be decided before the contract? | Before the contract: proposal, sizing and design |
| What happens between signature and go-live? | During the deployment: onboarding, build and go-live |
| How is it run afterwards? | After go-live: running the service |
Values marked proposed default are the deployment guide’s recommended starting points. Confirm each one per customer; the contract, order form, SLA and DPA prevail over this page.