01
Specs
What you are building, scoped tightly enough to finish.
Planned · not yet available
Ship software without rebuilding the same foundation
Auth, billing, data, deploys, and observability handled, so a new tool is a week rather than a quarter. SoftwareOS is the build half of AIOS — planned from the stack this platform already runs on.
SoftwareOS is not built yet. This page documents the model it will ship against, and your membership will include it when it does.
9
departments in the model
0
shipped so far — planned module
1
membership covers it at launch
9 departments planned
The first two weeks of every project are the same two weeks.
Auth, billing, a database, a deploy pipeline, and somewhere to read the logs. SoftwareOS is planned to hand those over already solved.
02
Scaffolding
A working app on the same stack this platform runs on, not a blank repo.
03
Auth & billing
Sign-in, subscriptions, and entitlement wired from the first commit.
04
Data
Schema, migrations, and row-level security as the default rather than a task.
05
Deploys
Edge deploys with preview builds that never touch production traffic.
06
Observability
Logs, errors, and the queries you actually run during an incident.
07
Agents
Scheduled and event-driven workers, with the same auth as everything else.
08
Docs
Written from the code so they are wrong less often than the alternative.
09
Support
Bug reports and user messages attached to the release that caused them.
Why SoftwareOS
Dogfooded before it is a product.
This module is the least speculative of the planned three, because AIOS itself is already built on exactly the stack it would hand you.
01
The stack is already in production
Cloudflare Workers, Supabase with row-level security, Stripe entitlement, R2, and an MCP server — running this platform today, not chosen from a blog post.
02
Entitlement is the hard part
Auth is easy and billing-driven access is not. That machinery exists here and is what SoftwareOS is planned to hand over.
03
Agents are first-class
Scheduled workers and AI agents are a department, not a bolt-on — because most of what small software does now is run on a schedule.
04
Included when it ships
Part of the same subscription, on the same login, with the same integrations as every other module.
Questions
Before you ask.
Can I build on AIOS today?
Not through a SoftwareOS surface — it is not built. What does exist today is the MCP server and the members-only Claude Code skill packages, which let you drive AIOS itself programmatically.
Is this a hosting product?
No. It is planned as the scaffolding, auth, billing, data, and deploy path around the code you write, on infrastructure you own accounts for.
Why should I believe the stack claims?
Because you are reading a page served from it. AIOS runs on Cloudflare Workers with Supabase, Stripe, and R2, and SoftwareOS is planned to hand over that same arrangement.
When will it ship?
No committed date. It is the most plausible of the three planned modules, since the pieces already run in production — but plausible is not shipped.
One platform
SoftwareOS is one of eight systems.
Every module shares the same login, the same subscription, and the same integrations. Add the ones you need as the work grows.
Not built yet — but you are reading a page served by the stack.
Your AIOS membership will include SoftwareOS when it ships. Nothing extra to buy.
Sign in →