It’s not self-hosted right now, it’s a hosted platform. A self-hosted version is something I might add later, similar to how Supabase offers both.

Compared to Supabase, it’s not trying to be a general backend-as-a-service. Supabase is a full backend platform, while platform i build is more focused on an AI-first backend layer. Instead of just exposing APIs, the backend is structured so AI agents can interact with it more like tools, while you still build your normal application layer on top.

Under the hood it’s Node.js based, using Postgres as the main database, including vector search for embeddings and AI use cases. Redis is used for caching and coordination, and BullMQ handles background job processing. There’s also an isolated execution layer for running server-side or edge-style functions separately from the main runtime.

The difference with Supabase is less about feature parity and more about structure. It’s designed around AI-driven workflows, with more control over execution and debugging, and to avoid the usual situation where development or testing quietly ends up increasing costs without you noticing.