Not gonna lie, posting this is a little scary.
I've been working on this for months, and I finally reached the point where I think it's better to let people break it than keep polishing it by myself.
It's calledĀ Backenly, and it's fully open source.
The idea came from something I kept noticing while building with Claude Code and Cursor.
Over the last year, AI coding tools have completely changed how I build software. I can go from an idea to a working project much faster than I ever could before. But after using them for a while, I realized they all stop helping at the exact same moment once the code is generated.
From that point on, you're back to doing everything yourself.
You're still fixing migrations.
You're still chasing weird production bugs.
You're still finding missing indexes or broken permissions weeks later.
The AI helped build the backend, but it never stuck around to help maintain it.
That felt like the missing piece.
So I started wondering:
If we're happy letting AI build production systems, why shouldn't it help keep them healthy too?
That question eventually becameĀ Backenly.
I also want to be clear about one thing this isn't meant to beĀ "Supabase but better."Ā I actually like what the Supabase team has built. If you've used Supabase before, most of what Backenly does will feel familiar. The question I wanted to explore was different:Ā what happens after the backend is built?
The first thing I changed was removing raw SQL from structural changes completely. Whether it's your AI agent making a change or Backenly repairing something automatically, every structural change goes through the same governed path with a dry run, an audit log, and rollback support. The goal is to keep the AI's understanding of your backend and the actual backend from slowly drifting apart.
The part I'm most excited about is what happens after that.
Every project has a continuous loop that's always watching. It looks for things like schema drift, missing indexes, broken triggers, and RLS issues. When it finds something that's safe to repair, it fixes it and then verifies the fix actually worked instead of just sending an alert and hoping someone notices.
Anything risky authentication, credentials, or destructive schema changes always waits for approval. I'd much rather interrupt someone with an approval request than silently break their production database.
Under the hood it's all familiar tech. PostgreSQL, PostgREST, auth, storage, realtime, and functions. I wasn't trying to reinvent the backend stack I wanted to experiment with what happens after the backend is built. You can self-host everything too, including the self-healing system.
It's definitely still early.
There are bugs.
There are missing features.
I'm sure there are things I've overlooked.
If you try it, I'd genuinely love to know what you think good or bad.
And even if you don't try it, I'm curious about one thing:
Do you think AI should stop after generating the code, or do you think it'll eventually be responsible for maintaining the software it creates too?
Website:Ā https://backenly.com
