Email replies
Every message sent through the contact form is read and answered by email.
Support
Get unstuck without the runaround.
DBHost keeps support simple: clear documentation, an honest status page, and a contact form that reaches a person who can actually fix things. No ticket maze, no chatbot loop.
Live status
status.dbhost.app tracks platform incidents and planned maintenance.
Docs first
Most setup, connection, and API questions are already answered in the documentation.
Channels
Pick the channel that matches the problem.
Docs for how-to questions, status for platform health, the contact form for anything account-specific. Every channel below is the real one - there is no hidden priority queue.
Documentation
Quickstart, concepts, CLI, and the full API reference. The fastest path for setup and integration questions.
Browse the docsContact support
Something broken, confusing, or account-specific? Send a note with the Support topic and we reply by email.
Open the contact formStatus page
Check for ongoing incidents or maintenance before debugging your own stack. Subscribe to updates there.
View statusCLI on npm
Install instructions and published versions of @dbhost-app/cli. Report CLI problems through the contact form.
View on npmFaster answers
Three details that cut a support thread in half.
A message we can act on immediately gets a useful first reply instead of a clarifying question.
01
Name the database
Include the database name and your plan, so we can find the right resources without a round trip.
02
Paste the exact error
Copy the full error message and a timestamp with timezone. Screenshots work; exact text works better.
03
Describe what changed
New deploy, new driver, rotated credentials, allowlist edits - the last change is usually the lead.
FAQ
Common support questions, answered plainly.
Backups, recovery windows, connectivity, and how disclosures are handled - the answers here match how the platform actually behaves.
How do I contact DBHost support?
Use the contact form with the Support topic. We read every message and reply by email. There is no live chat or phone support today.
Is support different per plan?
Every plan uses the same contact channel. Pick the topic that matches your question - support, business plans, dedicated instances, privacy, or security disclosures - so the message lands with the right context.
How do backups and restores work?
DBHost takes daily pg_dump backups of production databases, and of other databases unless you turn daily backups off. Backups are stored off-host in encrypted S3 storage and retained for 30 days. Every plan can trigger on-demand backups from the dashboard. If a restore looks wrong or you are unsure which backup to use, contact us before proceeding.
I deleted a database by accident. Can I get it back?
Deleted databases stay recoverable from the dashboard for seven days after deletion. After seven days the database and its deletion backup are permanently deleted automatically, so recover early rather than late.
My app cannot connect. What should I check first?
Check the status page for platform incidents, confirm your connection string uses the pooled PgBouncer endpoint on port 6432, and review the database IP allowlist if you configured one. If it still fails, send the exact error message and a timestamp through the contact form.
How do I report a security issue?
Use the contact form with the Security disclosure topic and include enough detail to reproduce the finding. The security policy describes how disclosures are handled.
Still stuck?
Send the details and we will take it from there.
Include your database name, the exact error, and a timestamp. Security findings go through the same form with the Security disclosure topic - see the security policy for how disclosures are handled.