Support

• -Status - if a region is degraded, we already know and the page says so
• -Documentation - the quickstart, the connection guide, and the import guide cover most of what people write in about
• -capydb doctor - lints a project's configuration for the mistakes that produce the most confusing symptoms
• -The dashboard's job list - a failed operation says what it was trying to do and what stopped it

Email reaches the people who build and operate the platform. There is no first-line script, no ticket-routing tree, and no attempt to close your conversation before it is finished.

Include the project name, the region, roughly when it happened, and what you expected instead. If it is a connection problem, the exact error string from your client is worth more than a paragraph describing it.

• -Platform incidents: we respond as fast as we can see them, and the status page is updated before the inbox is
• -Production-affecting problems: we aim to acknowledge within one business day
• -Questions, plan changes, and setup help: usually the same day, sometimes the same hour
• -Accessibility reports: acknowledged within five working days, with a plan or an honest no
• -Security reports: acknowledged quickly - see the Security page for what to include

Moving a live production database is the one operation we would rather do with you than watch you do alone. Tell us before you start: we will review the plan, be around for the cutover window, and keep a restore path ready.

The same applies to a restore over a production database. That operation exists, it works, and it is deliberately gated behind a human confirmation rather than exposed to a script or an agent.

We will help you with anything about the database and the platform. We will not write your application's queries, debug your ORM's configuration, or design your schema for you - not because we are unwilling, but because doing it badly from the outside is worse than not doing it.

If you want that kind of help anyway, ask. Sometimes the answer is yes.