Automatos·ai
Automatos AI · The company & the OS Open · Apache 2.0 Studio · Live as SaaS

One OS.
Any interface.

Automatos OS is the engine: an open-source, API-first backend with agents, memory, retrieval, knowledge graphs, NL2SQL, documents and socials. Studio is where you run it. Everything else is built on top of it.

Runs in
Automatos Studio
Plate 001 One OS
The engine in the middle, every interface around it
↗  Powered by Automatos AI
Chapter 01 The OS
Headless · API first · open source
↗  github.com/AutomatosAI

One engine underneath.
Any interface on top.

Automatos OS has no screen of its own. Agents, memory, retrieval, graphs, NL2SQL, documents, socials and the harness that governs them all sit behind one API. Studio is the first interface; widgets, chat channels, our own products and yours are others.

AutoAgentsMemoryRAGNL2SQLKnowledge graphsDocumentsSocialsAnalyticsHarness · governance, budgets, standardsChat channels1,000+ apps
/01 API first.Everything Studio does goes through the same API your own app can call.
/02 Modules with walls.17 feature modules whose boundaries CI enforces on every change.
/03 MCP.Agents in Claude Code and Codex sessions call the OS's tools over MCP today.
/04 Apache 2.0.Fork it, audit it, self-host it. Bring your own model keys.
Plate / 003 · System
The system,
end‑to‑end.
Fig. 03 — Router · Mission · Memory Open · Apache 2.0 · v1.36.04
Router 7 tiers

Every incoming message walks the same ladder — fast deterministic rules first, semantic and LLM only when they earn it.

T0Overrideuser
T1Cacheredis · ~5ms
T2aRulessource · pattern
T2bTriggersjira · webhook
T2.5Semanticcosine · 0.95
T2cIntentkeywords
T3LLMclassify
Mission engine DAG · 5s tick

Goals decompose into a task graph. A stateless coordinator reconciles state every 5 seconds — plan, dispatch, verify, repeat.

/01Decomposeplanner
/02Approvehuman · hitl
/03Dispatchparallel · locked
/04Executeagent · tools
/05Verifycross-model
/06Reconcilestall · retry
/07Reportevents · cost
Memory 5 layers

A biologically‑inspired hierarchy. Sessions promote into facts; facts decay until they earn a place in long-term memory.

L0Focuscontext window
L1Workingredis · 24h
L2Short termpostgres · decay
L3Long termmem0 · qdrant
L4Knowledgerag · nl2sql
·Field memoryqdrant · shared
·Daily logstemporal
Chapter 02 The family
One engine · many businesses
↗  Powered by Automatos AI

Build the engine once.
Sell it many ways.

Each product has one buyer, one promise and one button. The OS underneath is the same for all of them, so a new business costs a front end, not a platform. Every one carries Powered by Automatos AI.

Automatos Studio

Live
For
Owners and small teams
Promise
Run your business in your brand

The control panel for the OS: Command Centre, board, documents, brand kit, socials and the marketplace. Live today as SaaS; also runs locally as open source.

Automatos Studio ↗

Academy

Live
For
Learners
Promise
Free certification prep, with a tutor

Courses and a tutor at academy.automatos.app, with a mobile app on its way to the stores.

The Academy ↗

Market Intelligence

Live pilot
For
Crypto traders
Promise
Signals with receipts

The cockpit, plans, replay and a trade journal at markets.automatos.app. Free during the pilot. Not financial advice.

Market Intelligence ↗

Widgets

Built
For
Any website
Promise
Your site, AI-driven, in your brand

Chat and blog widgets that run on the OS and are managed in Studio. This site's field notes are served by one.

For developers →

Shopify app

In development
For
Store owners
Promise
Your store, AI-driven

A working Shopify app with a theme extension. The App Store listing follows once setup on install is fully automatic.

Ask about early access →

Enterprise

Coming
For
Regulated firms
Promise
The OS in your own cluster

A Helm chart exists and is tested in CI. Single sign-on and cloud plugins come next.

See the editions →

Partners

Partner
For
Platforms and agencies
Promise
Offer the OS to your own customers

BudStacks customers can add Automatos to their plan, and we're working with a few Shopify partners on their merchants' stores.

Become a partner →

