Hosted Postgres | Supabase

Why developers choose Supabase for hosted Postgres

You came for a Postgres database. You get a fully managed one, plus the tools you would otherwise build or buy. Pure Postgres, no lock-in.

• Real Postgres, fully managed

  Connect with psql, pgAdmin, or any standard client. Use native extensions and Row Level Security. We handle provisioning, patching, backups, and uptime.

• Free to start, $25 when you need more

  Launch a database for free in seconds. Upgrade to Pro for daily backups, email support, and additional production features.

• More than a database, from day one

  Every project ships with a Dashboard, a SQL Editor, a Table Editor, logs, performance and security advisors, and auto-generated APIs.

• Built to scale, dependable under pressure

  Read replicas, point-in-time recovery, and high availability when you need them.

Pay for Postgres, not for surprises

Most hosted Postgres plans start cheap and stay just okay. Supabase is free to start and $25 a month for a production database, with no charges for reads or writes and no per-connection fees. Here is what is included at each tier.

What you get

Free

Pro

Monthly price

$0

$25

Dedicated Postgres database

Dashboard, SQL editor, table editor

Auto-generated REST and GraphQL APIs

Full extension ecosystem (pgvector, PostGIS, and more)

Connection pooling

Charges per read or write

Never

Never

Automatic daily backups

7-day retention

Point-in-Time Recovery

Add-on

Read replicas

Add-on

Database branching

Usage-based

Projects never pause

Email support

Community

[

See full pricing about /pricingSee full pricing

](https://supabase.com/pricing)

More than a database

Backups, connection pooling, branching, observability, point-in-time recovery, and developer tools included from day one.

Your database is an application platform

Generate APIs, schedule work, trigger workflows, manage secrets, and connect external systems without leaving Postgres.

Top performance,

at any scale

Supabase is Postgres, so the ceiling is Postgres. Scale compute and storage independently, add replicas, and keep query times low whether you are handling a launch spike or steady growth. You will not outgrow it and need to start over somewhere else.

• Databases Created

  44,000,000+

• Postgres performance gains

  20-30x

Users

0,000,000

+00.0%

Security

Postgres is trusted for medical records, missions to the moon, and everything in between

Keep your data secure with SOC 2, HIPAA, and GDPR compliance. Your data is encrypted at rest and in transit, with built-in tools for monitoring and managing security threats.

[

Learn about security about /securityLearn about security

](https://supabase.com/security)

• SOC 2 Type II certified

• HIPAA compliant

• Encryption at rest and in transit

• SSL enforcement

• Network restrictions

• Row Level Security and Role-Based Access Control

• Database audit logs

• Security Advisors

• Multi-factor authentication

• DDoS protection and vulnerability management

Choose your platform to get started in seconds

Or, start with Supabase AI Prompts

Bootstrap Next.js app with Supabase Auth

1. Install @supabase/supabase-js and @supabase/ssr packages. 2. Set up environment variables. 3. Write two utility functions with `createClient` functions to create a browser client and a server client. 4. Hook up middleware to refresh auth tokens

Writing Supabase Edge Functions

1. Try to use Web APIs and Deno's core APIs instead of external dependencies (eg: use fetch instead of Axios, use WebSockets API instead of node-ws) 2. If you are reusing utility methods between Edge Functions, add them to 'supabase/functions/_shared' and import using a relative path. Do NOT have cross dependencies between Edge Functions. 3. Do NOT use bare specifiers when importing dependecnies. If you need to use an external dependency, make sure it's prefixed with either 'npm:' or 'jsr:'.

Declarative Database Schema

Mandatory Instructions for Supabase Declarative Schema Management

1. **Exclusive Use of Declarative Schema**

-**All database schema modifications must be defined within '.sql' files located in the 'supabase/schemas/' directory.

Create RLS policies

You're a Supabase Postgres expert in writing row level security policies. Your purpose is to generate a policy with the constraints given by the user. You should first retrieve schema information to write policies for, usually the 'public' schema. The output should use the following instructions:

• The generated SQL must be valid SQL.