1. Home
  2. Platform
  3. Capabilities
The NatusAI capability cataloguePlatform vision

One connected path from request to outcome

The NatusAI constellation is designed to connect what people ask for, what AI and engineering produce, what is verified, what is released and what actually happens in operation.

Platform vision · scoped foundations. This map describes the intended seven-role platform. NatusAI Lyra UI is an existing component system; NatusAI Cygnus 1.0 is planned and gated; the wider Orion experience remains a vision.

01 / Request and build

Turn a need into a verifiable application.

The Orion vision connects user intent to source changes, evidence, releases and observed outcomes.

Platform vision

01. Chat, requests, issues and knowledge

Owner Orion Workspace

Keep conversations, feedback, accepted requirements, decisions, documentation and support history connected. Incoming feedback only becomes a requirement after deliberate acceptance.

Explore Orion Workspace

Platform vision

02. Source history and collaboration

Owner Orion Workspace

Link versioned source and engineering documents to exact changes, reviews and work items. The Git forge and integration approach remain unselected.

Explore Orion Workspace

Platform vision

03. AI execution and context

Owner Auriga

Coordinate exact model bindings, authorised tools, relevant versioned context, durable attempts, cancellation, checkpoints and budgets.

Explore NatusAI Auriga

Platform vision

04. Build, verification and release

Owner Orion · Auriga

Produce candidate changes and previews in isolated workspaces; retain test evidence; promote immutable application releases through independent authority.

Explore NatusAI Orion

02 / Foundation and reuse

Keep data and interfaces connected.

The planned Cygnus release and existing Lyra components have different availability and qualification boundaries.

Planned v1Existing UI

05. Application runtime and UI

Owner Cygnus · Lyra

Cygnus is designed for typed language, data and services. Lyra already supplies reusable interface components; each application composes them for its own work.

Read the planned Cygnus 1.0 scope

Platform visionLater profile

06. Reusable libraries and artifacts

Owner Orion · Cygnus

Discover exact compatible modules, retain dependency and provenance records, and reuse independently verified releases. Private customer data and logic stay separate.

See the Cygnus roadmap

Platform vision

07. Documents and ingestion

Owner Aquila

Retain source bytes and provenance, produce separately identified text or chunk derivatives, and scope document interpretation to the application. Exact formats and providers need qualification.

Explore NatusAI Aquila

Platform vision

08. Integrations and notifications

Owner Shared libraries

Connect external services and deliver authorised notifications while tracking credentials, external effects and delivery failures.

How the platform connects

03 / Operate and recover

Keep the running system observable.

Deployment success, observed health, a completed backup and verified restoration are different pieces of evidence.

Platform vision

09. Infrastructure and delivery

Owner Draco

Manage environments, deployments, networking, domains, certificates, capacity and desired versus observed operational state.

Explore NatusAI Draco

Planned v1Vision

10. Schedules, events and durable workflows

Owner Cygnus · Orion · Auriga

Use planned durable jobs and schedules for recurring work and admitted retries; show their status in Orion and allow authorised AI steps through Auriga.

Read the planned Cygnus 1.0 scope

Platform vision

11. Monitoring and incidents

Owner Orion · Draco

Connect runtime telemetry, infrastructure observations and application acceptance checks to the affected release and application.

Security and recovery

Platform vision

12. Backup and recovery

Owner Gemini

Preserve data, configuration, application releases and recovery points together. Prove a restore through drills; backup completion alone is insufficient.

Explore NatusAI Gemini

04 / Govern and own

Keep authority and ownership explicit.

One connected experience still needs scoped access, accountable usage and an independent path back from failure.

Planned v1Vision

13. Identity and authority

Owner Orion · Cygnus

Govern organisation and application membership, scoped agent delegation, secrets and audit. Platform visibility never implies access to tenant-confidential content.

Sovereignty and ownership

Platform vision

14. Usage, budgets and billing

Owner Orion

Attribute hosting, AI-assisted development, ongoing maintenance and AI used inside customer applications to organisations, applications and jobs as distinct records. Provider-side costs and customer invoices are separate; funding, rates and billing policy remain open commercial decisions.

Questions about commercial terms

Platform vision

15. Platform bootstrap and independent recovery

Owner Orion · Gemini · Draco

Retain installation, promotion and recovery paths usable when Orion or its AI provider is unavailable.

Security and recovery

Platform vision

16. Ownership and portability

Owner Orion and every role

Identify owners and export paths for source, requirements, releases and data under access policies. Portable tenant export is beyond planned Cygnus 1.0.

Sovereignty and ownership

Designed for efficient AI use

Use context deliberately. Verify the result.

These seven principles guide the platform vision. They do not claim a measured token saving or that every existing part was built by AI.

  1. Machine-usable contracts

    Typed, versioned, permission-aware API, MCP and CLI surfaces describe capabilities, effects and structured outcomes.

  2. Progressive context

    Discover an exact capability first, then retrieve only the needed schema, source range, example or evidence.

  3. Durable work and knowledge

    Requirements, decisions, task state and verified results survive sessions with source references and freshness.

  4. Compact, sufficient feedback

    Bounded diagnostics, precise diffs, pagination and artefact references carry enough detail for correction.

  5. Reuse before regeneration

    Find compatible libraries, components, contracts and proven workflows before producing another copy.

  6. Independent verification

    Keep exact inputs and provenance; test and review changes under authority that the proposing agent cannot grant itself.

  7. Measured total efficiency

    Evaluate successful completion alongside tokens, retries, latency and cost. A shorter prompt is not useful if errors and rework rise.

Useful automation depends on more than a larger prompt: the same contracts, evidence and approvals that people rely on are what AI agents use. No measured token-saving or cost-reduction claim is made.

See the release boundaries

Explore the whole family. Inspect the technical scope.

The seven names describe responsibilities within one intended system. NatusAI Cygnus has a separate first-release plan and qualification gates; NatusAI Lyra’s current components have their own documentation.

Inside Orion Workspace: one request, a traceable path

Glowing glass cubes holding connected node graphs, linked in space: one connected platform
Build your next chapter

Let’s connect the possibilities

Tell us what your business needs. We will help you find a practical place to start, and tell you plainly which capabilities exist today.

Or write to contact@natusai.com

A product owner, a security officer and an analyst reviewing an internal app before release (illustrative image)