Your app

API · MCP
For
Developers and companies
Promise
Your own front end on the same OS

A voice assistant, a bot in a chat channel, or your own product, all over the same API.

Start building →
Chapter 03 Editions
Three ways to run it
↗  One OS · one Studio

Local, SaaS or Enterprise.
The same OS.

The same engine and the same Studio, wherever it needs to run.

Local

Open source

Free, on your own machine, Apache 2.0 and public on GitHub. Agents can work on your own Claude Code or other CLI subscription. docker compose up and it's yours.

Get the code ↗

SaaS

Live

Hosted Automatos Studio. Nothing to install: sign in, upload a logo and tell Auto what you need.

Automatos Studio ↗

Enterprise

Coming

The same OS in your own Kubernetes cluster, for firms that can't send data out.

  • Today A Helm chart, linted and tested in CI. S3 storage and Bedrock models on AWS. A Prometheus, Grafana and Loki monitoring stack.
  • Next Single sign-on (OIDC), Azure plugins beyond Azure OpenAI, and the monitoring stack packaged with the chart.
  • Compliance Our EU AI Act posture, article by article →
Book a proof of concept →
Chapter 04 Not another Jarvis
Every line on the right is in the code today
↗  Not on a roadmap

A Jarvis is an app.
We're what apps run on.

Plenty of AI operating systems are a chat window and a voice. Here's what's underneath this one.

AspectA typical AI “OS”Automatos
What it isA chat window in front of a modelA headless OS with an API. Studio, widgets, chat channels and our own products are all interfaces to it
OutputAnswers you copy somewhere elseInvoices, letters, spreadsheets, social posts and video, rendered from your brand kit and saved with a share link
ControlDoes whatever the model decidesA board of tickets. Money and publishing need a person's yes, and an approval is tied to the exact content that was approved
ArchitectureOne app17 feature modules whose boundaries CI enforces. Swap models today
BusinessOne userWorkspaces, roles, plans and render quotas, and partners who offer it to their own customers
Where it runsTheir cloudLocal and open source (Apache 2.0), SaaS live today, and your own Kubernetes cluster
ProofA demo videoOver 14,000 backend tests in CI, and a nightly harness where customer personas grade the real outputs
InterfacesOneStudio, website and store widgets, Claude Code sessions, the Academy, Market Intelligence, and chat channels: WhatsApp, Telegram, Slack and Discord today
Chapter 05 Developers
The API, MCP, the widgets and the source
↗  docs.automatos.app
/.01API

One API for everything Studio does.

Agents, tasks, documents, knowledge and socials, over the same API the product uses. Build your own front end on it.

Read the docs↗
/.02Open source

Fork it, audit it, run it.

Apache 2.0: the orchestrator, the frontend and the services. Next.js, FastAPI, Postgres and S3, with your own model keys.

GitHub↗
/.03MCP & widgets

Plug in from anywhere.

Agent sessions call the OS's tools over MCP. Chat and blog widgets put it on any website with one snippet.

DeepWiki↗
Chapter 06 Lego, for a business
Every piece reusable
↗  A front end, not a rebuild

BudStacks is
just the start.

Every piece of the OS can be reused, so every new way to reach customers is a front end and a partnership, not a rebuild.

Partners

White-label inside other platforms

BudStacks users can add Automatos to their plan, and we're working with a few Shopify partners. Any platform whose customers run small businesses can do the same: their brand, our OS.

Verticals

A package per trade

A café, a salon, an accountant, a store. One install brings the agents, playbooks, templates and setup questions that trade needs.

Distribution

The app stores

The Academy app for learners, and the Shopify App Store for stores once our app is listed. Distribution we don't have to build.

Interfaces

Your own front end

A voice assistant, a screen on the wall, a bot in WhatsApp or Telegram, or a company's own product, all over the same API.

Enterprise

The OS in your cluster

A Helm chart exists today. Single sign-on and cloud plugins come next, for firms that can't send data out.

Community

A marketplace people build for

People publish agents and playbooks, and soon templates; others install them in one click. Auto is the guide.

Get started

One OS.
Pick your door.

Run your business in Studio, learn in the Academy, trade with Market Intelligence, or build your own interface on the open-source OS.

Find your door