Server and uptime management for MSPs and resellersRun the fleet, prove the uptime
When you run infrastructure for customers, reliability is the product. InfraNest gives you fleet-wide server management, multi-region monitoring and branded status pages — the backbone to deliver uptime and show it.
Free plan · No credit card · Set up in minutes
- Made in Germany
- No migration needed
- Tokens encrypted at rest
- Export anytime, no lock-in
- customer-a · web-01Up · 99.99%
- customer-b · db-primaryHigh load · 91%
- customer-c · edge-euUp · 12 ms
- customer-d · api-02Incident · investigating
- customer-e · cache-01Up · 8 ms
One fleet view across every customer and region.
The problem
When the customer finds the outage first
A customer opens a ticket at 9:14: their shop is slow. Your team checks one provider console, then another, then the monitoring tool, which shows green from the one location it checks. Forty minutes later someone finds a database server that has run out of memory. The customer found the problem before you did.
At contract renewal they ask for uptime figures. You have them somewhere, spread across three tools that each measure differently, and none of them is something you would put in front of a customer with confidence.
When you sell infrastructure, reliability is the product, and showing it is part of the job. InfraNest puts every customer’s servers, across clouds, in one fleet view, monitors them from up to three continents, and turns those checks into status pages your customers can read for themselves.
The old way
- A separate console per provider
- Uptime you assert but can’t show
- Support tickets for every status question
- Access that’s all-or-nothing
With InfraNest
- One fleet view across every provider
- Branded status pages that prove uptime
- Customers self-serving their own status
- Roles, audit trail and SSO for the team
How it works
How a reseller runs on InfraNest
Every customer’s servers in one fleet view
Connect Hetzner Cloud, DigitalOcean, TransIP and OVHcloud and every server appears in one list, with the provider’s metrics straight away. Create, power, rebuild, rescue, back up and snapshot from the same console. A one-command agent adds what no cloud API can report: memory, disk space, load average, and an alert when a machine goes quiet.
- Four clouds in one console, with nothing to install to get started
- Backups, snapshots, volumes and private networks managed in place
- The agent adds memory, disk and load in about a minute per server
- Delete protection, and a clear difference between deleting and untracking
14 servers · 12 running
Point-in-time copies of your server disks, kept even after a server is deleted.
Floating IP addresses you can attach to and move between your servers.
5 servers are polled by their provider, so memory, disk space and load are not being measured on them.
DigitalOcean — Staging1 of 5€204.00/mo
Hetzner — Production2 of 6€149.59/mo
OVHcloud — Beauharnois1€12.00/mo
TransIP — Amsterdam1 of 2€60.00/mo14 servers across 4 accounts · €425.59/mo
web-01 golden imageProtectedfrom web-01 · 80 GB disk · 6.2 GB stored6.2 GBdb-01 nightlyfrom db-01 · 40 GB disk · 11.1 GB stored11.1 GBqueue-01 weeklyfrom queue-01 · 80 GB disk · 14.2 GB stored14.2 GBapi-01 before the 2.4 rolloutfrom api-01 · 60 GB disk · 9.8 GB stored9.8 GBdb-01 before schema migrationProtectedfrom db-01 · 40 GB disk · 11.4 GB stored11.4 GBmail-01 pre-upgradeProtectedfrom mail-01 · 75 GB disk · 18.6 GB stored18.6 GB6 snapshots · 71.3 GB stored
3 attached to nothing — €6.30 a month
A reserved address keeps billing after the server it was reserved for is gone. Release it at your provider, or attach it to a server.
14 addresses across 4 accounts
Monitoring that finds the outage before your customer does
On Business and up, checks run from Europe, North America and Asia-Pacific, and a status only changes when enough regions agree. Tell InfraNest which services depend on which, and one database failure becomes one incident instead of twenty alerts. Send warnings to Slack and hard-down to PagerDuty, and let an automation open the ticket in Jira or Linear.
- Probes on up to three continents, with response times per region
- Dependencies, so the root cause alerts you once
- Maintenance windows that keep uptime figures honest
- Email, Slack, Teams, Discord, Telegram and PagerDuty
https://api.northwind.com/v1/search
Checked from 3 regions · 2 probes must agree · 2 of 3 regions must agree
A status only changes when the thresholds above are met — which is why one region having a bad second never reaches you.
Status pages that prove the uptime you sell
Each customer gets a status page built from the checks you already run, on their own domain with HTTPS handled for you. Planned maintenance shows as planned, so it does not count against the uptime figure. Every incident keeps a permanent link, and the same page has a private team view with the on-call contact and runbook links for your engineers. On Enterprise, the “Powered by InfraNest” line can be removed.
- Uptime figures from the same checks your team watches
- The customer’s domain, logo and colours
- Public or password-protected, per page
- White-label on Enterprise
What your team needs during an incident. Only people signed in to your organisation can see this page.
Overall
Major outage
Services up
6/8
Uptime · 30d
100%
Next maintenance
—
On call
Primary: Sam Okoye · +31 6 12 34 56 78 · #northwind-oncall on Slack. Escalation after 15m: Alex Rivera.
Open right now
Services · last 30 days
Public
Developer
Refreshes itself every 30 seconds, so it can be left open through an incident. The on-call note and the runbook links never reach any public payload — enforced by a whitelist and two tests, not by a filter someone has to remember.
The same safety checks on every server, in every cloud
Every server carries a standing check: is there a firewall, is SSH open to the world, is a database port reachable, is there a restore point, is anything watching it. Firewall rules are edited the same way whichever cloud the server runs on, templates give you a rule set that already works, and InfraNest will not let you apply rules that lock you out of your own server.
- Eleven standing checks on every server
- One firewall editor across clouds
- Templates for rule sets you trust
- A guard against locking yourself out
Reusable rule sets — apply a starting point to a firewall.
Web Server
Built-inFor a public website or app. Opens HTTP (80), HTTPS (443) and HTTP/3 over QUIC (UDP 443) to everyone. Add SSH restricted to your own IP separately for management.
3 rules
Mail Server
Built-inFor a self-hosted mail server. Opens SMTP (25), submission (587), SMTPS (465) for delivery and sending, plus IMAP/IMAPS (143/993) and POP3/POP3S (110/995) for clients. Open to everyone.
7 rules
DNS Server
Built-inFor a public, authoritative or recursive DNS server. Opens port 53 over both UDP (normal queries) and TCP (large responses and zone transfers) to everyone.
2 rules
Database Server
Built-inKeeps the database off the public internet — PostgreSQL (5432) and MySQL (3306) are reachable only from your private network, so your app servers can connect but the outside world cannot. The default 10.0.0.0/8 is your servers' private network, NOT your personal IP — change it to your actual private subnet (e.g. 10.0.0.0/16). To connect as an admin, tunnel over SSH rather than opening these ports to your own IP.
2 rules
Game Server
Built-inA starting point for a game server — opens the common Steam/Source ports (27015 UDP + TCP) and a generic UDP game port (7777) to everyone. Replace these with the ports your specific game uses.
3 rules
Minecraft
Built-inA Minecraft server — Java Edition on TCP 25565 and Bedrock on UDP 19132, open to everyone. Drop whichever edition you do not run.
2 rules
WireGuard VPN
Built-inA WireGuard VPN endpoint — opens the default UDP port 51820 to everyone (handshakes are cryptographically authenticated, so this is safe to expose). Change the port if you customised it.
1 rule
OpenVPN
Built-inAn OpenVPN server — opens the default UDP port 1194 to everyone. Adjust the protocol/port if you run OpenVPN over TCP or a non-standard port.
1 rule
Remote Desktop (RDP)
Built-inWindows Remote Desktop, restricted to a private network — NEVER expose RDP to the internet (it is a top attack target). The default 10.0.0.0/8 is your private network; change it to your VPN or admin range. For ad-hoc access, connect over a VPN rather than opening this to your own public IP.
1 rule
Blank Strict
Built-inThe safest starting point: blocks all inbound traffic. Nothing can reach the server until you add explicit allow rules for exactly the ports and sources you need.
0 rules
Deny all inbound
Web server (80/443)
Allow HTTP and HTTPS from anywhere, plus SSH from the office network.
3 rules
Start with your own fleet
Connect your first provider on the free plan in minutes. When you are ready to size Enterprise, talk to us.
Getting started
Bring the fleet under one roof
No agents to install, no migration.
Connect every provider
Add each cloud and registrar with a token. Servers, DNS and certificates sync into one fleet view.
Set roles and SSO
Bring your team in with SSO, give each person the right access, and turn on the audit log.
Publish status pages
Give each customer a branded status page and route incidents to the right on-call.
What you get
What changes on day one
many1
Consoles to run the whole fleet
ticketsself-serve
How customers check their uptime
guessworkSLA
Uptime you can put in a contract
Questions
Questions resellers ask
Can I separate customers cleanly?
Yes. Each customer is its own organisation with its own servers, monitors and status page, isolated from the rest.
Do you support SSO?
Every plan signs in with Google, Microsoft or GitHub. Enterprise adds single sign-on through Okta, Entra ID or any OIDC provider, SCIM provisioning and a sign-in IP allowlist, plus unlimited usage and a dedicated contact. Every change is recorded in the audit log with who made it.
Can customers see only their own status?
Yes. Give each customer their own status page, public or password-protected, on their own domain, showing only the services you choose to publish.
Is there an uptime SLA?
Enterprise comes with a dedicated contact and an SLA, so the uptime you promise your customers is backed by one to us.
Which clouds do you support?
Hetzner Cloud, DigitalOcean, TransIP and OVHcloud for servers, plus the registrars and DNS providers on the integrations page. Where a provider cannot do something, the control is greyed out with the reason instead of failing.
Do I need to install an agent on every server?
No. Connecting a provider gives you the fleet, its metrics and the full server lifecycle with nothing installed. The optional agent is one command and adds memory, disk space, load average and service checks.
Is there a DPA?
Yes. Enterprise includes a signed DPA. InfraNest is built in Germany and hosted in the EU.
Can routine work run automatically?
Yes. A rule can open a ticket, post to a status page, reboot a server, or stop and ask a named person for approval before anything irreversible. You can dry-run it against your own history before you switch it on.
Not quite you?
Manage the fleet, prove the uptime.
When you run infrastructure on behalf of customers, reliability is the product. InfraNest gives you fleet-wide server management, multi-probe monitoring, alerting and status pages — the operational backbone to deliver and demonstrate uptime.
Free plan · No credit card required · Set up in minutes