On this page

FAQ

Answers to common questions about project status, limits, data and the platform.

#Is there a status page?

Yes: stitchdb.com/status shows every platform service, project APIs, Postgres connections and DNS per region, checked every minute, with incidents and maintenance. A copy is served by our database servers at https://health-eu-de-1.stitchdb.com/status, so it stays reachable when the main website is not. Each project also shows its own status in the dashboard, and GET https://<project-ref>.p.stitchdb.com/ returns {"status":"ok"} when the project's API is reachable. See Support and status.

#How do I contact support?

Open a ticket in the dashboard under Support. See Support and status.

#My API returns 503 project_paused

The project was paused, usually because nobody signed in to the account or used its projects for a year. Restore it from its page in the dashboard. See Inactive free projects.

#Writes fail with "over its database size limit and is read-only"

The database is over its plan's size limit. Delete data (see Database limits) or upgrade; writes resume within a few minutes.

#Uploads fail with 413

Either the file is larger than your plan's or the bucket's upload limit, or the project's file storage is full.

#I get 429 Too Many Requests

You reached the API requests per second of your plan, or an auth rate limit. Retry with backoff, cache reads, or upgrade.

#My query returns no rows, but the table has data

Row Level Security is on and no policy allows the request. Add a policy; see Row Level Security.

#Can anyone read my table?

If RLS is off on a table in public, yes: anyone with your anon key. Tables created with SQL start with RLS off. Check Advisors in Studio.

#The first request after a while is slow

On Free, a project's Auth and REST services sleep after 60 minutes without requests and wake up on the next one within a few seconds.

#Do my connection strings change when my project moves or my plan changes?

No. The database host stays the same for the life of the project.

#Is my data backed up?

Every project can be restored to any moment of the last 24 hours (Free), 7 days (Pro), 14 days (Scale) or 30 days (Enterprise). Paid projects also get a daily restore point (kept daily for 7 days, then weekly up to the plan's retention). Any project can export a pg_dump file from the Backups page. See Backups.

#What happens if my payment fails?

After 3 days your account moves to Free limits; nothing is deleted. See Billing.

#Can I run my own server-side code?

Yes, with Edge Functions: TypeScript or JavaScript functions served at https://<project-ref>.p.stitchdb.com/functions/v1/<name>. Database functions, cron and HTTP from SQL are available too.

#Which sign-in methods are there? Can I resize images?

E-mail and password, magic links and codes, phone (with your own SMS provider), OAuth providers, anonymous sign-ins, Web3 wallets, passkeys, SAML single sign-on and multi-factor authentication. Stored images can be resized on the fly with a URL, on every plan.

#Is there a command line tool?

Yes: the stitchdb CLI runs your project locally, manages migrations, generates TypeScript types and deploys functions. Install it with npm install -g stitchdb-cli.

#Can I test schema changes before they reach production?

Yes. Run everything locally with stitchdb start, and on paid plans give each feature or pull request its own preview branch: a separate database built from your migrations.

#Can I rename a project, move it to another region or rotate keys?

Not from the dashboard. Contact the StitchDB team.