From prompt to production.
AIOS turns natural language into deployed, monitored, self-evolving software. Type a sentence; ship a system.
Designs.
Architects whole systems from a single sentence.
Builds.
Ships type-safe code with tests and deployment.
Defends.
Monitors, recovers, and adapts — for as long as it runs.
The toy era of prompt-to-app is over.
Current tools generate code. They don't generate systems. They render a screenshot of an idea, then disappear when you ask for tests, monitoring, type safety, deployment, or recovery.
AIOS is built around the assumption that production is the only state worth shipping to. Every prompt produces a system that runs, monitors itself, and recovers without supervision.
Working software. Live URL. Monitored from minute zero.
Every project comes out the other side as a deployed system: type-safe code, a test suite, a hosted URL, an uptime monitor, and an automatic recovery path. You receive an artifact you can use the moment generation completes.
One prompt. One system.
No labels. No phases. No machinery on display. Watch the prompt go in and the system come out.
Prompt
Working
Deployed
Five things AIOS does, every time.
Specifies the system.
Turns the prompt into a specification: schema, data model, contracts, acceptance criteria.
Writes the code.
Type-safe code end-to-end. No scaffolds, no stubs, no placeholder comments.
Tests every contract.
Synthesizes the test suite, checks contracts, runs the suite before any deployment is attempted.
Ships to a live URL.
Hosted URL with health checks, logs, metrics, and a rollback path baked in.
Evolves the system.
Monitors, recovers, and evolves the system against new requirements without a rebuild.
The system defends itself.
Every generated system runs behind continuous defense: input validation, runtime guards, anomaly detection, and automatic rollback. Failures get traced to a root cause and fixed without human intervention in the common cases.
SLA
Live99.95% deployed-system uptime on Builder and above. Custom commitments at Enterprise.
SOC 2 Type II
Q3 2026Audit kicks off June 2026 with Drata. Bridge letter published the day it's signed.
Encryption
LiveAES-256 at rest. TLS 1.3 in transit. Customer prompts encrypted before they're written to disk.
Auto-recovery
LiveAnomaly detection triggers automatic rollback within 90 seconds. Root cause traced to the failed input.
Pay for what runs.
Three things meter: planning tokens (free up to a quota), build credits (per generation), monthly deployment (covers hosting, monitoring, and SLA).
Starter
- 100k planning tokens
- 25 build credits
- 1 deployed project
- Community support
Builder
- 1M planning tokens
- 200 build credits
- 5 deployed projects
- Priority email support
- 99.9% SLA
Team
- 5M planning tokens
- 1,000 build credits
- 25 deployed projects
- Slack support channel
- 99.95% SLA
Scale
- Unlimited planning
- 5,000 build credits
- 100 deployed projects
- Dedicated solutions engineer
- 99.95% SLA
Enterprise
- Unlimited everything
- Self-host option
- Dedicated SLA
- SSO + audit log
- Direct line to engineering
The shape of the API.
A streaming SDK. Stages emit as they happen. project.url resolves when the system is live.
import { Ominus } from "@ominus/sdk"; const ominus = new Ominus({ apiKey: process.env.OMINUS_KEY }); const project = await ominus.projects.create({ prompt: "A team retro tool with Slack integration, RBAC, and weekly digest emails.", tier: "builder", }); for await (const event of project.stream()) { console.log(event.stage, event.status, event.elapsed); // planning complete 2.4s // generating in_progress 18.1s // verifying in_progress 4.3s // deploying in_progress 12.7s // ready complete 38.5s } console.log(project.url); // → https://team-retro-9f2a.ominus.app
Honest answers.
What's shipped today?
The core generation engine runs end-to-end. A small set of product-layer features is in active development before public launch. Specific milestones land in the public changelog.
How does this differ from Cursor or Lovable?
Cursor edits files alongside a developer. Lovable scaffolds a frontend. AIOS produces a complete deployed system from a prompt — including the test suite, the deployment, the monitoring, the recovery path, and the SLA.
What language are generated systems in?
TypeScript, end-to-end. Other targets are on the roadmap.
What happens when the AI is wrong?
Generated systems are validated before deployment, monitored after, and rolled back automatically on anomaly. You don't need to babysit them.
Can I self-host?
Enterprise tier, yes. Lower tiers run on Ominus infrastructure.
What's the SLA?
99.9% generation availability and 99.95% deployed-system uptime on Builder and above. Enterprise negotiates custom commitments.
Who built this?
One founder, in active development. Read the manifesto for the why.
When does the Console open?
Now. Click Start building — planning runs free.
Start building.
Your first prompt is free. Planning runs end-to-end with no card. Build credits start the moment you ship.