Show HN: InsForge AI, Open-Source Agent Friendly Alternative to Supabase

[tonychang430]

Hi HN, We are excited to present you InsForge AI. We quit Databricks, Meta, and Amazon to build *an agent-friendly Supabase alternative*.

Why? Because current tools like Supabase make it painful for agents and developers:

1. *RLS enabled by default* → queries fail without policies

2. *Verbose Postgres policies* that are error-prone to write and maintain

3. *Secrets and auth setup* require lots of manual wiring

InsForge is an open source project and we provide hosted versions with API access as well. (Website: https://insforge.dev/ , Github: https://github.com/InsForge/InsForge)

With InsForge, APIs ship with sane defaults via MCP servers — security rules are applied automatically so developers get safe behavior out of the box, without manual intervention. Both client and server code are fully open source.

For a quick start in the hosted version, login to our website and create a project. Then start connecting with your coding agent and start calling our APIs directly. You can find more details in our docs. https://docs.insforge.dev/quickstart

This is still an early release and we’d appreciate feedback from the community. What are your pain points when interacting with BaaS platforms? We’ll be around in the comments to answer questions. Thanks for reading!

[albertlsc]

I’ve always found the “RLS enabled by default” behavior in Supabase/Postgres to be a double-edged sword: great for security, but brutal for DX when you’re just trying to get an agent or prototype working. The idea of having MCP servers enforce sane defaults automatically feels like a huge win for developer productivity without sacrificing safety.

Also really like that you’re tackling the “manual auth & secret wiring” problem — I’ve seen so many projects stall because the glue code around auth is brittle and error-prone.

Curious on two points:

How does InsForge handle multi-agent coordination? For example, if multiple AI agents are calling APIs concurrently, are there built-in isolation or quota mechanisms?

What’s your roadmap for integrations? (e.g., vector DBs, observability hooks, hosted dashboards)

This feels like it could lower the barrier for agentic apps quite a bit. Kudos on open-sourcing both client & server — looking forward to seeing how the community builds on this

[hemuyuan120]

This looks really interesting — thanks for sharing! I’m curious: how does InsForge handle scaling and performance compared to Supabase, especially when dealing with high-throughput applications? Do the MCP servers introduce any trade-offs in latency or flexibility for developers?

[tonychang430]

For high-throughput applications, we expect minimal differences compared to Supabase on the hot path, since both ultimately run on native Postgres and rely on the same proven, open-source modules (RLS, replicas, extensions).

Where MCP stands apart is in flexibility and safety: we provide the most secure and scalable setup out of the box, with guardrails for agents and developers, while still letting you drop down into Postgres when you want fine-grained control.

[junwenfeng]

How do you imagine devs using this with coding agents day-to-day? Is it mostly for prototyping, or can it fit into production CI/CD flows?

[BowenLI-BV]

What’s on your roadmap — will you add support for other databases (MySQL, MongoDB), or is the focus purely Postgres?

[tonychang430]

Right now our focus is purely on Postgres, since it integrates best with our agent-native system. That said, we do plan to support other database types in the future as the ecosystem grows and user demand makes sense.

[jjh1102]

If I want fine-grained control later, can I still drop down into Postgres policies and override the defaults?

[fermioniclyu]

Do you see InsForge as more of a Supabase alternative, or a new category focused on agent-native backends

[tonychang430]

Eventually, we see InsForge as more than just a Supabase alternative. Supabase is great for giving developers a backend in minutes, but it was never designed with agents in mind.

InsForge is a new category: agent-native backends. Instead of just exposing APIs, our MCP servers actually set up database, storage, auth, and policies with safe defaults, so both agents and humans can collaborate without breaking things. On top of that, the system knows how to debug, enforce security, and adapt workflows automatically.

[qqqqqqyn]

Does the hosted version let me bring my own Postgres, or is it all managed by you?

[tonychang430]

For the hosted version, we completely manage Postgres for you — it’s fully provisioned, secured, and maintained in our cloud. That way you don’t have to worry about backups, scaling, or patching.

If you’d prefer to bring your own Postgres, that’s possible through our self-hosting version. You get the same agent-native features, but plugged into your own database instance and infrastructure.

[leo-yu222333]

How do you debug when the auto-generated policies don’t match what you want?

[gasxchenzhuo123]

How do you manage the infra of this, what cloud provider do you use ?

[tonychang430]

We run on AWS as our underlying infrastructure, largely because of our team’s deep experience with it and the materiality of its ecosystem

[barrywang0706]

How is the MCP server different from supabase MCP

[tonychang430]

Supabase MCP is more like a wire — it gives you a way to connect APIs, but it’s still up to you to set up the backend logic, security, and debugging around it.

Our MCP, on the other hand, is more of an ecosystem. It doesn’t just connect APIs — it actually sets up your backend with proper defaults, security, and advanced features out of the box. It also understands how to debug and manage workflows end-to-end, so agents and developers don’t have to manually patch things together.

[yaowenc2]

Does AI handle all these things well??

[honoyomu]

Dedicated PostgreSQL for every project

[tonychang430]

100%!!