The notebook demo
Works on your laptop. Dies the first time a customer hits it.
With Theo: `git push` → live URL in minutes, on the same stack as production.
Chat. Build. Deploy. From idea to live agent in minutes. Open-source AI chat, frameworks, and a managed runtime where your agent actually runs. Your code, your repo.
~4 min median deploy · Apache-2.0 · no credit card · your code, your repo
No credit card. Free tier is permanent — no expiry, no auto-upgrade.
See it in action$ curl -fsSL https://install.usetheo.dev/theo-code | shbrew install --cask theo-code$ git push origin main Theo deploys automatically: Building api... [24s] Building web... [18s] Deploying... [15s] Live: api → https://example-my-saas-api-production.usetheo.dev web → https://example-my-saas-web-production.usetheo.dev
When we say "AI agent", we mean a backend process that listens, decides, acts, and keeps an audit record — running on a schedule or on demand. Not a chatbot. Not a browser plugin. Three real examples shipped on TheoCloud: a worker that reads your GitHub PRs and posts a summary to Slack · a job that watches a shared inbox and files invoices into your ERP · a nightly routine that reconciles bank statements against accounts payable.
Most agents look magical in a notebook and dissolve the moment they meet real traffic, real auth, real logs. Theo is the layer in between.
Works on your laptop. Dies the first time a customer hits it.
With Theo: `git push` → live URL in minutes, on the same stack as production.
No logs, no rollback, no record of what changed. Someone is on call all weekend.
With Theo: structured logs, ~3-second rollback, platform audit log — from day one.
The agent talks to models, not to your ERP, your bank, your inbox.
With Theo: real backend in your language — Postgres, queues, SDKs in 7 stacks.
Theo is the Agent Production Platform — the layer most agents skip, and most teams pay for in outages.
Open-source AI chat in your terminal or Desktop. Plan / Code / Infra modes.
"I need an agent that reconciles the bank against our ERP every Friday at 6 PM."
TheoCreate scaffolds in 7 languages. TheoKit is the Next.js framework where your agent lives.
Full backend: Postgres, workers, and scheduler — not a preview, not a mock. Apache-2.0, in your repository.
One git push puts it live on the internet. Live URL in ~4 minutes for a typical Node/Postgres app. Larger monorepos take longer; cached rebuilds are faster.
git push, or theo deploy. Signed images, ~3s rollback, audit log included.
LLM-powered automations wired to your systems. Run 24/7 with audit trail. Not chatbots, not previews — real code in your repository. ~4 min is the deploy; ~1 week is the full automation, integrated and live. Different speeds for different things.
Connect your bank, your ERP. Theo reconciles paid invoices against received NFs every Friday at 6 PM. The dashboard tells you what matched, what didn't, and why.
Example: a weekly bank-vs-ERP reconciliation that takes ~4h manually. Payback math at $29/mo Pro: ~2 weeks if the analyst's time is worth $30/h+. Your numbers will differ.
npm create theo@latest30 CVs per role → top-5 ranked by your criteria, with a summary for the hiring manager. LGPD-aware (consent + retention), Gupy/Greenhouse/Lever-friendly ingest. Reasoning is auditable for compliance.
Example: 30 CVs/role, first interview scheduled in ~24h. Compares to typical weekly manual triage. Volume and SLA will vary.
npm create theo@latest10 supplier proposals normalized into one matrix. Compare on the criteria that matter, decide, store the audit trail.
Example: 10 proposals in a comparable matrix in ~1h. Compares to a manual spreadsheet + emails for 1 week. Your approval flow adds time.
npm create theo@latestTheoCode writes it. TheoKit or TheoCreate shape it. TheoCloud ships it. Your repo, your domain, no lock-in.
Real backend — Postgres, queues, scheduler — not a preview, not a simulation. Plan / Code / Infra in TheoCode, Next.js framework in TheoKit, scaffolds in 7 languages from TheoCreate. All Apache-2.0, all in your repository.
Example: AI agent with auth + billing + dashboard in production in ~1 week. Compares to a 4-6 week manual bootstrap. Speed varies with complexity.
npm create theo@latestFour pillars, one commercial runtime. Your code, your repo, your domain — operated for you, or self-hosted under commercial license.
`git push` to live URL in minutes, on Node, Go, Python, Rust, Java, Ruby, PHP, or Next.js.
Auto-detect framework via Railpack · PR previews · signed images by default
OpenTelemetry spans per LLM call, per tool call, per sub-agent. No manual instrumentation.
Native export to Datadog, Splunk HEC, Elastic, S3, Prometheus federation
~3-second rollback to any prior build. Canary plus analysis on every deploy from Pro tier up.
Signed container images · build-level component report (SBOM) · 99.9%+ SLA
Per-role permissions (Admin · Deploy · View), platform audit log, SBOM per build, project isolation by default.
SSO / SAML 2.0 · SCIM 2.0 · DPA on request · public security disclosure
$ git push origin main Theo deploys automatically: Building api... [24s] Building web... [18s] Deploying... [15s] Live: api → https://example-my-saas-api-production.usetheo.dev web → https://example-my-saas-web-production.usetheo.dev
Theo is the Agent Production Platform — Chat (TheoCode) + Build (TheoCreate / TheoKit) + Deploy (TheoCloud) in one ecosystem. Compared side-by-side with the deploy/coding tools developers already use.
| Capability | Theo | Vercel | Railway | Cursor | Internal infra team |
|---|---|---|---|---|---|
| Agent runtime (long-running, scheduled jobs) | Partial (Edge fns, no long-running) | yes (you build it) | |||
| Coding agent integrated in the workflow | yes (TheoCode, Plan/Code/Infra) | yes (Cursor editor) | |||
| Open-source funnel (Apache-2.0) | yes (TheoCode, TheoCreate, TheoKit) | n/a | |||
| Audit log, signed images, SBOM by default | Partial | Partial | n/a | yes (you build it) | |
| Self-host option | yes (commercial license) | ||||
| Polyglot scaffolds (Node, Go, Python, Rust, Java, Ruby, PHP, Next.js) | yes (19 templates via TheoCreate) | Frontend-first | Partial | n/a | yes (you build it) |
| Time to first deploy | Minutes (chat + scaffold + deploy) | Minutes (frontend) | Minutes | n/a (editor only) | 3–6 months bootstrap |
| Where it wins | Full agent cycle in one ecosystem | Frontend + Edge at global scale | PaaS DX for general apps | In-editor AI for any codebase | Total control over every line |
Compare Theo vs:
| Capability | Theo | Vercel |
|---|---|---|
| Agent runtime (long-running, scheduled jobs) | Partial (Edge fns, no long-running) | |
| Coding agent integrated in the workflow | yes (TheoCode, Plan/Code/Infra) | |
| Open-source funnel (Apache-2.0) | yes (TheoCode, TheoCreate, TheoKit) | |
| Audit log, signed images, SBOM by default | Partial | |
| Self-host option | yes (commercial license) | |
| Polyglot scaffolds (Node, Go, Python, Rust, Java, Ruby, PHP, Next.js) | yes (19 templates via TheoCreate) | Frontend-first |
| Time to first deploy | Minutes (chat + scaffold + deploy) | Minutes (frontend) |
| Where it wins | Full agent cycle in one ecosystem | Frontend + Edge at global scale |
*Where each competitor wins is stated honestly. None of these tools is bad — they solve a different shape of the problem. The question is whether you want to compose them yourself or have one ecosystem ship the full cycle.
Theo is the only one that ships the chat, the build, and the deploy as one runtime. The rest you compose.
Real automations across finance, people, procurement, support, knowledge, and ops. Every one starts from the same command, on any of the 19 templates.
Pull bank statements and ERP postings nightly. Match what matched, flag what didn't, log the reasoning.
Example: ~4h weekly manual job → nightly automated with audit trail.
npm create theo@latestIngest CVs from Gupy, Greenhouse, or Lever. Rank top-5 against your criteria with a summary the hiring manager can read in 60 seconds.
Example: 30 CVs/role → first interview scheduled in ~24h. LGPD-aware.
npm create theo@latestTake 10 supplier PDFs in 10 different shapes. Hand back one comparable matrix and a recommendation you can audit.
Example: 10 quotes normalized in ~1h vs 1 week of email back-and-forth.
npm create theo@latestRead every inbound ticket, classify by priority and category, draft the first reply, and route it. The human reviews and sends.
Example: 500 tickets/week → median first-touch under 5 min, escalations down.
npm create theo@latestIndex Notion, Confluence, or your repo. Answer in your team's voice, with citations. Logs every question and answer for audit.
Example: every 'where is the X policy' question answered in <10s with sources.
npm create theo@latestWatch a shared inbox. Extract invoice fields, validate against PO, file into ERP, alert on exceptions. Audit trail per email.
Example: ~80% of invoices processed without human touch; exceptions land in a clean queue.
npm create theo@latestNeed a use case not listed here? Start from any of the 19 templates — your shape, your stack, your repo.
Each example is a real shape teams have built; numbers describe one shipped version, not a benchmark. Volume, latency, and savings will vary with your data, team, and provider.
Every plan includes auto-deploy on push, monorepo support, encrypted secrets, signed containers, and instant rollback — same experience across all tiers.
An environment = isolated deploy with its own URL, secrets, and database. dev/staging/prod count as 3.
Validate your idea
Solo professional
A whole team or department
Self-host + SLA
Free tier is permanent. Pro is $29/mo. Team is $99/mo. Pay only when the ROI shows up.
No card required. Cancel anytime on paid tiers.
$ curl -fsSL https://get.usetheo.dev | sh