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.
Guilty as charged. This is a clone of the Neon console, built from scratch on the Neon API. Every project, branch and compute you manage here goes through the same endpoints you can call with an API key, from a script, an agent or your own platform.
Read the story: “I Slop Forked Neon. You Should Too.”Agents are changing how we build software and they’re doing it at agent speed. They’re far better (faster, more token-efficient) at using APIs, CLIs and MCP servers than at clicking through a dashboard. Give an agent an API key and it can rule the world (or at least your dev tool).
For the best developer and agent experience, think of your open API as the core of your product. That’s the bet Neon makes: if you can do it in the console, there’s an endpoint for it too.
As a developer, you can use the API to automate everything around the platform and build on top of it. As an agent, you can do the same at agent speed, without getting stuck behind the console’s bot protection.
Neon went all in on its API because of Neon for (agentic) platforms. 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.
So I slop forked Neon to prove that you can literally rebuild the Neon console from scratch on Neon’s APIs. Check it out: sign up and provision real Neon resources through the slop fork.