When you need us, a person answers
Small team, European hours, no ticket maze. Below: where to write, what we do when something breaks, and everything that has changed.
How it works
You write an email. That is the whole process — there is no portal to log into and no form to fill in. On our side it becomes a tracked ticket, and the reference travels in the subject so the thread stays whole:
[TKT-7GK2MQ].One address for everything — support, sales, Enterprise sizing, the DPA and security reports. One inbox that is always read beats four that are unevenly watched.
If something is on fire, say so in the subject and it jumps the queue. Keep the [TKT-…] reference in the subject when you reply and nothing gets lost; strip it
and you have simply opened a second ticket.
Status and incidents
We email you when your node is affected — that is the promise, and it is the one we can keep. A status page that says "all systems operational" because nobody remembered to change it is worse than no status page, so we ship the alert first and the dashboard when it is fed by real monitoring rather than by hand.
You also decide in advance what an outage of ours means for your traffic: fail open, and requests reach your backend unfiltered, or fail closed, and they stop at the edge. Per node, from the panel.
What's changed
Who builds this
Quota is made by Syrakon, a European group of developers building tools for developers — including the two database engines underneath Quota. The group, what else it ships and who works there live on syrakon.com; this page stays about your node.