TheoVex
AI for regulated work

Build and run AI with compliance at every layer.

Applications for your teams. Intelligence, inference, and developer tools for your products. A compliance-first approach, from the work people do to the infrastructure behind it.

Built for healthcare, insurance, and the people building for them.

The TheoVex stack04 layers
  1. ApplicationsOpenCharts · Theo CRM
  2. IntelligenceTheo orchestration
  3. InferenceTheo ARCA models
  4. ConstructionAPIs · SDKs · AIRCTRL
Compliance across the stack

Purpose-built controls. Configured for your deployment.

The four layers

Four layers. Built for regulated work.

Use the applications, embed the intelligence, or build on the infrastructure. Start at the layer your team needs, with controls you can inspect.

  1. Applications

    Run the day-to-day.

    Connected workspaces for your people, business knowledge, and daily operations. Less switching between tools. More context with the work.

    Workspace roles, reviewed actions, and activity history.

  2. Intelligence

    Give AI a job to do.

    Theo coordinates models, memory, skills, and tools. Build AI workers that can carry out a workflow, not just return an answer.

    Per-key policy gates and live execution visibility.

  3. Inference

    Power the reasoning.

    Our own model platform, with serving tiers for speed, deeper reasoning, code, and constrained deployments.

    PHI guardrails and evaluation gates documented in the report.

  4. Construction

    Build it your way.

    Developer tools to bring AI into your own products, govern model traffic, and manage credentials across environments.

    Scoped access, a client-encrypted Vault, and audit history.

The controls

Control the work. Keep the evidence.

Regulated AI needs more than a good answer. It needs clear boundaries, visible execution, and a record your team can review.

  • Policy gates

    Set the boundaries.

    Theo guardrails are opt-in per API key. Use non-streaming responses when output must be checked before anyone sees it.

    Inspect the policy gates
  • Live visibility

    See what actually ran.

    Follow Theo’s routing, activated skills, tool calls, and artifacts as they happen. Investigate the execution, not just its final answer.

    Explore execution events
  • Protected credentials

    Keep secrets in scope.

    AIRCTRL Vault encrypts values on the client. Scope access by project and environment instead of passing credentials around in shared files.

    Review Vault security
  • Audit evidence

    Keep verifiable history.

    Theo’s immutable audit trail stores prompt hashes, not raw prompts. AIRCTRL’s append-only chains make changes to recorded history detectable.

    Read about audit records

Built to support HIPAA safeguards and SOC 2 control programs.

Our compliance approach

Controls are product-specific and must be configured; they are not automatic compliance or an attestation. Scope still depends on your deployment, operations, provider settings, and agreements. Gateway’s provider credentials and request handling have a separate trust boundary from Vault.

Still have questions?

Ask theo about
what we do.

Anything the page above didn't cover: the products, the engine, the research, or the team.

Ask Theo about
  • What we do
  • How it works
  • Our research
  • The team
  • Investors
TheoVexStart building

Build on theo.

One API key. The whole pipeline. HIPAA-native from the first request, built for healthcare and insurance.