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’s API answers, InfraNest shows it. Where it does not — and it does not expose server metrics — the page says so instead of drawing an empty chart.
Free plan · About 3 minutes · One-click OAuth 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 the API has nothing to give
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/moOVHcloud — 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
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 claim about OVHcloud’s API — 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
Open the OVHcloud integration
Go to Integrations and open OVHcloud.
- 2
Pick your API region
OVHcloud Europe, Canada/Asia-Pacific and United States are separate platforms — choose the one matching the site you log in to.
- 3
Connect with OAuth or a token
Select Connect with OVHcloud for one-click access if available, or create an API token using the link provided, which opens with the right permissions pre-selected.
- 4
Choose your features and connect
Select DNS and Domains, then select Connect.
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 doesn't manage certificates through this integration, and domain renewal still happens on OVHcloud's own site rather than through InfraNest.
Questions about the OVHcloud integration
#Does this work with OVHcloud US and OVHcloud Europe?
Yes, but they're separate platforms and an account from one doesn't work on the other. Pick the matching API region when you connect — using the wrong one causes an authentication error right after connecting.
#What happens if my API token expires or is revoked?
InfraNest stops being able to read or change anything at OVHcloud until you reconnect with a new token or OAuth. Nothing is deleted on either side — your zones, domains and servers stay as they were, and syncing resumes once you reconnect.
#Can InfraNest register or transfer a domain for me?
Yes, domain registration and transfer-in can be done through InfraNest. Renewals, though, still happen on OVHcloud's own site.
#Can InfraNest stop someone from deleting my server by accident?
Yes — InfraNest can lock a server, volume, firewall, network or load balancer so it can't be deleted through any interface, API, bulk action or automation, something OVHcloud does not offer on its own. It can't stop a deletion made directly in OVHcloud's own dashboard.
#Will editing DNS here affect records I manage manually?
No — every record at OVHcloud has its own identifier, so an edit in InfraNest changes exactly the record you meant, and InfraNest can tell when a record was changed outside it too.
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