Support
One address. A person answers.
How to reach us, what to put in the mail so the first reply is the fix, and how fast we answer on each plan.
Support hoursMonday to Friday, 09:00 to 18:00 CET
Monday to Friday, 09:00 to 18:00 Central European Time, public holidays excluded.
Where to write
There is no ticket portal and no chat widget. A mail lands with the people who built the product, and the reply comes from one of them.
Write to us
hello@devbench.shhello@devbench.sh, from the address on your DevBench account.
- No ticket portal
- No chat widget
- A person answers
Before you write
The in-app guide answers most “how do I” questions first: open Guide in the sidebar, or read the public copy here.
Something is down
Put DOWN at the start of the subject. Mails with that subject are read first, on every plan.
A security issue
Write to security@devbench.sh, not to support, so it reaches the right people and only them.
What to include
Fill in what you know and the mail writes itself. It opens in your own mail app, ready to send.
The first reply is the fix when the mail carries these:
- 1Your organization's name and the workspace, if there is one.
- 2What you did, what you expected and what happened instead. Exact wording of any error.
- 3The time it happened and the time zone. Every action a box takes is in the audit log and the task timeline, and the time is how we find it.
- 4Where the organization runs: DevBench compute, your own host, or a cloud account.
- 5A screenshot or, better, the recorded demo of the run. The product records its own work; attach the clip.
Do not send secrets, tokens or credentials. If a token is involved, revoke it on the provider and say so; we never need the value.
Write a mail that gets fixed on the first reply
Preview
- To
- hello@devbench.sh
- Subject
- Support request
Organization: …Workspace: …Runs on: …When: …What I did:…What I expected:…What happened instead:…Opens your own mail client. Nothing is sent from this page.
Response times
The first reply, by plan, and where it comes from.
Starter
First reply
Community, best effort
Channel
The community channel (by mail until the channel exists); mail for account and billing matters
Team
First reply
Next working day
Channel
Mail
Business
First reply
Same working day
Channel
Mail, and a call when a mail is not enough
Enterprise
First reply
As agreed, with a named contact
Channel
Mail, call, and the shared channel in the contract
A working day is Monday to Friday, 09:00 to 18:00 Central European Time, public holidays excluded. Access requests from this site get a reply within one working day whichever plan you are considering.
Something is down
Put DOWN at the start of the subject. Say whether it is one workspace, one organization or everything, and whether it runs on DevBench compute or on your host. Mails with that subject are read first, on every plan.
On a host you run, check the host first: the update script, the container runtime and Redis are the three things the hosting page says an operator must be able to see.
A security issue
Write to security@devbench.sh, not to support, so it reaches the right people and only them. The Trust section of the security page says what happens next, and security.txt carries the same address for tools that look for it.
Your account and data
To export your organization's data, delete your account, or exercise a right under the GDPR, mail hello@devbench.sh from the account's address. We answer within one month, usually far sooner. The privacy policy says what we hold and for how long.