How to reach a person
We are a small team and we answer our own mail. That has an upside and a limit, and both are described plainly below.
Shared channel
Slack or Teams
Design partners get a shared channel with us. Ask during onboarding and we will set it up.
What to expect
We are pre-launch, so we are not publishing an SLA. Promising a response time we have not yet proven at volume would be a commitment we could not stand behind. What we can commit to is that every message is read by an engineer, and that we will tell you honestly if something will take a while.
In practice, during early access we aim to reply to ordinary questions within one business day, and to anything marked urgent considerably faster. Treat those as our intent rather than a contractual guarantee. When we have earned the right to publish real numbers, we will publish them here with the measurements behind them.
Reporting a problem well
The fastest resolutions come from reports that include a few specifics. If you can, tell us:
- The environment name and cloud account involved
- What you expected to happen, and what happened instead
- The deployment or plan identifier, if there is one
- Whether production traffic is currently affected
That last one matters most. It changes how we triage, and we would rather you tell us bluntly than understate it out of politeness.
Security issues
Suspected vulnerabilities should not go through ordinary support. Follow the disclosure process on the security page instead.
Sales, partnerships, and everything else
Same inbox. Use the contact form if you would rather answer a few structured questions than compose an email from scratch. It produces a better first reply from us.