HostAtlas · Solutions · For solo founders
Solutions · For solo founders

All the ops knowledge
you don’t have to have.

You ship the product, write the marketing, answer the support email and remember to renew the domain. Ops should be the thing that just keeps working. HostAtlas’s defaults are the ones a senior SRE would set if they were doing this for you: auto-recovery before the page, encrypted off-site backups with a ransomware gate, AI triage when something goes sideways at the wrong moment.

your week · summary
mon 04:12● php-fpm auto-restart · no page
tue 03:00● off-site backup · 4.2 GB · ransomware-gate ok
wed 22:18● certificate renewed · api.example.com
thu 09:42● disk forecast · 38 d to 90% · stable
fri 14:01● queue backlog growth · 1 ack · digest
— 1 thing to read · 0 things to do —
1 install
One agent install on one box brings auto-discovery, metrics, log tail, backup runner and recovery online.
$0 / first host
Free tier covers a single server forever. You don’t pay until your fleet grows past the one box.
AES-256 client-side
Backups encrypted on the host before they leave. Even our backup provider only sees ciphertext.
03:42
The hour Auto-Recovery is designed for. The page no longer fires; you read the audit log on Monday.
— The reality of solo ops

Four problems that hit every solo founder.

Not theoretical SRE concerns. The actual time-and-attention drain of being the only one who knows where the servers live.

01

You don’t want to be the on-call human.

A PHP-FPM segfault at 03:42 is not a learning experience — it’s 90 seconds of systemctl restart and three days of bad sleep. Auto-Recovery does the 90 seconds; you read the daily digest on Monday.

02

Backups are the silent killer.

You set them up once. You assume they run. You find out they didn’t when you need them, which is the worst possible time. Off-site backups ship with their own monitoring and a ransomware gate that refuses encrypted uploads.

03

Ops decisions distract from product decisions.

Every dashboard you build, every alert you wire, every monitor you forget — that’s time not spent on the thing customers actually pay for. Sensible defaults mean fewer of those decisions per week.

04

One bad incident burns trust faster than you can rebuild it.

Customers don’t remember 99.9% uptime; they remember the day the API was 502 for an hour. A public status page, auto-synced and honest about what’s happening, is what they look at first.

— Defaults that kick in for you

What happens the day you install the agent.

Not "and then configure". These are the things that work from the second your first host enrols.

01 · Inventory

Server Auto-Discovery, instant.

Deep page →

The agent catalogs services, containers, certificates, cron jobs, listening ports, OS packages, network interfaces — within thirty seconds of install. Domain discovery from nginx / caddy / apache config follows automatically.

You stop wondering "what runs on web-prod-04". The platform has it on the host page.

02 · Self-heal

Auto-Recovery on common services.

Auto-Recovery →

Default policy on nginx, php-fpm, caddy, redis, workers: auto_once with a 10-minute cooldown. A single crash → service restarts → you get a digest entry, no page. A second crash within the cooldown → then you get a page.

Databases are manual by default. You opt in if and when you trust the policy.

03 · Backup

Off-site backups + ransomware-gate.

Off-site backups →

Backups encrypted with AES-256-GCM on the host before they leave the machine. Stored on Hetzner S3 (EU residency). Each upload runs through entropy + magic-byte detection — if a backup looks encrypted by something that isn’t us, the off-site gate refuses it.

You don’t want the day your laptop’s key vault breaks to also be the day ransomware overwrites your good backups.

04 · Alerting that doesn’t scream

Smart Alerts with hysteresis.

Smart Alerts →

Anti-flapping clear thresholds, durations, severity routing. The default rule set is the one a senior operator would write for a small fleet: page only on sustained problems; warn only on real anomalies; ignore the rest.

One Slack channel, one email address, one mobile push category. Tune later.

05 · A second brain when you need it

AI Triage drafts the explanation.

AI Triage →

When something does go sideways, AI Triage opens the incident with a root-cause hypothesis already drafted, evidence cited, the most likely fix surfaced as a runnable recipe. Your job is to read it, not to assemble it.

