OVHcloud integration
OVHcloud in the inventory, including the parts it will not tell you
Connect OVHcloud and your zones, domains and servers arrive with everything else you run. Where OVHcloud gives an answer, InfraNest shows it. Where it does not — and it gives no server metrics — the page says so instead of drawing an empty chart.
Free plan · About 3 minutes · One-click connect available
- Zones discovered on connect, records edited from here
- Domain expiry, nameservers and transfer lock tracked
- Delete protection OVHcloud does not offer natively
- An honest blank where OVHcloud has nothing to give
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.
DigitalOcean — Staging1 of 5€204.00/mo
Hetzner — Production2 of 6€149.59/moOVHcloud — Beauharnois1€12.00/mo
TransIP — Amsterdam1 of 2€60.00/mo15 servers across 5 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 GBshop-old before shutdownfrom shop-old · 80 GB disk · 21.5 GB stored21.5 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 GBstaging-data before the 2.4 migration100 GB disk · 5.9 GB stored5.9 GBstaging-data nightly100 GB disk · 6.4 GB stored6.4 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 GB9 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
Zones found on connect, records edited from here
Existing OVHcloud zones are discovered and imported the moment the connection is made, so there is no re-entering records you already have. A, AAAA, CNAME, MX, TXT and the rest are edited in the editor every other provider’s zones use, each edit going straight to OVHcloud, and each record tracked individually so a change made on either side still lines up.
- Existing zones discovered and imported on connect
- All the standard record types, edited from one place
- Edits sent straight to OVHcloud
- Per-record change tracking, so nothing drifts silently
Domains you can see without logging in
Expiry dates, nameservers and transfer lock state are read from OVHcloud and shown in the portfolio with every other registrar’s names. Registration and transfer-in run from here; renewal is the one that still happens on OVHcloud’s own site, and the page tells you that rather than letting you find out on the day.
- Expiry, nameservers and transfer lock, without the control panel
- Registration and transfer-in from InfraNest
- Beside the names you hold at every other registrar
- Renewal stays at OVHcloud — stated, not discovered
Delete protection OVHcloud does not have
Some clouds enforce a "do not delete" flag themselves. OVHcloud does not, so InfraNest holds the lock instead: a protected resource refuses to be deleted through InfraNest’s own server management, whether the delete comes from a click, a bulk action, or an automation running at three in the morning. It is not a feature of OVHcloud — it is a guard in front of it.
- Protection enforced by InfraNest where the cloud has none
- Holds for bulk actions and automations, not just single clicks
- A delete made in OVHcloud’s own panel is still OVHcloud’s to allow
Delete — the machine goes
Destroys mail-01 at your provider. The billing stops.
At TransIP this is a cancellation: the machine keeps running until the end of the period you have already paid for.
Of your accounts, only TransIP works that way — and the confirmation says which of the two you are about to do.
Type the server name to confirm deletion:
Plus your organisation’s re-authentication where it is required — passkey, code or password. The capability check runs first, so you are never asked for a passkey for an action the provider was never going to allow.
Stop tracking — the machine stays
mail-01 will disappear from your server list, monitoring and cost reports. Nothing happens to the machine itself.
The server keeps running and your provider keeps charging for it. To stop paying, delete it at the provider instead.
You can bring it back at any time from Servers → Not tracked. Its metrics, tags and settings are kept.
No re-authentication, deliberately: gating the reversible button would push people towards the one that is not.
Two locks, and either one is enough to refuse
InfraNest’s delete lock
Guards deletion, rebuild and restore through InfraNest (and, where supported, the provider). It can’t stop changes made in your provider’s own dashboard.
TransIP’s own protection
TransIP declares no protection of its own, so ours is the only lock. That is not reported as “off” — the cloud simply never offered one.
Enforced at the deletion itself rather than on the API route, so it also refuses a rebuild, and a delete arriving from an automation or a background job.
See your own OVHcloud account in InfraNest
Free plan, no credit card. Connect once and the zones, domains and servers appear on their own.
Connect OVHcloud in about three minutes
One-click OAuth if you would rather not handle keys, or an application key pair created in OVHcloud’s API console. Either route covers DNS, domains and servers together.
- 1
Pick your region
Choose the OVHcloud platform your account signs in to (Europe, Canada/Asia-Pacific, or United States) — this decides which account InfraNest talks to, under Integrations > OVHcloud.
- 2
Connect your account
Select Connect with OVHcloud and approve access, or use an API key if one-click sign-in isn't available for your region yet.
- 3
Choose what to manage
Turn on DNS, Domains and Servers as needed, then select Connect — your zones, domains and VPS instances appear right after.
That’s it — OVHcloud is connected.
Full setup guideSet up with AI
I use OVHcloud and I want to connect it to InfraNest (infranest.io) — it manages DNS, domains and servers across providers. OVHcloud can be connected either with one-click OAuth or with an application key pair created at the OVHcloud API console (eu.api.ovh.com/createToken). Help me decide which route to take and walk me through it: what the OAuth option grants compared with a key pair, what scopes or endpoint patterns a key pair needs for DNS zones, domains and servers, whether keys can be given an expiry, and how to check the credentials work before I paste them in.
What syncs
What InfraNest keeps in sync with OVHcloud.
| Cloud resources | Servers, volumes, firewalls, networks and load balancers |
| DNS zones | DNS zones and records |
| Domains | Domains, expiry dates, nameservers and lock state |
What still happens at OVHcloud
InfraNest can't manage certificates through OVHcloud, and renewing a domain stays on OVHcloud's own site — InfraNest can turn auto-renew on or off but won't process the renewal itself.
MCP server
OVHcloud in Claude and ChatGPT
Connect your AI assistant to InfraNest and ask about your OVHcloud account in plain words, next to every other provider you use. It reads, and acts only when you allow it.
- Which of my OVHcloud servers are running out of disk?
- Which of my OVHcloud domains expire in the next 60 days?
- Where does shop.example.com point, and did anything change there this week?
Questions about the OVHcloud integration
#Will this find my existing DNS zones and domains automatically?
Yes. Once connected, your existing zones are found and imported, and your domains — with their expiry dates, nameservers and lock state — show up without you re-entering anything.
#Can I register or renew domains through InfraNest?
You can register new domains and transfer existing ones in from InfraNest. Renewing a domain stays on OVHcloud's own site, though you can still turn auto-renew on or off here.
#What happens if my OVHcloud credential expires or is revoked?
InfraNest will flag the connection as failing and pause the affected features until you update the credential — nothing is deleted on either side in the meantime.
#Does editing a DNS record in InfraNest change it at OVHcloud too?
Yes. Records are created, edited and deleted directly on OVHcloud, and because each record has its own identifier there, InfraNest can tell correctly when one was changed outside InfraNest as well.
#What do I need before connecting OVHcloud?
You need an OVHcloud account for the correct region (Europe, Canada/Asia-Pacific or United States), either for one-click sign-in or to create an API key — see the setup guide.
#Is there a OVHcloud MCP server?
Yes, through InfraNest. Once OVHcloud is connected, InfraNest’s MCP server lets Claude, ChatGPT, Cursor, VS Code and other assistants read your servers, domains and DNS records at OVHcloud, together with every other provider you use. It works on every plan, including Free.
Bring OVHcloud into one inventory
Connect in about three minutes, then add the next provider. Everything you run, in one place — including what the provider will not tell you.
Free plan · No credit card required · Set up in minutes