Contact
Pick the route, not the form.
DevEx is maintained by one person. Where you send something changes how fast it gets answered and whether anyone else can benefit from the answer, so the routes are listed separately rather than pooled into an inbox.
Five routes
- A bug, or something missingThe issue tracker. Public, searchable, and the only route where someone else hitting the same thing can find your report. Include the workspace template and what you ran.Open an issue
- A question about using itRepository discussions, or an issue if you are not sure whether it is a question or a bug. Check the documentation first — most of what gets asked is in the quickstart or the self-hosting guide.Start a discussion
- Commercial, enterprise or partnershipA call. Bring the shape of what you want to run — how many concurrent workspaces, what has to be inside the container, and whether it needs to sit in your own infrastructure.Book a call
- SecurityReport privately rather than in a public issue: open a GitHub security advisory on the repository, which is visible only to the maintainer until it is fixed.Report privately
- Anything elseThe maintainer's own site has the current direct routes. This is the slowest of the five and the right one for things that do not fit above.Reach Parth Kapoor
What to expect
This is not a company with a support rota. Issues are usually looked at within a few days; a call is the fastest route to a person. If something is broken on the hosted instance, the status page checks the cluster, the object store and Redis live — worth a look before writing anything up.