Show HN: Supapool – a Supabase per coding agent in ~400 ms

In one line

Full, isolated Supabase instances for coding agents in 1 second.

Opening excerpt

npx @supapool/cli run — npm run dev Wrap any command. Supapool leases a clean instance, injects its credentials, keeps it alive, and releases it when the command exits.

npx @supapool/cli login npx @supapool/cli run — login opens GitHub sign-in and saves an API key to ~/.config/supapool/config.json . run does the same sign-in on first use, so most people never run login directly.

run acquires a clean instance, applies every .sql file in supabase/migrations in filename order, starts your command with the instance credentials in its environment, renews the lease while the command is alive, and releases the instance when it exits. Your repository’s environment files are never modified.

Every instance is a lease with a TTL, 30 minutes by default. The CLI renews it every 5 minutes while your command runs. When the command exits, or if the process dies and renewals stop, the lease expires and the slot is wiped and returned to the pool. Nothing you store in an instance survives release, so treat every run as disposable.

(Excerpted from the original; full article via the source link below.)

This story hit the Hacker News front page today (25 points / 4 comments, via supapool.io). Our Tech Radar aggregates daily signals on AI engineering, backend architecture and DevOps — browse the related services and further reading below, or get in touch with our team.