Site
One page to ten. Content that changes now and then, a form that reaches an inbox, and a domain that simply has to work.
- Storage
- 10 GB
- Databases
- None
- Mailboxes
- 3
- FTP accounts
- 1
- Response time
- One business day
The same infrastructure that runs our own systems, and the same control plane. Once the payment settles, the allocation, the certificate and the DNS records are written automatically — nobody has to be awake for it.
Prices and limits are read from the control plane that will run you
One page to ten. Content that changes now and then, a form that reaches an inbox, and a domain that simply has to work.
Someone signs in with a password, there is data you cannot lose, and a release has to go up without taking the live one down.
Anything where half an hour down means someone loses money and someone picks up the phone.
Signing up allocates nothing until the payment settles. If something fails halfway, you are not left with a half-built site.
Payment is taken on a secure external page. Card details never pass through our servers and are never stored here.
This is not a marketing diagram. It is the list of operations the system actually performs, in order. Each one is written to the audit log and visible in the panel.
An account and a subscription open in a pending state. They own no disk, no mailbox and no domain — signing up on its own allocates nothing.
A checkout link opens. When the payment settles, a tax invoice is issued and sent automatically — not by hand, and not at the end of the month.
A vhost is written, the document root is created, and nginx reloads only after the configuration passes its own validity check. A bad config rolls back instead of taking the server down.
A Let's Encrypt certificate is issued for the domain and its renewal is scheduled. Nobody has to remember it in ninety days.
The records are written on our own nameserver and replicate to the secondary automatically. DNSSEC is one switch away.
You get panel credentials — files, databases, mail, FTP, backups and a change log.
The subscription goes past due and keeps serving the site for seven days. Only then is it suspended — suspended, not deleted. Your data and backups stay where they are.
Yes, and we hand over an export that works: the files, the databases, the mailboxes and the DNS records. Migrating out is not billed as a project.
A tax invoice is generated automatically on every settled payment and sent to the email you signed up with. You never have to ask for it.
On servers we operate ourselves, not an account with a provider selling you a slice. We can tell you which machine your site sits on.
Point it at our nameservers, or leave it where it is and point one record. Either way the cutover happens on your schedule and does not take the existing site down.
Then it is not an off-the-shelf plan. We run a separate track for dedicated hardware tuned to your workload — and that one starts with a conversation, not a form.
Several applications, a heavy database, or a regulatory requirement for isolated hardware. In that case we measure what runs today and fit a machine to it, rather than selling you a bigger tier.