Support
Get help when infrastructure gets serious.
Tell us what you are building and where you are blocked. Good support starts with useful context and never requires you to send secrets.
Account and billing support
For wallet, reservation, renewal, or manual-transfer questions, include your account email, transaction reference, approximate time, and the action you expected. Do not include payment secrets, passwords, API keys, or connection strings.
Technical support
For database issues, include the workspace name, cloud region label, approximate time, endpoint state if visible, and the exact error message. A short reproduction path is more useful than a screenshot containing credentials.
Before you contact support
Check the service-status page, confirm your account is verified, review wallet and reservation state, and check whether the database workspace shows an endpoint or synchronization warning. These checks can resolve simple issues quickly and give support a better starting point.
Responsible disclosure
If you believe you found a security issue, do not test beyond what is necessary to demonstrate the problem and do not access another customer’s data. Report the issue with a minimal reproduction and avoid sending secrets in the first message.
Frequently asked questions
What should I never include in a support request?
Never include passwords, API keys, payment secrets, or full database connection strings.
Can support help with migrations?
Support can help you understand the available workspace and operational workflow. Keep a tested export, restore, and migration plan for important production data.
Continue exploring SaveOn
Choose the next resource for your project, from practical documentation to pricing, security, and support.