A demo of how far the Neon Open API takes you. Projects, branches, monitoring, SQL editor, tables and settings — all rebuilt on the same REST API any agent, platform or app can call.
— A hastily produced software clone that imitates the surface features, design language, or “vibe” of an existing product while lacking architectural rigor, security hardening, or production readiness.
This is exactly that: a faithful clone of the Neon console, rebuilt from scratch on top of the Neon Open REST API. No private backend, no special access — every project, branch, compute control and SQL query you see here runs through the same public endpoints any developer, agent, or platform can call.
Read the story: “I Slop Forked Neon. You Should Too.”Agents are changing how we build software. They’re far better at using APIs, CLIs, and MCP servers than they are at clicking through a dashboard — give an agent an API key and it can provision resources, inspect state, and manage infrastructure on its own, no UI to drive.
So the best developer platforms are becoming agent-native, exposing everything through open surfaces. That’s the bet Neon makes: if you can do it in the console, there’s an endpoint for it too. This fork is the proof — the whole console, rebuilt on nothing but the public API.
It’s also why Neon works as infrastructure behind other products. Vercel, Netlify DB, Replit, and Laravel Cloud all manage fleets of Neon databases through the same APIs you have access to. If they can build a platform on top of Neon, so can you.
That’s the real reason to slop fork. It’s a fast way to prototype product ideas — new layouts, workflows, resource experiences — and an even better starting point for your own console: tighter integrations with your tooling, custom observability, AI-native workflows, or a completely different UX for your team. Fork it and build the dashboard your Postgres fleet actually deserves.