Not rented from
someone else's cloud.
We run our own dedicated hardware and wrote the control plane that operates it. That means no shared tenancy, no per-request pricing surprises, and a change window that answers to you rather than to a vendor roadmap.
- 04in production
Applications
Product workloads we build and ship
- 03automated
Control plane
Deploys, secrets, backups, observability
- 02DNSSEC
Network
DNS, TLS, routing and edge cache
- 01ours
Compute
Dedicated metal, tuned per workload
Four commitments the rest follows from.
We own the machine
Dedicated servers in an EU datacentre, operated by us. No shared tenancy, so your latency does not depend on somebody else’s traffic spike, and we can tell you exactly which machine your workload is on.
We wrote the control plane
Deploys, DNS, certificates, backups, users and monitoring run through software we built and maintain. When something needs to behave differently, we change it — we do not open a ticket with a vendor.
Recovery is tested, not assumed
Backups are verified by restoring them on a schedule and reporting the result. A backup nobody has ever restored is a belief, not a backup.
Nothing is undocumented
Every machine, service, domain and credential is written down and kept current. If you replace us tomorrow, the next team can pick it up in an afternoon.
Numbers we are willing
to be measured on.
Measured continuously, reported monthly. Including the months we miss — a vendor who only reports good months is not measuring anything.
- Measured uptime
- Response latency
- Production workloads
- Operational coverage
Rolling 12-month average across the fleet
p95 time-to-first-byte from EU edge
Applications we build, host and operate
Monitored, alerted and on-call, always
What is promised — and what enforces it.
Every line here is a promise something in the system actually keeps. Under each one is what enforces it, because a promise no mechanism enforces is phrasing, not a commitment.
- backups
- Every night, automaticallyolny-nightly.timer · 00:15
- retention
- 7 copies per site and database · up to 30 daysthe newest copy is never aged out
- restore drill
- Every night — a site or a databaseactually unpacked, and checked for content
- dns monitoring
- A check cycle every 60 seconds · 6 zonesprimary against secondary, and against public resolvers
- certificates & dns
- Renew themselves · separate primary and secondaryDNSSEC on request
- response time
- One business day · four hours · one hour, around the clockby plan · set out in the service level agreement
Tell us what you are building.
One call. A straight answer on whether it is worth building and what it costs. Then a written plan — yours to keep, and yours to take to another vendor if you prefer theirs.