Teradius Enterprise Suite: early preview access is open.Register your interest

TeradiusENTERPRISE SUITE
Platform

One Core. Everything else stands on it.

Eleven layers, one tenancy model and one data model. Select a layer to read what it does, then compose the suite you would start with.

Architecture explorer

The platform, layer by layer

Select a layer to expand it. Arrow keys move between layers.

  1. Everyone and everything that acts in Teradius. Board members get a read-only view. Executives, finance and operations teams run the business. Partner systems connect through APIs. AI agents sign in with identities, roles and scopes of their own, so the same rules reach them.

    • People sign in with multi-factor authentication; single sign-on is planned
    • Agents hold identities, roles and scopes like people
    • Partners connect through versioned, signed APIs
    In development

  2. One native web application serves every module, so adding a module adds screens, not systems. The board view is a separate, read-only experience with its own audit trail. Public APIs are versioned contracts that partners can rely on.

    • One shell shows only what is entitled
    • Board view: read-only, aggregated, separately audited
    • APIs and webhooks, versioned and signed
    In development

  3. Always present. Core owns the mechanics every module relies on and never a business outcome: who you are, what you may do, what happened, what is switched on, how processes run and how money is computed.

    • Identity and MFA; organisations and legal entities
    • Role, record and field-level permissions for people and agents
    • Immutable audit; licensing and entitlements checked in every request
    • Process engine, action catalogue, exact-money services and duplicate-request receipts
    In development

  4. The operating products. Teradius CRM and ERP run customers and finance. Teradius Studio shapes workflows, forms and decision rules without code. Each runs standalone as Core plus that module, and all share one data model, so adding a second module is a licensing step, not a project.

    • Teradius CRM and Teradius ERP: in development
    • Teradius Studio: in design, internal use first
    • Any module runs standalone on Core
    In development

  5. Evidence from the source records. Metric definitions are governed and versioned, every number traces to the rows it was computed from, and forecasts are shown as ranges with their accuracy published beside them. Connectors read third-party ERP and CRM, so Intelligence can run before those systems are replaced.

    • Board-owned, versioned metric definitions
    • Drill-through from any number to its source rows
    • Connectors to existing ERP and CRM systems
    Planned

  6. The differentiator. Board decisions become directives with objectives, key results and guardrails, and progress is computed from live operating data, never typed in. The Strategy Lab tests a price change, a new site or a hiring plan on a copy of the real figures before anyone commits.

    • Board Room: directives, guardrails, frozen board packs
    • Strategy Lab: scenarios as ranges, assumptions on record
    • Executives explain beside a number; they never edit it
    In design

  7. A single runtime serves every agent in the suite. Agents act only through the typed actions in Core's catalogue, under the same permissions, approvals and audit trail as a person, with budgets and a stop control. An agent never invents a figure.

    • Approval checked at the moment of execution
    • Budgets, stop control and a model gateway per tenant and region
    • Works without a model: every action is a typed, auditable call
    In design

  8. Versioned bundles of processes, rules, forms and reports layered on the suite. Industry packs: Professional Services, QSR and Hospitality, and SEZ (Special Economic Zones), described as Free Zones for UAE audiences. Jurisdiction packs: Australia and the UAE first. Customers customise by overlay, never by fork.

    • Teradius Pack: Australia is in development; UAE is in design
    • QSR and Hospitality and SEZ run standalone on Core; ERP optional
    • Every pack release carries upgrade tests
    In design

  9. How Teradius talks to the outside world: connectors to third-party ERP, CRM and banking systems, public APIs and webhooks, and e-invoicing networks through jurisdiction packs. External providers are called only through an outbox with duplicate-request receipts, so a retry never sends twice.

    • Duplicate-request receipts: in development
    • Public APIs and webhooks: in development
    • Third-party connectors and e-invoicing: planned
    In development

  10. One tenancy key, the tenant and its legal entities, across every module. One shared data model. An immutable audit trail, exact money arithmetic and duplicate-request receipts. A thin global control plane holds directory and catalogue only, never business records.

    • Every change audited: true now
    • Exact money arithmetic: true now
    • One tenancy model, one data model: in development
    In development

  11. Each tenant lives in a cell in its home region, with in-region data residency designed for Australia and the UAE first. Stateless services scale up; cells scale out. The pilot today is one tenant in Australia on a web shell, managed database and Python services.

    • One region per tenant; residency Australia and the UAE first
    • Pilot today: one tenant in Australia (true now)
    • Multi-region cells: planned
    Planned

Select a layer to expand it. Arrow keys move between layers.

Build your suite

Start with Core plus one. Add the rest when you are ready.

Choose the modules and packs you would start with. Every module runs standalone on Teradius Core. Add another and the links between them light up, with no re-implementation.

Teradius CoreAlways present. It comes with every module and is the reason a second module needs no migration.

Modules

Packs

Your suite

Teradius Core

What lights up

    This explainer needs JavaScript. The text below describes the same thing. Every module is a complete product on Core. The rest light up when you add them.

    No prices here. Modular pricing. Start with Core plus one module. Talk to us.

    Principles the architecture enforces

    Core plus any module

    Customers start with one module and grow. No re-implementation when the second arrives.

    In development

    One tenancy model, one data model

    Tenant and legal entity are the only tenancy keys. Every module reads and writes the same records.

    In development

    Every change audited

    Create, change and action by any person or agent is recorded with who, when and what.

    True now

    Exact money arithmetic

    No floating-point drift. Out-of-range amounts are refused, never approximated.

    True now

    Never double-post

    Repeated requests carry a receipt. The same request twice returns the first result.

    In development

    AI through governed actions only

    Agents act through the action catalogue under the same permissions, approvals and audit as people.

    In design

    Deployment and data

    One region per tenant

    A tenant's records live in exactly one home region. The control plane holds directory and catalogue only.

    Planned

    In-region data residency

    Designed for Australia and the UAE first, with more regions added as cells.

    Planned

    Scale vertically and horizontally

    Stateless web and API tiers replicate freely; leased workers mean no single scheduler to saturate.

    Planned

    Pilot today

    One tenant in Australia: web shell, managed database and Python services. The cloud service follows the runway above.

    True now
    Architecture overview PDF
    Request early accessSee how it works