Blog

The perfect server on ServersCamp

Anyone who has run servers knows how much routine comes before even a clean one is ready. Monitoring, useful alerts, off-site backups and a disk that grows before it fills up are built into ServersCamp, with the decisions already made, on every plan.

Card payments are live, and the welcome credit moves to the card

ServersCamp now runs as a production service. Top-ups by card start at EUR 10, every payment comes with a fiscal invoice by email, and the EUR 25 welcome credit is issued when you save a card. How prepaid billing, Stripe, 3D Secure and VAT work from today.

Off-site backups in another country: why ours leave Romania

A data centre is a building with an address, and a backup kept at the same address shares its fate. Why every disaster-recovery backup we take is encrypted with your key and stored with another provider in another country, how the copy is verified, and four questions to ask about your own backups.

ServersCamp is out of beta

Today we switch to Early Access. Billing is on, accounts are prepaid, and existing accounts have received compensation credits. A short note on what changed and what we are still tuning.

New rules for trial accounts

Mining, crawling, scanning and outbound spam on a trial account now stop by themselves, usually inside a minute. The rules went into the terms of service today. This post covers what the platform watches for, where the thresholds sit, and what to do if your work legitimately needs one of them.

Beta is ending. Here's what happens next.

ServersCamp is moving from beta to production. Before the interesting parts, one unglamorous step: we need to know your email actually works. And for the people who were here first, a credit gift based on what your account normally used during the beta.

The benchmark we expected to lose

We took vanilla PostgreSQL and ran it against Hetzner premium hardware: their local NVMe versus our replicated network disk, on the workload where network storage is supposed to get slaughtered. We did not know the result in advance, seriously. This is how it went.

We pointed a load balancer at nothing. The internet showed up anyway.

We put a brand-new load balancer in front of a server that hosts nothing. Within a day it had been contacted by 113 clients from 20 countries, and more than a third were already on public threat lists. A look at the background noise of the internet, and why a balancer should be able to say no on its own.

Most people think they have backups.

Snapshots, a multi-region copy, a thing called "Backup" in a panel. Most of the time it is enough. Disaster recovery is about the day it is not. A walk up the failure ladder, from a bad migration to your provider disappearing.