Automated Incubation Complex
Every product your studio ships, on one board.
AIC reads your repos, releases and feature ledgers every night and shows where each product stands. You run it yourself, on your own database. Nobody writes a status update.
- Projects watched
- 1
- one config line each
- Ledger rows
- 24
- 0 releases · 0 deployed
- Latest release
- none yet
- waiting for the first collect
The problem
The facts are in the repos. The status report is somewhere else.
Status updates go stale
Someone writes where each product stands, and by Friday it is wrong. The facts are already in the repos; nobody should copy them out by hand.
Dashboards that guess
A number that looks right and is not, or a job that failed without saying so, is worse than no number at all.
How it works
Three files and a nightly job.
Step 1
Add one line per project
Each product is one entry in config/projects.yaml: its repo, its site, what to look for on the page.
Step 2
Keep a ledger in each repo
A short features file lists what is planned, in progress and done, and which version shipped it.
Step 3
Let the hub collect
Every night, and on every release, AIC reads the repos and updates the board, the change log, readiness and the weekly digest.
Features
Numbers you can check, and a board that keeps itself.
Every number shows its source
Each collect is logged step by step. A failed step is named with its reason, and the day's raw snapshots are kept as plain JSONL files you can read without the hub.
Health checks that explain themselves
Each production site is probed for the text it should show. When one is down, the board says why: no answer, HTTP 502, or the expected text is missing.
Feedback from your sites, in one queue
Your sites post what people send with a per-site key. You triage it as open, in progress or closed, with the context laid out in plain rows.
A board you arrange
One card per product with its latest release, commits this week and completion. Drag cards, or use the arrow keys, into the order you read them.
Readiness from the ledger
Done against not done for every product, grouped by area, so you can see what is left before a release.
Ideas in, issues out
Capture an idea from the board or an API call, move it through inbox, triaged, doing and done, and send it to the repo as a GitHub issue.
A weekly digest written for you
Once a week the model writes a short review from the numbers alone and posts it to your Discord channel.
Pricing
Free, and yours to run.
Self-hosted
$0
MIT-licensed. Every feature, no seat count, no trial clock. You pay your own database and host, which fit in free tiers for a small studio.
FAQ
Before you set it up.
- What do I need to run it?
- A Postgres database (Neon's free tier works; PGlite works on a laptop), a host for a Next.js app, and a GitHub token that can read your repos.
- Does it send my code anywhere?
- No. The collect reads repository metadata, releases and the ledger file. The weekly digest sends counts, not code, to the Claude API, and only if you set a key.
- Can my team sign in?
- Not yet. Today there is one owner account, with a password or a passkey. Team accounts are not built.
- Can I import from another tool?
- There is no importer. Projects come from the config file and features from each repo's ledger, so moving in is mostly writing those two files.
- What does it cost?
- Nothing. AIC is MIT-licensed and you host it yourself; you pay only for your own database and hosting.
Ship log
What shipped lately.
Nothing recorded yet. The first collect fills this in.
Follow what ships here.
Every release this hub sees, as a feed for your reader.