What does ATLAS give the end user?

The part people actually see and use: the web and mobile applications, dashboards, integrations and APIs through which the rest of the platform is delivered.

How does it connect to systems a customer already runs?

Through documented APIs and prebuilt connectors for common business systems, so the platform slots into existing workflows instead of demanding new ones.

How do users know whether to trust an answer?

Answers are shown with their supporting sources, a confidence indicator and an easy route to the underlying document, so a person can verify before acting.

Is it usable by non-technical staff?

That is the design goal. Requests are made in ordinary language, results are presented as readable summaries and visualisations, and no configuration knowledge is assumed.

Why is the interface a funded module rather than a wrapper?

Adoption decides commercial return. A capable platform that people find awkward to use generates no revenue, so delivery, integration and usability are funded as first-class engineering.

All modules

M07 · In Design

ATLAS

Enterprise interface and integration suite

Investment

$1,300,000

Share of programme

9.1%

Timeline

Q3 2026 — Q2 2028

Delivery team

11 engineers / 3 designers

22% complete

Enterprise workspace and API surface visualisation for the ATLAS module — M07 · ATLAS — Enterprise interface and integration suite

In plain English

The part customers actually see and buy — the workspace, the connectors into their existing systems, and the controls their administrators need.

What the software does

Provides the web workspace where staff ask questions, review agent work and approve actions.
Connects to the systems a business already runs, so the platform reads live data instead of copies.
Gives administrators control over who can see what, with single sign-on and role-based permissions.
Reports usage, cost and value delivered so a buyer can see the return.

How it works, step by step

01ConnectPre-built connectors and an open API link the platform to the customer's existing data and identity systems.
02WorkTeams use one interface to ask, review, approve and hand back — with the full trace of how an answer was produced.
03Govern and accountAdministrators set permissions and limits; dashboards show consumption and outcomes per team.

A simple analogy

Everything else is the engine. ATLAS is the dashboard, the steering wheel and the keys handed to the driver.

Why it matters

This is the commercial surface: it converts six modules of engineering into something a customer can sign a contract for.

How ATLAS works

Inside the module

The six underlying modules go in; a product an enterprise can buy and operate comes out.

Input

Platform APIs
Everything the six other modules produce
Customer systems
Existing business software and data sources
Identity
Single sign-on, roles, quotas and entitlements

M07 pipeline · select a stage

1/4

The platform is joined to systems the customer already runs

Prebuilt connectors and a documented API let the platform read from and write to existing business systems, so it fits the current workflow.

Connector suitePublic REST APIWebhooks

Output

Workspace
The application analysts and operators use daily
Integrations
Results delivered into systems people already work in
Oversight
Usage, cost and access visible to administrators

Stage by stage, in detail

Workspace

A collaborative surface where analysts run, review and share model and agent work.

Administer

An admin console for tenants, roles, quotas and policy assignment.

Connect

Connectors read and write against enterprise systems of record under scoped permissions.

Expose

A public API and SDKs unify NEXUS, ORACLE and HELIX under one auth and quota model.

Meter

Usage metering wired into the inference fabric drives quotas and usage-based billing.

Design partners

Validating the workspace prototype across three regulated verticals

First connectors

Enterprise systems of record in the initial release

22%

Module complete

Design system and metering schema finalised

Multi-tenant workspaceAdmin and tenant consoleEnterprise connector suitePublic API + TypeScript/Python SDKsMetering and billing engineDeveloper portal

Questions answered

ATLAS FAQ — how the AI works, in plain terms

Common investor questions about what this module does, how it does it, and why it is funded as part of the programme.

Scope

ATLAS is where the other six modules become a product. A collaborative workspace for analysts, an admin console for IT, connectors into the systems of record, and usage-based billing wired into the inference fabric.

The public API and SDKs expose NEXUS, ORACLE and HELIX under one authentication and quota model, with tenant isolation enforced by AEGIS policy.

Design bias is toward observability: customers can see exactly what an agent did, what it cost and what data it touched.

Contracted deliverables

Multi-tenant workspace and admin console
Connector suite for major enterprise systems of record
Public API, SDKs and developer portal
Metering, quota and usage-based billing

Achieved to date

Design system and workspace prototype validated with 5 design partners
Metering schema finalised against the inference fabric

Currently in production

Admin console and tenant management
First 8 enterprise connectors
Developer portal and public SDK release

Where it is used

Analyst workspace

The daily surface where customers actually get value out of the platform.

Developer platform

Third parties building on the stack through a single documented API.

Commercial metering

Usage-based billing that converts inference volume directly into revenue.

Platform dependencies

Fronts every other module
Tenant isolation enforced by AEGIS
Meters usage against the VERTEX fabric

Key risks and mitigations

Connector maintenance burden

A shared connector framework rather than bespoke integrations per customer.

Product surface outpacing capability

Design partner cohort gates each release against real workflows.