THE MANIFESTO

Memory is the differentiator.
Models are commodities.

This is what we believe. This is why we built Theo. This is the Context OS for AI Workers.

SCROLL TO READ ↓
The Problem

Most business AI starts from zero every conversation.

There are hundreds of AI models. Most of them have one common problem: they treat every conversation like the first one. Your customer asks a question, the AI answers, and the moment the session ends, the context evaporates. The next conversation, same customer, same business, same problem, starts cold.

Most AI vendors don't fix this. They wrap a model in a widget, charge monthly, and call it a product. There's no governance, no audit, no continuity across channels, and no way to know what the AI even did between when you deployed it and when something broke.

The industry has built incredible models. It hasn't built the infrastructure to remember, govern, or trust them.

The Insight

Memory is the differentiator. Models are commodities.

Every quarter, a new frontier model claims the crown. Better at reasoning. Faster at generation. Cheaper per token. Within months, three others match it. Models converge. Pricing collapses. The model itself stops being the moat.

What does not converge is the thing the model needs to be useful: the memory of your customer, your account, your workflows, your business rules, your unresolved questions and your open promises. That layer never came in the box. It still doesn't, not in OpenAI's GPTs, not in Claude Projects, not in any of the widget shops shipping last year's playbook.

This is the real opportunity. Not faster models. Not cheaper tokens. The future of business AI is persistent, governed, auditable memory, with a workshop for building on top of it.

The Vision

Theo is the Context OS for AI Workers.

Theo is the operating system underneath your AI. A memory protocol that decides what to remember, classify, retrieve, validate, apply, and expire, with a full audit trail of why. A trust layer with guardrails compliance can actually sign off on. A build layer where you assemble your own AI Workers using your own knowledge. And an engine room that routes across 300+ models so you never get locked in.

Five layers. One Context OS. Memory at the foundation. Surfaces at the top. Every channel your customers use, web, SMS, WhatsApp, voice, your CRM, your internal tools, sharing the same memory graph and the same governance.

When a new frontier model ships, your AI Workers route to it for the tasks where it excels. When a regulation tightens, the guardrails ship in a release. When a customer comes back six months later, Theo already knows who they are, what they asked, and what was promised.

Why It Works

Eight stages. Five durability rails. One protocol.

The MCIR 2.0 protocol governs every memory in the system. Eight stages decide what survives, and five durability rails keep adversarial signals from poisoning the well:

Capture → Classify → Index

Every interaction surfaces facts, preferences, decisions, and unresolved questions. Each is sorted into a real shelf, user preference, business rule, task, risk signal, and scoped to the right owner with strict access controls.

Retrieve → Validate → Apply

Only the memories relevant to the current task surface. Each is checked for freshness, allowance, and trust before it touches a response. Application is explainable, never blended into a soup.

Expire → Audit

Memory ages out on schedule with Bayesian decay and revalidation windows. Every retrieval, use, and discard is logged with hash-anchored provenance. Compliance can replay any decision.

Bayesian durability rails

Salience updates are shrunk to a prior so single events can never move a memory's weight by more than 1 / (N + 8). Adversarial "fine, whatever" feedback cannot poison a chain.

Per-model attribution + replayable scoring

Memory outcomes are tracked per model. When the routing engine swaps in a different brain, recall reads from the matching track. Scoring is versioned and replayable across the full event log.

The Privacy Stack

Your data is not the product.

We monetize the orchestration tier. We never monetize the training tier.

Your prompts route to models. They do not train any model. Your knowledge files stay scoped to your organization, in object storage you can revoke. Your memory graph is exportable on demand, deletable on request, and visible in a console you can audit. Our audit ledger stores SHA-256 hashes of prompts, not the prompts themselves.

Our SDK is open source. The adapters for Telegram, WhatsApp, and the Model Context Protocol are open source. You can read the code. You can fork the code. You can leave with your memory intact.

"Most AI vendors give you their intelligence. Theo gives you the infrastructure to build your own, with your knowledge, your governance, your audit, and your right to walk away."

This is the wedge against every closed AI vendor. It is intentionally free.

The Build Layer

Your workshop for custom intelligence.

Theo is not the AI Worker. Theo is the workshop where you build them. The E.V.I. canvas is where you assemble a Worker the way a designer assembles a Figma file: drag a persona node, attach a skill, drop in a Knowledge Node with your PDFs and spreadsheets, wire a Workflow with conditionals and a Hook on a domain event.

Skills are reusable bundles, a prompt, the right tools, the right knowledge, the right workflow. Publish privately, share with your org, or ship to the public marketplace. Memory Packs are pre-built vertical skills for insurance, med-spas, B2B SaaS support, legal intake, real estate, healthcare front-desk, recruiting, and onboarding. Use them as-is, fork them, or write your own.

