Contact
Reach the Devpilot team — book a demo, ask a sales question, get support, or send a general enquiry.
Contact
Need to talk to a human? The public Contact page is the single front door for getting in touch with the Devpilot team. This guide explains how to use it, what information you should include, and when to expect a reply.
How to submit a request
Open the contact form
Go to /contact. You do not need a Devpilot account to submit a request — the page is public.
Choose a request type
Pick the option that best matches your enquiry. Devpilot supports four types:
| Type | Use it for |
|---|---|
| Demo | A walkthrough of Devpilot tailored to your team's stack. |
| Sales | Pricing, plan sizing, or procurement questions. |
| Support | Issues with an existing Devpilot account or deployment. |
| General | Anything else — partnerships, feedback, press. |
If you do not pick a type, the form defaults to Demo. When you are not sure which to pick, choose General and we will route it for you.
Fill in your details
Provide the following:
- Name (required) — up to 255 characters.
- Email (required) — a valid email address we can reply to, up to 255 characters.
- Company (optional) — the organisation you are asking on behalf of, up to 255 characters.
- Team size (optional) — rough headcount. Helps us prepare the right demo.
- Message (optional) — up to 2,000 characters. See tips below.
Submit the form
Click Send. You should see a confirmation message that reads something like:
"Your request has been submitted successfully. Our team will be in touch within 24 hours."
A copy of the request is also emailed to the Devpilot support team so nothing falls through the cracks.
Every submission is stored with a status of new and tracked internally until it is answered, so nothing is lost even over a weekend.
What information to include
The more context you give, the faster the right person on the Devpilot team can respond. For each request type, consider including:
- The stack you deploy today (languages, frameworks, cloud provider).
- Your team size and how many developers will use Devpilot.
- Timezones and preferred days or times for a call.
- What you hope to see during the demo (for example "zero-downtime rollbacks" or "GitHub Actions integration").
- Your expected usage — number of workspaces, projects, or deployments per month.
- Any procurement constraints (invoicing, currency, SSO, regional data residency).
- Whether you need a signed NDA or custom terms.
- Who on your side will sign off and roughly when.
- The workspace and project name or slug where the problem is happening.
- The time the problem occurred (include timezone).
- Error messages, screenshots, or deployment IDs where possible.
- What you have already tried.
If you already have a Devpilot account, also visit the Status page to check whether a known incident is affecting you before filing a support request.
- Who you are and what you are working on.
- Why you are reaching out.
- Any deadlines we should know about.
Please do not paste secrets, API keys, or private tokens into the message box. If you need to share sensitive data for a support case, wait for a team member to reply so we can set up a secure channel.
Response expectations
- The confirmation message promises a reply within 24 hours.
- Demo and sales requests are handled during business hours in the Devpilot team's timezone.
- Support requests from signed-in customers are prioritised by severity. Active outages on your workspace are fast-tracked.
- Responses land in the email address you entered on the form — make sure you can receive mail at that address.
After you submit
- Keep an eye on the email address you entered — replies land there.
- If you need to add more information before hearing back, submit the form again with the same email and reference your original request in the message.
- For live updates on platform-wide issues, follow the Status page while you wait.
- If you asked for a demo, a calendar invite usually follows within a business day.
Frequently asked questions
Yes — the form accepts any valid email. For support requests against an existing workspace, the team will cross-check that the email is associated with a member of that workspace before sharing account-specific details.
Check your spam folder first — replies come from the Devpilot support domain. If you still cannot find a response after 24 hours, re-submit the form and mention that this is a follow-up.
Simply submit the form again with the corrected details and reference the previous request in the message. There is no undo button, but the team routinely dedupes near-identical submissions from the same email.