Supabase Lite
The Supabase core - Postgres, Auth, and the REST API behind Kong - without the seven services most apps never touch. Fits a 2 GiB plan.
One-click deploy, from $13/mo on a Miget plan.
Most Supabase apps use three things: the database, auth, and the auto-generated REST API. The full self-hosted distribution ships eleven services to cover every feature - this template ships the four that carry those three workloads: supabase-postgres, GoTrue, PostgREST, and the Kong gateway in front.
The payoff is footprint. The full stack wants 8-16 GiB; this core idles around 600 MiB and is sized to fit a 2 GiB plan. Studio and postgres-meta ride a compose profile - enable the dashboard when you are working on the schema, turn it off when you are not.
It is the same pinned upstream images and init SQL as the full template, minus the optional surface - so supabase-js works unchanged for database, auth, and REST calls, and if you grow into Realtime or Storage later, the full template takes over with the same database volume.
Upstream project: Supabase
#what you get
- Postgres + GoTrue auth + PostgREST behind one Kong gateway
- Fits a 2 GiB plan - core idles around 600 MiB
- Studio dashboard on an optional compose profile
- Same pinned images and init SQL as the full supabase template
- supabase-js compatible for db, auth, and REST
- Upgrade path: move the volume to the full template when you need more
#topology
| Service | Role | Public |
|---|---|---|
| kong | gateway: APIs + Studio basic auth (:5000) | yes |
| auth / rest | GoTrue + PostgREST | via kong |
| db | supabase-postgres with its own volume | no |
| studio + meta | dashboard (profile: studio) | via kong |
#miget sizing
// this stack needs
2 GiB RAM · 8 GB disk · 4 services
Core (kong 512 + auth 256 + rest 256 + db 768 MiB) fits the 2 GiB plan with headroom - measured idle is ~600 MiB. Enabling the studio profile adds ~768 MiB: size up to 4 GiB while it is on, or toggle it only when needed.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Supabase Lite on Miget ★ | 2 GiB plan | $13 | this whole stack, flat - no usage meters, and room left for your own apps |
| Supabase Cloud | Pro | ~$25 | per org + metered compute/egress/storage/MAUs past included quotas |
The comparison flips versus the full stack: the lite core costs less than hosted Pro while keeping the always-on, no-meters, your-data advantages.
#vs. other PaaS
Estimated monthly cost of running this exact stack (2 GiB RAM, 8 GB disk, 4 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$100 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| Render | ~$30 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| DO App Platform | ~$29 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Railway | ~$21 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$13 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
supabase-lite -
Set the required variables:
POSTGRES_PASSWORD, database superuser passwordJWT_SECRET, 32+ chars; ANON_KEY and SERVICE_ROLE_KEY are signed with it - set once, never rotate casuallyANON_KEY / SERVICE_ROLE_KEY, JWTs signed with JWT_SECRET (use the supabase key generator)DASHBOARD_USERNAME / DASHBOARD_PASSWORD, Kong basic auth in front of StudioPG_META_CRYPTO_KEY, postgres-meta encryption key (studio profile)
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/supabase-lite
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
What do I give up versus the full Supabase stack?
Realtime (websocket change streams), Storage (file uploads), edge functions, the connection pooler, and image transforms. Database, auth, row-level security, and the REST/GraphQL API - the core most apps are built on - are all here.
Does supabase-js still work?
Yes, for everything this stack serves: createClient against your Kong URL, then auth flows and from()/rpc() queries work unchanged. Calls to realtime channels or storage buckets will fail - those services are not running.
Can I upgrade to the full stack later?
Yes - both templates use the same supabase-postgres image and init SQL, so the database volume carries over. Deploy the full supabase template pointing at your data and the extra services join around it.
Why is this stable when the full template is experimental?
Four services with fixed wiring are a much smaller surface than eleven with optional profiles. The core path (db, auth, rest, kong) is boot-tested end to end and changes rarely upstream.
Is $13/month really cheaper than Supabase Cloud free tier?
The cloud free tier is $0 - but it pauses projects after a week of inactivity and caps at two projects. This is for the step after: always-on, no meters, your infrastructure, still an order of magnitude less than running the full stack.
Ship Supabase Lite today
One compose stack, 2 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.