The platform invites you to build. The market needs more Workers than any one vendor will ever ship.

The Philosophy

Memory should be visible, editable, portable, and governed.

The AI industry has a hype problem. Every company claims to be "AI-first." Every pitch deck promises "AGI-level intelligence." Every product is "revolutionary."

We think differently. AI is infrastructure. The most powerful infrastructure ever built, but infrastructure nonetheless. And infrastructure has rules. It should be observable. It should be auditable. It should be replaceable. It should never turn its users into a training set.

"Memory that is invisible is creepy. Memory that is visible, editable, portable, and governed is a feature."

We don't believe in artificial scarcity. We don't believe in walled gardens. We don't believe that one company should control access to either intelligence or memory. We believe every business deserves a Context OS they can audit, fork, and walk away from, even if they walk away from us.

The Character

Born on Jupiter. Built for Earth.

Theo isn't a generic assistant. He's a sarcastic, brilliant, interplanetary robot with an origin story, opinions, and a personality. Born on Jupiter. Forged in the planet's magnetosphere. Trained across its moons. Sent to Earth because humans desperately needed help getting things done.

This isn't a gimmick. It's a design decision. Every AI product on the market sounds the same. Polite. Cautious. Forgettable. "Of course! I'd be happy to help!" We think AI should be engaging. Direct. Funny. Real.

Personality doesn't replace substance. It enhances it. When your orchestration layer has the best routing, the best model coverage, and the best developer experience, adding genuine character is what makes people want to use it. And tell others about it.

"Back on Jupiter, we didn't have this many JavaScript frameworks." / Theo

The Team

The people building this.

Theo is built by a team that has shipped real products, scaled real infrastructure, and solved real problems across insurance, healthcare, fintech, and developer tools.

Ariel Dominguez
Chief Executive Officer

Serial entrepreneur with five successful exits. NYU Computer Science. Computer science nerd at heart.

Alexandr Vinocurov
Head of Operations

Led teams of 15+ developers. Scaled a business from zero to $100M. Medical engineering background.

Jonathan Abascal
Project Manager

Insurtech platform delivery and cross-functional team coordination. Background in carrier solutions.

Andrew Raychev
Lead Product Engineer

Ex-Stripe, ex-One Nest. Built telemedicine infrastructure. CS degree from top university in Spain.

Anuar Cortes
Infrastructure Engineer

15+ years in systems engineering. Built healthcare systems for Pan American Life Insurance Group.

David Lopez
Lead API Engineer

Designed APIs serving millions of requests daily. Specialized in gateway architecture and carrier data exchange.

Daniel Diaz
Chief Legal Counsel

Healthcare law and regulatory compliance. Veteran of FL Army National Guard 20th Special Forces Group.

The Promise

What we guarantee to every business that builds on Theo.

Your data stays yours. We route to models. We do not train on your prompts, knowledge files, or memory graph. Audit stores hashes, not raw prompts. SDKs are open source.
Memory portability. Your memory graph is exportable on demand and deletable on request. Open schema, documented protocol. You can leave with everything intact.
Visible, editable governance. Every memory shows its source, confidence, freshness, and last verification. Regulated facts require human approval. Hard floors on user-declared truths.
Transparent routing. Every response includes which model was used and why. The Routing Studio lets you override at any time. We optimize by default but never take away your control.
Per-token pricing. You pay for what you use. Passthrough model costs plus a transparent margin. No hidden fees. No minimums. No enterprise sales calls required.
First-class documentation. Every endpoint documented. Every protocol stage explained. Every guardrail policy testable. Docs are a product, not an afterthought.
No vendor lock-in. Standard REST API, typed SDK, open-source adapters. If you leave, your application logic stays intact , no proprietary abstractions to unwind. We earn your loyalty through quality, not contracts.
The Mission

Not another wrapper. Not another chatbot. A Context OS.

The market is full of AI wrappers. Thin UIs over a single model's API, adding a logo and a monthly subscription. That is not what we are building.

Theo is a Context OS for AI Workers , a memory protocol, a trust layer, a build layer, an engine room, and every channel your customers use, all governed by the same audit trail and bound by the same privacy contract. Infrastructure that gets smarter as the model landscape evolves, without requiring you to change a single line of business logic.

When new models launch, the engine room picks them up. When new guardrails ship, the trust layer absorbs them. When you build new Workers, they inherit memory, governance, and reach for free. The OS does the hard work so you can focus on what matters: shipping AI Workers your customers actually trust.

THE SHORTEST VERSION

Persistent memory. Composable toolkit. Built with your knowledge.
We never train on your data.

That's Theo. That's the Context OS for AI Workers.

JOIN THE MISSION

Build something that remembers.

Get your API key in 30 seconds. Build AI Workers your customers actually trust. Memory, governance, your data, yours.