06 · Customer-facing

Public status page, auto-synced.

Public status pages →

Branded. CNAME'd to status.your-domain.com. Components reflect your real monitors; incidents auto-post. Customers stop emailing you "is it down?" because the page tells them.

— A week, narrated

What it looks like when ops just works.

Five workdays. One thing that needed your eyes. Zero things that interrupted real work.

Mon 04:12 autophp-fpm on api-prod crashes. Restart within 4 seconds. Probes recover, audit logged. You don’t notice until Monday morning’s digest.
Tue 03:00 autoOff-site backup run starts. 4.2 GB compressed, encrypted on the host, shipped to Hetzner S3. Ransomware gate: entropy check passed.
Wed 22:18 autoLet’s Encrypt renewal for api.example.com succeeds. New cert chain pushed; uptime monitor verifies; old cert filed.
Thu 09:42 infoCapacity outlook: disk on db-prod-01 projected to hit 90% in 38 days. Provider plan suggestion attached.
Fri 14:01 warnEmail queue wait time climbing — p95 over 8 seconds for 5 min. Bell ping, no page. AI Triage: "SES rate limit hit; backlog clearing slowly."
Fri 14:04 humanYou ack from the bell, request a rate-limit raise from SES, file it. 3 minutes of attention total.
Sun 18:00 infoWeekly digest email: 1 acted-on warning, 0 pages, 7 auto-recoveries, 7 backup runs, 3 cert events. Status page uptime: 99.98%.
— Pricing fit

Priced like a tool, not a trap.

Free covers a single host forever, including the agent, auto-discovery, basic alerting, public status page. The features that earn paid plans are the ones a growing solo product genuinely needs.

Free
Starter
Pro
Hosts
1 forever
10
50
Server Auto-Discovery + metrics
Included
Included
Included
Auto-Recovery
Included
Included
Included
Off-site backups + ransomware-gate
20 GB / host
200 GB / host
2 TB / host
AI Triage
Manual run
Per-incident, automatic
Plus root-cause assistant + recipes
Public status page
HostAtlas-branded
Custom domain
Custom domain + subscribers
Vulnerability scanning
Monthly
Weekly
Daily + real-time alerts
— From here

Three steps. Quiet ops within an hour.

01

Install on your one production box.

One curl | bash. Auto-discovery runs immediately. Domains + certs + services come online without you typing them in.

Install →
02

Turn on off-site backup.

Generate your master key, point at your backup paths, schedule daily. The ransomware-gate runs automatically. Free tier gets 20 GB.

Off-site backups →
03

Connect your status page.

Take the auto-generated public URL or CNAME it to your own domain. Components light up from your real monitors immediately.

Status pages →
— FAQ

Questions solo founders actually ask.

Do I need to know ops to set this up?+
No — the defaults are the point. The install command is one line, the platform suggests what to enable next, the bell tells you when something needs reading. The configuration that’s required is zero.
Can I run HostAtlas on a single $5 VPS?+
Yes. The agent is small enough to run alongside your app on a single small box. The platform is hosted by us; the VPS only carries the agent and your application.
What if I migrate hosts?+
Each host has a stable UUID derived from machine-id, so a hostname change doesn’t fragment the timeline. A full migration to a new box: install the agent there, enroll, the new host appears; archive the old one when you’re ready.
What if I just want backups, nothing else?+
That works — install the agent, enable the backup runner, ignore the other features. Auto-discovery still runs, but you don’t have to look at it. Most founders enable more over time; some never do.
What does the ransomware-gate actually check?+
Entropy of the backup stream + magic-byte presence at known offsets. A normal compressed-and-encrypted-by-us backup looks predictable in entropy; a ransomware-encrypted file looks too random. We refuse uploads that fail the check before they overwrite the previous generation.
EU data residency?+
Yes — EU instance for the platform (Frankfurt + Helsinki). Off-site backups land in Hetzner S3 (EU). No leg outside the EU on the EU instance.

Ops you don’t have to think about.

Free tier covers your first host forever. Add the agent, watch what happens.

Get early access See pricing