Resources

Read before you shortlist.

The architecture overview, answers to the questions evaluators ask first, and the terms Teradius uses precisely.

Architecture overview (PDF)

A six-page summary of the architecture page for circulation to a technology committee: layers, principles, deployment and data, and the status of each capability.

Placeholder. The document is being prepared and will be linked here. Until then, the Architecture page carries the same content.

Read the Architecture page

Frequently asked questions

Can we start with one module?

Yes. Every module is sold as Core plus that module and runs standalone. Adding a module later is a licensing step on the same tenant, with no migration.

Is Teradius available now?

Teradius is in pre-release and working with a small number of companies by invitation. Module status labels on the Modules page show what is in development, planned or in design.

How is pricing structured?

Modular pricing. Start with Core plus one module. Talk to us. Modules are licensed per entity with user seats where relevant; packs are entitlements added to an existing tenant.

Where is our data stored?

The architecture places each tenant in one home region with in-region data residency, designed for Australia and the UAE first. This is planned for the cloud service; the current pilot runs in Australia.

Can we keep our existing ERP or CRM?

A planned entry configuration pairs Core, Intelligence and Strategy with connectors to third-party ERP and CRM systems, so a board can adopt Teradius before the company replaces its operational software.

What can an AI agent do without a person?

Only actions a module has registered in the action catalogue, within the agent's permissions and budget. Where a person would need approval, so does the agent, at the moment of execution. Everything is audited.

Do you hold security certifications?

Not yet. We will state certifications only when they are granted. The Security and trust page lists each control with its status.

Which jurisdictions are supported?

Jurisdiction specifics ship as packs, so the platform itself is not tied to one country. The Packs page lists the jurisdiction packs and their status.

Glossary

Action catalogue: The set of typed actions each module registers. Workflows and agents can act only through it.
Board Room: The Teradius Strategy workspace where board directives are tracked with progress computed from operating data.
Cell: A self-contained deployment unit in a home region that holds a set of tenants and their data.
Core: Teradius Core, the always-present layer that owns identity, entities, permissions, audit, entitlements, the process engine, the action catalogue and exact money.
Directive: A board decision recorded in Teradius Strategy, with objectives, key results, guardrails and initiatives beneath it.
Entitlement: A record in the Core catalogue that switches a module or pack on for a tenant and is checked in every request.
Exact money: Arithmetic on monetary amounts that produces no rounding drift and refuses out-of-range values.
Guardrail: A counter-metric attached to a key result. If it is breached, the key result is reported as unhealthy even when the target is met.
Pack: A versioned bundle of processes, rules, forms, reports and settings for an industry or a jurisdiction, applied by overlay.
Receipt: The duplicate-request record that makes a repeated request return the first result instead of posting twice.
Strategy Lab: The Teradius Strategy sandbox where strategies are modelled on a snapshot of real figures and compared as ranges.
Tenant: A customer organisation in Teradius. Tenant and legal entity are the only tenancy keys.

Request early access See how it works