Seed

Open source · MPL-2.0

Software that
grows itself.

Plant a Seed and tell it what to become. It writes the code, tests it, lets you try it on a copy of your data, and only then goes live, as a new generation you can always roll back.

curl -fsSL https://raw.githubusercontent.com/paezao/seed/main/install.sh | sh
seed new acme-ops -e OPENROUTER_API_KEY
Get started See how it grows
Become our team's release calendar, with on-call and uptime.
Evolutionevolving
Team release calendar
Planning · 1 of 8$0.00
Generation 2 is live
✓ 18 tests pass

How it grows

From a seed to your app,
one generation at a time.

  1. Plant

    seed new acme-ops gives you a folder with a kernel, a database and an empty app, in its own container.

  2. Ask

    Tell it what to become in chat, or point at part of the app. It plans first, and asks before guessing.

  3. Try

    It builds and tests the change in a sandbox, then lets you try it on a copy of your real data.

  4. Live

    Apply it: a new generation, a git commit, with your data backed up first. Roll back any time.

Point and ask

Show it what to change.

A little seed lives in the corner of your app. Hover it, drag a box around anything, and say what should change. Your Seed gets a picture of exactly that area, and your words. Nothing is sent until you confirm it.

  • Wears your app's colours and font
  • Only you see it; visitors never do
  • The picture is drawn in your browser
ops.acme.dev
Acme OpsNew release
This week5 releases · 1 freeze · on-call: Sam, then Priya
MonRelease 4.2On-call
TueDesign reviewFreeze
WedRelease 4.3
ThuOn-callRetro
FriHotfixLaunch: Atlas
Deploys24Uptime99.98%Incidents2

Try before it's live

See it on your real data. Then decide.

Every change runs beside the live app, on a copy of your data. Click around, then apply it, ask for changes, or throw it away. Everyone else keeps seeing the live version until you say so.

  • Its own database, no secrets, private network
  • Ask for changes in your own words
  • Get a notification when it's ready
ops.acme.dev
Acme OpsNew release
This week5 releases · 1 freeze · on-call: Sam, then Priya
MonRelease 4.2 · On-call
TueDesign review · Freeze
WedRelease 4.3
ThuOn-call · Retro
FriHotfix · Launch: Atlas
MonRelease 4.2On-call
TueDesign reviewFreeze
WedRelease 4.3
ThuOn-callRetro
FriHotfixLaunch: Atlas
Previewing: Release calendar as a week a copy of your dataApply

Generations

Every version is kept. Go back any time, data too.

Each change is a commit and a generation. Your data is copied before every one goes live, so a rollback can bring back the data of then as well.

1Initial seed
2Release calendar
3On-call rota
4Uptime cards
5Auto-deploy
6Back to 4, with its data

Everything a living app needs

The careful parts come built in.

The kernel does the boring, careful work, so every app a Seed becomes gets it for free.

Looks after itself

Notices errors and crashes, restarts what fell over, finds the cause and fixes it, with a test that proves it.

Knows what it costs

Every model call counted. Watch a change's cost tick up live; set a monthly budget.

Tells you when it needs you

On your laptop and phone, when a change is ready to try or it has a question.

Locked down by default

Your app has no network except HTTPS to hosts you approve, with only the secrets you grant. Risky actions wait for you.

Routines

Tasks it runs on a schedule and reports on, and jobs your app runs.

Updates itself

Signed kernel releases, installed from its control plane. If one fails to start, it rolls back.

The control plane

Its own admin, built in.

Chat, plans and progress, generations, health, spending and backups: everything about your Seed, in one place only you can open.

Under the hood

Careful by construction.

  • One container per Seed, with its own PostgreSQL, or an external one with DATABASE_URL.
  • Every change built and tested in a sandbox with a scratch database. Your live data is out of reach.
  • A kernel boundary: the app it becomes can't change the parts that keep it safe.
  • Git is the source of truth. Every generation is a commit; history is never rewritten.
  • Any model through OpenRouter, with your own key. Keys are passed at start, never stored.

Architecture → · Security →

Yours

Your app is yours.

Seed is open source under the MPL-2.0. The app your Seed becomes is yours, under the MIT license: take it anywhere. A Seed runs anywhere Docker does, from your laptop to a VPS or Kubernetes, with a volume and optionally an external database.

Hosting a Seed →

Put it online

Your own server, one command.

Any Linux server with Docker: a VPS from Hetzner, DigitalOcean or AWS, or a box at home. One command installs what's missing, starts your Seed with HTTPS, and prints where to sign in. No domain yet? It gets one from sslip.io.

Host on a server →

curl -fsSL https://raw.githubusercontent.com/paezao/seed/main/deploy/vps/setup.sh | sudo OPENROUTER_API_KEY=sk-or-… sh
  • HTTPS from Let's Encrypt, renewed by Caddy
  • Its sandboxes work as on your laptop
  • Your server, your data, your model key

Plant one.

curl -fsSL https://raw.githubusercontent.com/paezao/seed/main/install.sh | sh

Linux, macOS, or Windows with WSL2. Needs Docker. Or build it yourself: git clone https://github.com/paezao/seed && cd seed && make install