ɳSelf vs Supabase: when self-hosted wins

Supabase is good software. The developer experience is polished, the team ships fast, and the free tier is generous. For solo projects and early startups, it is often the right choice.

But the math changes as you scale, and ownership changes never. Here is an honest look at when each tool fits.

When Supabase wins

Be straightforward about the trade-offs. Supabase wins on:

• Managed operations. No server to maintain, no updates to run, no 3am alerts from your own infra.
• Dashboard UX. Supabase's dashboard is excellent for quick iteration and SQL editing.
• Realtime subscriptions. Well-polished and battle-tested at scale.
• Zero cold-start for serverless. Edge functions spin up instantly.

If you are building a prototype, a hackathon project, or a small app that will stay small, Supabase Cloud is the faster path. You will be writing product code in minutes instead of provisioning servers.

When ɳSelf wins

ɳSelf wins on ownership, cost at scale, and extensibility.

Pricing at scale

Supabase Pro starts at $25/month. That gets you 8GB database, 250GB bandwidth, and 1GB file storage. Go past those limits and you pay overages.

At meaningful scale, 500k monthly active users, 100GB database, heavy egress, you are looking at $200-500/month or more. The costs are hard to predict because they depend on usage patterns you cannot always control.

An ɳSelf stack on a $4/month Hetzner CX23 server handles the same workload. The CLI is free. You pay for the VPS and optionally for Pro plugins ($9/year) or the AI suite ($19/year). Total cost at scale: $50-70/year instead of $2,400-6,000/year.

Data ownership

Your data on Supabase lives on their infrastructure. Their security posture, their compliance certifications, their uptime SLA, and their pricing decisions apply to your data. If Supabase changes pricing, gets acquired, or sunsets a feature, you feel it immediately.

With ɳSelf, your Postgres database is on hardware you control. Point-in-time recovery, backups, encryption at rest: all configured by you, verified by you. Your data never touches a third party's servers.

Extensibility

Supabase extensibility is mostly Edge Functions and Postgres extensions. Both are useful, but they are sandboxed.

ɳSelf has 55+ plugins that wire directly into the backend stack:

• AI agents (ɳClaw) with ReAct reasoning and tool auto-discovery
• Email routing (nself-mux) for inbound/outbound email pipelines
• Cron jobs for scheduled tasks
• Full-text search via MeiliSearch
• CMS, Stripe, Shopify, LiveKit, notifications, and more

Each plugin installs in one command and integrates with the Hasura GraphQL schema automatically. No manual wiring.

Custom services

Need a Go microservice? A Python data pipeline? A Rust WebSocket server? ɳSelf supports up to 10 custom services from 40+ language templates:

nself service create my-api --template go-fiber
nself build && nself restart

Your service gets automatic SSL, nginx routing, health checks, and log aggregation. Try doing that with Edge Functions.

The same foundations

Both platforms use standard Postgres. Both expose GraphQL (Supabase via pg_graphql, ɳSelf via Hasura). Both support JWT auth, S3-compatible storage, and real-time subscriptions.

This means the migration path is real. Moving from Supabase to ɳSelf is a pg_dump and restore for the data layer. The Supabase-specific pieces (realtime channel names, auth JWT claims, storage policies) need adjustment, but it is a one-time effort, not permanent lock-in.

See our full comparison page for a detailed feature-by-feature breakdown.

They are not mutually exclusive

A project can start on Supabase Cloud and migrate to ɳSelf when it outgrows managed pricing. The migration path is straightforward because the core primitives are the same.

Build where it makes sense today. Move when the economics change.

The honest recommendation: if you are a solo developer building a weekend project, use Supabase. If you are building something you plan to run for years, something where you need to own the infrastructure and control costs, look at ɳSelf.

brew install nself-org/nself/nself
nself init
nself start

Five minutes to a full backend stack. Your server. Your data.