This platform turns issues into shipped software. You describe what you want in an issue. An AI crew builds it, reviews it, and releases it to a live URL. Everything runs through the Forgejo you are reading right now. Forgejo enforces your permissions on every action, and the crew runs inside the platform's own cluster — never on your machine. Start at Build Your First App, or pick a door below.

Not a developer? Start with The Big Idea — the whole platform in plain language, no jargon, and everything you need to build your first thing. The technical pages below will still be here when you're curious.

The loop

You describe software in issues. The build crew builds it in pull requests. Every PR gets a real preview environment: its own database, its own URL, its own TLS. A reviewer signs into the preview with a real browser and posts one verdict. On ✅ Ship it, the PR merges and your app releases to a public URL.

You steer the whole time with plain comments and labels. Comment on a PR to redirect the builder mid-build. Add the agent-work label to any issue to queue it. That is the entire interface — no dashboards to learn before your first ship.

What lives where

Four URL shapes carry the whole platform.

Surface	What it is
https://git.open-platform.sh	Everything. Repos, issues, PRs, CI, packages, secrets, this wiki — Forgejo is the whole control plane.
https://mcp.open-platform.sh/mcp	Your agent's door. Point any MCP client (Claude Code, Cursor, ...) here to build on this platform through tool calls.
https://grafana.open-platform.sh	The meters and levers: fleet allocation, spend burn, and the flow-control forms. The admin login is on your YOUR PLATFORM card.
https://<app>-<org>.open-platform.sh	Your software. Every released app gets this URL. Every open PR gets https://pr-<N>-<app>-<org>.open-platform.sh.

Start here

Pick the door that matches your goal.

1. Build Your First App — click "Use this template" on open-platform/app-template. The repo name and description ARE the spec. The first pull request opens within a minute. Ten minutes to a live URL.
2. Create an org and let it plan — create an org whose description is a product brief. The platform files a seed issue for you. Arm the plan-org label on that issue. A planner designs an integrated suite with an ownership map and a dependency-wired roadmap. The crew then builds it in waves.
3. Connect Your Agent — run claude mcp add --transport http plat https://mcp.open-platform.sh/mcp. Authenticate through Forgejo when prompted. Your own harness gets the full tool surface: create apps, file issues, release, query logs.

The rest of the wiki

• For everyone — The Big Idea, A Day With Your Crew, Questions People Ask
• Experience — Build Your First App / Building with Issues / Routines / Orgs and Planning / Preview Environments / Connect Your Agent
• Operate — Steering the Fleet / Users Teams and Access / Secrets and Config
• Under the hood — Architecture / Platform Internals / Security Model / CI and Builds
• Grow — Grow Your Own Platform / Reference

This wiki grows on the platform it describes

This platform can clone itself onto new hardware, and this wiki ships inside the seed. When a platform reproduces, the daughter is born with her own copy of these pages, with every link rewritten to her own domain. The flagship instance is open-platform.sh, run with support from espodev; the platform you are reading belongs to whoever grew it. Documentation here is an organ of the organism, not an appendix — see Grow Your Own Platform.