Open Platform

Say what you want.
Watch it get built.

A software platform with an AI build crew. Describe a tool in plain words — the crew builds it, tests it by clicking through it in a real browser like a person would, and puts it live at a web address. On hardware you own.

Your ideas go in as sentences; working tools come out as URLs.

Start building How it goes

How it goes

One real session, start to finish. It plays on its own — or take the wheel.

Make an org.

An org is a company, a team, a garage. Yours starts empty.

git.open-platform.sh

New organization

Nameshopfloor

Everything you build lives here. People you add see all of it.

Create organization

Make a repo. A repo is just an app.

Give it a name and one honest sentence about what you want. That sentence is the spec.

git.open-platform.sh/shopfloor

New repository from template: app-template

Namejobs-board
DescriptionA board for tracking cars through the shop — waiting, in progress, done. Big and readable from across the garage.
Create repository

Go chill.

The crew works in the open — pull requests, issues, CI runs. You can read every bit of it, or not.

git.open-platform.sh/shopfloor/jobs-board
  • crewopened PR #1 — v1: jobs-board
  • builderpushed the data model, then the API, then the screen
  • previewup at pr-1-jobs-board-shopfloor.open-platform.sh
  • validatoropened the preview in a real browser, added a car, moved it, reloaded — it stuck
  • checksgreen — merged

It's live.

At a web address. No build you ran, no server you configured, no laptop it only works on.

jobs-board-shopfloor.open-platform.sh

Waiting

  • Blue Civicoil + filter
  • Red F-150front brakes

In progress

  • Silver Camryalternator

Done

  • White Transitannual inspection

You gave it one sentence. Of course it's not perfect.

So say the next sentence. An issue with the agent-work label is the entire act of software maintenance here.

git.open-platform.sh/shopfloor/jobs-board

New issue jobs-board

TitleAdd a waiting-on-parts column.

Labels agent-work

Create issue

Chill again.

Same loop, no ceremony. Nobody had to be free on Thursday.

git.open-platform.sh/shopfloor/jobs-board
  • crewpicked up issue #2 — Add a waiting-on-parts column.
  • builderopened PR #3, pushed one column and the move between them
  • previewup at pr-3-jobs-board-shopfloor.open-platform.sh
  • validatorput a car in the new column and took it back out
  • checksgreen — merged

It changed.

Same address, same board — a fourth column, because someone asked for one in plain words.

jobs-board-shopfloor.open-platform.sh

Waiting

  • Blue Civicoil + filter

Waiting on parts

  • Red F-150front brakes

In progress

  • Silver Camryalternator

Done

  • White Transitannual inspection

Oh — and an org will grow multiple apps that work together.

Same accounts, same rules, same address book. The second app is easier than the first.

git.open-platform.sh/shopfloor
  • jobs-boardCars through the shop, on a screen you can read from across the garage.
  • quotesEstimates out, approvals back, nothing lost in a text message.
  • intakeThe form at the front desk. It knows the cars the other two know.

That's the whole thing.

Start building

Rather read it than watch it? A day with your crew Questions people ask

Under the hood, briefly

Everything is a commit.

Forgejo is the whole control plane. The crew's work is pull requests, issues, and CI runs — in the open, reviewable, auditable. Nothing happens off the books.

The crew is contained.

Builders run in a non-privileged, isolated CI pool with no path to your machines or your credentials. A cold-start gate grows a complete platform in CI before any change to the platform itself can merge.

It's yours.

Your hardware, your domain, your keys, your data. No vendor to outgrow — clone the source and grow your own.

It reproduces.

Mitosis: a platform can seed a daughter platform — fresh keys, its own identity, lineage recorded — like buying the CD. It’s yours; hand someone else the same power.

Architecture Security Model Platform Internals

Own one

In one command.

bunx open-platform-ts up

One Bun process that is a whole platform — git hosting, identity, CI, app deployment, and the build crew. It boots on your machine in about a minute and prints your card: your URL, your logins, your first app one curl away. MIT, on npm.

open-platform-ts on npm Source

The full-size one.

git clone https://git.open-platform.sh/open-platform/mitosis
cd mitosis
CLAUDE_CODE_OAUTH_TOKEN=<your-token> nix run .#up

That's the whole install — and it's what this website runs on. Thirty to sixty minutes later it prints a YOUR PLATFORM card — your domain, your logins, how to reach everything.

Grow Your Own Platform

One idea at two sizes. What you build on one can move to the other when you're ready.

Prefer it delivered and run for you? espodev build production implementations — on your servers, and they hand you the keys.