Internal apps.
That keep running.
Run monitoring, a wiki or an admin tool on two machines under one name. If one stops, everyone moves to the other on their own, and nobody has to change a bookmark.
grafana, last 30 days
100%
available, every day
serving
stopped
mon-a
mon-b
mon-a stopped
grafana moved to mon-b. Nobody had to do anything.
One machine down
shouldn't mean the app is down.
Give the app its own name, and put more than one machine behind it.
The usual way
- 01The app goes down with its machine
- 02Bookmarks point at one machine's address
- 03Updates wait for a quiet evening
With a private network
- 01The name and address belong to the app
- 02If a machine stops, everyone moves over
- 03No load balancer, no DNS changes
Three steps.
Then it looks after itself.
Name the app, run it on more than one machine, and approve them.
- 1
Give the app a name
Add a service in the dashboard with the port it uses. It gets its own name and address.
New serviceName
grafanaPorts
tcp:443Create service - 2
Run it on two machines
On each machine running the app, one command says this machine serves it, and where the app listens.
deploy@mon-b$ underpass serve --service=svc:grafana --tcp=443 127.0.0.1:3000
Serving svc:grafana on port 443 from mon-b.
- 3
Approve them
Approve each machine under Services in the dashboard. From then on, people just open grafana.
grafana · hosts100.100.0.7Servingmon-a
approved
Approvemon-b
wants to serve grafana
Uptime without
the usual machinery.
The parts that usually take a load balancer and a weekend.
- Automatic failoverA machine that stops checking in counts as offline after 90 seconds; everyone moves over.
- One name, foreverSwap or retire machines behind it without telling anyone.
- Calm maintenanceStop serving on a machine first, and people move to the backup right away.
- Private by defaultOnly your network can reach it, and access controls narrow it further.
Questions about uptime.
Something we didn't cover? Write to us and we'll help you get set up.
Ask us anythingIf a machine stops checking in, it counts as offline after 90 seconds and everyone moves right after. If you stop serving on it first, they move right away.
/ Independent · bootstrapped · no investors
Built by a person,
not a fund.
I'm Endi, and I build Underpass myself. No investors to answer to, only the people who run their networks on it. Every message that comes in reaches me directly.