You didn't get into DevOps for this:
Stop being the help desk for dev VMs.
Developers start, stop, resize, and wake their own machines, inside guardrails you define, every action logged. You have real work to do.
Ready for your existing AWS and Google Cloud resources. No migration, no rebuilding instances. Just a trust role between your account and the Deployport account.
Your cloud credentials never leave your account. You grant a scoped role, and you can revoke it in one click.
Two commands, on a server you already run.
Free for your first 3 hosts. No credit card.
curl -fsSL https://get.deployport.com | sh For you
Who it's for
Whoever wants to spend more time being productive without migrating clouds.
Founders
You pay for every box. Idle machines put themselves to sleep and the bill drops, without anyone changing how they work.
DevOps
Often the whole platform function is one or two of you. The dev-environment tickets stop landing on your desk, because the policy does the babysitting and the team serves itself.
Developers
Your box stays yours. Wake it yourself, hold it awake through a long build, and nobody has to approve it.
How it works
Our agent daemon, plus our globally available control plane.
Nothing is overkill when it comes to saving you time and money.
The math
Pays for itself twice: the cloud bill, and your attention.
The obvious return is the cloud bill, and that is the number that clears procurement. The one you feel is the other column: every request to wake a box, every disk that filled up on a Sunday, every machine you shut down because nobody else was going to. Those are interruptions to the work you were actually hired for.
that never reach you about 0 hrs back every month, and none of it arriving mid-sentence
Wardens
Small jobs that watch one thing each, and say what they did.
A warden is one narrow responsibility running on your machines: notice a disk filling, catch an out-of-memory kill, stop a box nobody is using. You switch on the ones you want and set their thresholds, and from then on they either tell you something worth knowing or take an action you already approved. Nothing here is a dashboard you have to remember to read.
- Watches
Notice when a machine disconnects
Reports a machine that stops responding, and stays quiet when it was stopped on purpose.
- Watches
Report kernel out-of-memory kills
Names the process the kernel killed, within seconds, from the host's own kernel log.
- Watches
Warn on sustained memory pressure
Warns when memory use stays high for a whole window, so a build spike never pages anyone.
- Watches
Warn before a disk fills
Warns on a used-space threshold, and predicts when a volume will fill from its own growth rate.
- Acts
Stop machines that are idle
Turns a machine off once it has been idle, after warning whoever is on it, and lets a developer hold it awake.
- Acts
Reclaim disk space with Docker
Prunes Docker when the disk is under pressure, with a cooldown so a build cache is not killed by a thousand cuts.
- Acts
Reclaim disk space from developer caches
Measures the caches Go, npm, pip and Cargo leave behind, and clears them when you ask. Never on its own.
The watching ones are free on every tier and need no permissions in your cloud at all. The three that act ask for their own small set, only when you turn that one on.
Questions
The things people ask before they install it.
Is this a platform I have to adopt?
It is a platform, and that is the point: we run the control plane and the console so you do not have to. Your workloads stay exactly where they are, enrolling a box takes two commands, and there is nothing to migrate and nothing new for you to operate.
How is this different from a CDE like Coder or Codespaces?
They create and own the environment, so adopting one is a migration. Uplink installs on the machines you already run and leaves them yours.
We already have SSM and SSH. Why add this?
Those give your team root with extra steps, and root is the thing you were trying not to hand out. Uplink gives them a fixed set of buttons instead, dry-run first, every action recorded against the machine it touched.
We already have Datadog. Does this replace it?
No, and it does not try to. Monitoring tells you a disk is filling; Uplink ships the verdict with the fix attached and can carry it out. It also turns machines off, which is something a vendor billing you per running host is never going to build.
What access to my cloud does this need?
A trust role you create in your own account and can revoke at any moment. You never hand over a key. It also starts at zero: diagnostics need no cloud permissions at all, and each capability asks for its own small set only when you switch that capability on.
What stops it turning off a machine somebody is using?
Idleness is measured, not assumed: a machine that is working does not qualify, whatever the clock says. Before anything happens the person using it is warned, and they can hold the machine awake themselves without asking you.
Hang on, I could vibe-code this in 15 minutes.
You could vibe-code version one in 15 minutes, and it would be a cron job that turns machines off. Then it kills somebody's build at 4pm, and now you own version two: idleness that can tell a compile from an idle shell, a warning before anything happens, a hold the developer can press without asking you, the audit trail, and the permissions to go under all of it. That is not 15 minutes, it is a side project with a pager. It is your time and we do respect it. It is also $7 per host per month if you would rather have the Saturday.
From the founder
We were spending about 9k a month on dev environments, and my one devops engineer was constantly getting distracted by vm-related tickets. At some point we introduced a weekend and nightly schedule to turn those machines off, and it was so inflexible it hurt more than it helped. So I built the version I actually wanted, one that frees up the devops person without the rest of the team feeling it.
Johan, Deployport
The last VM ticket you'll ever close.
curl -fsSL https://get.deployport.com | sh Your cloud credentials never leave your account. You grant a scoped role, and you can revoke it in one click.