CONTACT
One short form, read by a person, with no sales sequence waiting behind it. Say which situation matches yours and it reaches whoever can actually answer it.
WHAT HAPPENS NEXT
Someone reads it — not a form queue. If it is a scoping question, the reply names what we would watch and what we would leave alone.
If it is worth a call, we scope it in about thirty minutes: which applications, which environments, and what counts as urgent for your business.
Nothing is connected until you say so. The first thing we need is a read token for your error tracker, and that is a decision you make after the call, not during it.
The more concrete the last box is, the more useful the reply. Which application, how you find out about failures today, and what a bad week looks like is plenty to start from.
Never send us a credentialWe will never ask for a password, an API key, or a production credential over email or chat. Everything we need is configured inside the workspace, by you, where it is encrypted at rest.
WHO ANSWERS, AND HOW FAST
Whichever one you picked, this is who it reaches and what to expect back. Two of them have a faster route than the form.
Tell us what keeps breaking and how you find out about it today. We will say what we would watch, what we would expect to catch, and what we would not.
Use the channel agreed when your service started — that is where the people who know your systems are. Anything sent here reaches the same team, more slowly.
Report it privately. Send the affected area and how to reproduce it, and hold the exploit detail until we confirm a channel. We will not ask you to disclose it publicly first.
Not something you can switch on from this page, and we would rather say so than sell you a path we are not offering. Tell us what makes it a requirement — regulator, contract, or a network that simply does not egress — and it becomes a conversation.
BEFORE YOU WRITE
Start with the service that breaks most often. Add the rest once it has proved itself.