Small on purpose.
The person who answers your email has full system access. This is why we are so specific about our setup.
How we work
One primary, documented
One well-understood machine we own, in Drenthe, a written failover design, and daily backups, with an off-site copy on the way. It is better to know your one point of failure than to have six unknown ones.
Written before built
Hosts, mail routing, certificates, models, and backups are laid out in writing before provisioning. If a plan does not make sense when read, it will fail in production.
You keep the keys
Source, runbooks, DNS, and accounts stay yours throughout. When we end a contract, we hand over everything. We do not hold your data hostage.
We say no in writing
If something is outside what we can operate well, we say so and point you elsewhere. Referring you to a better provider is cheaper for you than us doing a bad job.
An engagement, start to finish
- 1
Brief
You write what you are running and what you want. We read it and reply the same day as a rule, within 48 hours at most, signed.
- 2
Read
Two or three sessions and access to what exists. We look before we propose.
- 3
Written scope
A document with the architecture, sequence, price, and explicit exclusions. A signed scope fixes its price.
- 4
Build
Vertical slices, shipped weekly. Each is a working piece. You watch the deploys we do, and slips are in writing before you ask.
- 5
Hand over
Source, runbooks, credentials, and a walkthrough. Maintenance afterwards is optional and priced per term.
Send a brief. A person reads it.
Tell us what you are running today and what you want it to do instead. You get a personal reply with a price that fits, and if it does not, we work out a plan together. The person who writes to you is the same one who would do the work.
Mon–Fri 08:30–23:00 · Sat–Sun 11:00–00:00 CETReply the same day, 48 hours at most. S/MIME-signed.