FAQ

Yes — a real Postgres database, with its own login role and connection string. Point psql, Prisma, Drizzle or any Postgres driver at it. Nothing about your schema is proprietary.

Settings can dump the project, download the file, or restore it. Pro and above also get a daily snapshot. That is not point-in-time recovery — only those copies. You can still pg_dump the connection string yourself.

You skip provisioning, connection handling, and writing a CRUD API. Creating a project gives you a database plus generated REST endpoints, email/password auth, file storage, change subscriptions, vector search, and HTTP calls to your own Postgres functions.

Yes, optional. Secret API keys (sk_) bypass RLS. Publishable keys (pk_) are subject to whatever policies you write. If you enable RLS and add no policy, publishable keys cannot read or write that table.

In the United States, on a shared Postgres instance, as its own database with its own role. Other tenants cannot CONNECT to it. Dedicated instances are not offered. There is no uptime SLA.

Free is one database, 500 MB growing to 1 GB, 1 GB of files, 1 GB egress, 20k embed tokens, paused after 7 days idle, and a manual snapshot. Pro is $10/month for 3 databases with 2 GB Postgres, 5 GB files, 3 GB egress, and 200k embed tokens. Pro+ is $29 for 8 databases with 10 GB / 20 GB / 10 GB / 1M tokens. Those allowances are hard caps; more capacity requires the next plan. Your own vector floats do not consume embed tokens.

Supabase Pro includes much more storage and traffic for one busy project. starterpg is optimized for several small projects: Pro is $10 for three databases and Pro+ is $29 for eight, with teammates included. Choose Supabase for its larger ecosystem, edge runtime, and high included traffic; choose starterpg when direct Postgres plus several inexpensive backends is the better fit.

Yes. The project Logs tab shows seven days of API status, latency, normalized paths, request IDs, and end-user Auth outcomes. Responses include X-Starterpg-Request-Id for correlation. Bodies, query strings, credentials, tokens, and email addresses are not stored. Webhook delivery history has separate status filters, delivery-ID search, payload inspection, and replay.

Only if you turn Embed on in the project and pass ?embed=true. Otherwise you send floats yourself. Hosted embed uses Google’s gemini-embedding-001 into vector(768) and counts against the plan’s monthly token wall.

Yes — ordinary Postgres functions in the public schema. Create them in the SQL editor, then POST /rpc/<name> with named arguments. They run as your database role. There is no separate edge-function runtime. For outbound work, paste an invoke URL: we POST signed row-change events to your HTTPS endpoint and show every retry.

Immediately. Switch plans and the new allowances apply at once. Unused time on the old plan is credited on the next invoice.

Yes, on every plan — including Free. Create a team in the dashboard and invite accounts by email. There is no Team SKU, no seat fee, and no organisation surcharge — unlike Supabase’s $25 org.

No uptime SLA. Pro and above get daily per-project snapshots you can download or restore. Free can take a manual snapshot in Settings. That is a convenience, not a restore contract, and not point-in-time recovery. You can still export with pg_dump.

Technically yes — provisioning uses a superuser. We do not inspect customer data except to run the platform, respond to abuse, or comply with law. Do not store data you cannot accept on shared infrastructure.

Not unless we have signed a separate written agreement. The standard Terms forbid PHI, PCI cardholder data, and similar regulated workloads.

Unpaid accounts can be suspended. Free projects may be paused after 7 days idle and deleted after 60 days idle, after we try to email you. Export first. Fees already paid are not refunded except where law requires it.

You, for backups and application-level mistakes. Our liability is capped as described in the Terms — typically the fees you paid in the prior three months, or $50 on the free plan. Use the Service only if that is acceptable.

Read the FAQ and docs, then use the contact form. Paid plans get email support as a best-effort queue, not a response-time SLA.