DigitalOcean integration
Droplets you can actually see the shape of
Connect a DigitalOcean account and every Droplet, volume, firewall, network and DNS zone in it appears in InfraNest — with CPU, memory, disk and network read from DigitalOcean’s own metrics, beside the machines you run at other providers.
Free plan · About 2 minutes · One token covers Droplets and DNS
- Real CPU, memory, disk and network per Droplet
- Power, reboot, rebuild, snapshots and weekly backups
- Zones discovered on connect, records for any registrar’s domain
- Certificate expiry tracked with everything else
api-02web server
cpx41 · Falkenstein · a reading every 5 minutes
CPU
46%
of 8 vCPU
Memory
needs the agent
Disk
needs the agent
Load average
needs the agent
Memory, disk space and load need the agent on this server: Hetzner sees the machine from the outside.
api-01web server
cpx41 · Falkenstein · a reading every minute
CPU
50%
of 8 vCPU
Memory
62%
of 16 GB
Disk
44%
on /
Load average
4.03
8 cores
What the agent adds
- An alert when the server stops reporting at all — the one thing polling structurally cannot notice.
- The processes using the most CPU and memory, sampled on the machine itself.
- What is filling the disk — the largest folders on the fullest mount, so “94% full” arrives with something to delete.
- The services the machine was told to run, and in plain language why any of them failed.
One command, about a minute — and the same command on every server, whichever cloud it is on.
Droplets in the same list as everything else
Size, region, addresses and tags arrive with each Droplet, and the routine actions come with them: power on and off, reboot, rebuild, snapshot, and DigitalOcean’s weekly backups toggled from here. They sit in one fleet list with every other cloud, which is the only view that answers "what am I actually paying for" in one go.
- Power, reboot, rebuild and snapshot
- Weekly backups turned on and off from here
- Size, region, addresses and tags on every row
- Volumes, firewalls, networks and load balancers read into your inventory
- Several DigitalOcean accounts at once
15 servers · 13 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.
4 servers are polled by their provider, so memory, disk space and load are not being measured on them.
15 servers across 5 accounts · €425.59/mo
9 snapshots · 105.1 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
DigitalOcean DNS for a domain you bought anywhere
DigitalOcean will host a zone for any name you point at it, and InfraNest finds the zones you already have the moment you connect. Records are created, edited and deleted in the editor your other providers’ zones use, and each one keeps its own DigitalOcean identifier — so an edit changes the record you meant, and a change made outside InfraNest still lines up.
- Existing zones discovered and imported on connect
- Records for any domain pointed at DigitalOcean, whoever sold it
- Per-record identity, so edits land where you meant them
- Changes made in DigitalOcean’s panel still match up here
VPCs, and the machines sitting on them
Private networks come in with their CIDR ranges and the Droplets attached to them, so the question of what can reach what has an answer that does not involve reading a diagram someone drew last year. DigitalOcean is also one of the few clouds where a machine can join a network as it is created, rather than being attached afterwards.
- Private networks with their ranges and members
- Droplets joined to a network at creation, not after
- Read beside the networks you run at other providers
6
servers
2
subnets
0
routes
In plain English
private-backbone is a private network in eu-central. 6 servers are connected over private IPs. No routes — traffic stays inside 10.0.0.0/16.
What attaching a server grants
6 servers are on this network today, and every one of them becomes reachable from the new one on its private address — on every port it exposes there. There is no allow step in between.
Staying off a private network is not treated as a problem to fix. A CI runner, or a public site with nothing to share, has no reason to join one. We removed a banner that suggested otherwise: we hold no traffic data, so it was an opinion rather than a measurement.
Certificates, counted once
Certificates held at DigitalOcean appear in your certificate list with their expiry dates, next to the ones at your other providers and the ones your servers issued themselves. Expiry stops being something you check per account and becomes something you are told about.
- DigitalOcean certificates with their expiry dates
- One list across every provider and every server
- Warned ahead of expiry, not after the outage
See your own Droplets in InfraNest
Free plan, no credit card. Connect an account and the Droplets, zones and certificates appear on their own.
Connect DigitalOcean in about two minutes
One personal access token from the API section of your DigitalOcean account. Read & Write if you want to act on things from here — a read-only token still shows you everything.
- 1
Open the DigitalOcean integration
Go to Integrations and open DigitalOcean, then give the connection an Account label if you're connecting more than one account.
- 2
Pick what to use it for
Choose Servers, DNS and Certificates depending on what you want InfraNest to manage.
- 3
Connect your account
Select Connect with DigitalOcean and approve it, or paste an API token, then select Connect.
That’s it — DigitalOcean is connected.
Full setup guideSet up with AI
I use DigitalOcean and I want to connect it to InfraNest (infranest.io) — it manages servers, DNS and certificates across providers. It needs a DigitalOcean personal access token, created under API → Tokens/Keys. Walk me through creating one: where that screen is, what the Read and Write scopes each allow, whether the token can be given an expiry, and how to check it works before I paste it in. Also tell me what a read-only token would stop me doing.
What syncs
What InfraNest keeps in sync with DigitalOcean.
| Cloud resources | Servers, volumes, firewalls, networks and load balancers |
| DNS zones | DNS zones and records |
| Certificates | Certificates and their expiry |
What still happens at DigitalOcean
InfraNest can't register, renew or transfer domains through DigitalOcean — that stays with whoever you bought the name from. DigitalOcean only hosts the DNS for it here.
MCP server
DigitalOcean in Claude and ChatGPT
Connect your AI assistant to InfraNest and ask about your DigitalOcean account in plain words, next to every other provider you use. It reads, and acts only when you allow it.
- Which of my DigitalOcean servers are running out of disk?
- Where does shop.example.com point, and did anything change there this week?
- Which certificates expire this month, and does anything renew them?
Questions about the DigitalOcean integration
#Will connecting DigitalOcean move my domain's registration?
No. DigitalOcean hosts DNS for a domain registered anywhere — you point the domain's nameservers at DigitalOcean, and the registration itself stays exactly where it is.
#What happens if my API token expires or gets revoked?
The sync stops as soon as the token is no longer valid. If you used a token to connect, either give it no expiry or diarise the renewal; one-click connect avoids this because there's no token to expire.
#Can InfraNest stop someone from deleting a server by accident?
Yes — InfraNest can lock a server, volume, firewall, network, snapshot or load balancer against deletion, something DigitalOcean does not offer on its own. The lock blocks deletion through the interface, the API and automations, but not a deletion made directly in DigitalOcean's own dashboard.
#Does InfraNest change anything in my DigitalOcean account on its own?
Only the changes you make from InfraNest — creating or editing a Droplet, volume, firewall, load balancer or DNS record — which are sent straight to DigitalOcean. InfraNest doesn't make changes in the DigitalOcean panel independently of what you do here.
#What do I need before connecting DigitalOcean?
Either approve the one-click connection, or create an API token with the scopes for the features you're enabling — see the setup guide.
#Is there a DigitalOcean MCP server?
Yes, through InfraNest. Once DigitalOcean is connected, InfraNest’s MCP server lets Claude, ChatGPT, Cursor, VS Code and other assistants read your servers, DNS records and certificates at DigitalOcean, together with every other provider you use. It works on every plan, including Free. DigitalOcean also runs its own MCP server for your DigitalOcean account alone. InfraNest’s answers across all your providers, with your monitors and incidents in the same answer.
Bring DigitalOcean into one dashboard
Connect an account in about two minutes, then add the next provider. Everything you run, in one place.
Free plan · No credit card required · Set up in minutes