Part of our stack. We choose the right tools for each project, not the other way around.
Supabase is one of the two databases we build applications on, alongside Xano. A full PostgreSQL database with login, file storage and realtime updates, just as stable and scalable as you would expect from a production backend. Among other things, we use it to build the software that speeds up our own work.
An open source backend built around PostgreSQL. Tables, users and permissions, file storage, realtime updates and server functions in one package. The access rules live in the database itself, so an app talks directly to the data without anyone seeing what is not meant for them. It runs in European data centres or on your own servers.
Internal apps for our daily work, a generator that creates content, a management environment for visual assets and our own SaaS products. Applications that are used daily and need a heavy-duty database underneath. We use the same approach for an asset library or content generation for clients.
Supabase for data and login, Next.js for the interface, hosting on Vercel. Where needed, an integration with Webflow through the Data API, so that what happens in the app also appears on the website.
Both give you a serious PostgreSQL database, equally reliable in production. The difference is where the logic lives. In Xano you build endpoints and business rules visually on the platform itself: clear, easy to hand over and a natural partner for Wized. In Supabase the logic lives in code, in the app or in server functions, and the interface talks directly to the database. That is a better fit once an application is being built in code anyway.
If the client wants to be able to view or change the backend logic themselves without code, we choose Xano. For content that only needs to appear on a website, the Webflow CMS is enough. If a team prefers to manage data as a spreadsheet, we use Airtable.