HomeProvider guide

Provider guide

Host Next.js on OVHcloud

Deploy Next.js on an OVHcloud Public Cloud instance with region, network, firewall, DNS, TLS, cost, and rollback guidance.

Plan an OVHcloud deployment Read the resource

By HostNextJS Editorial TeamReviewed by HostNextJS Technical Review Published July 12, 2026Updated July 12, 2026

01Typeprovider

02Last reviewedJuly 12, 2026

03Update policyCheck regional prices every 30 days; review Public Cloud networking and deployment modes every 90 days or after a material change.

Provider-specific scope

What is specific to OVHcloud

This guide uses OVHcloud Public Cloud instances and their OpenStack model: 1-AZ, 3-AZ, or Local Zone placement, security groups, Basic or Floating public IPs, optional vRack networking, and OVHcloud DNS. It does not substitute OVHcloud VPS or Web Hosting instructions.

Products and locations

Choose the right provider surface

01Discovery instances use shared resources for testing and light workloads; General Purpose instances are the clearer production baseline when balanced CPU and memory are required.
02Choose between 1-AZ, 3-AZ, and Local Zone regions only after reviewing resilience and networking differences; product and model availability varies by location.

Before you start

Prerequisites

01An OVHcloud account with a Public Cloud project and sufficient quota
02A public SSH key stored locally or in the project
03A domain and access to its authoritative DNS zone
04A tested Next.js build, backup scope, and rollback plan

Manual path

Deployment sequence

01Create the instance
Select the location, instance model, maintained Linux image, SSH key, backup policy, network mode, public IP type, and hourly or monthly billing in the Public Cloud project.
02Define security groups
Use OpenStack security groups to permit public HTTP and HTTPS, restrict SSH by source, and avoid an ingress rule for the private Next.js application port.
03Deploy the Next.js runtime
Install a supported Node.js version, deploy an immutable or standalone artifact, and supervise the unprivileged process behind Nginx or another reverse proxy.
04Set DNS, TLS, and cutover
Point the A record to the Basic Public IP or reusable Floating IP, issue TLS after resolution, run production checks, and retain the previous target for rollback.

Network and domain

Firewall, DNS, and TLS

01Choose Basic Public IP for an address tied to the instance lifetime or Floating IP when the address must move between instances.
02Use vRack/private networking for internal services where applicable; verify gateway and Local Zone limitations before launch.
03Apply an OpenStack security group and a compatible guest firewall with public 80/443 and restricted 22 only.
04Update A and optional AAAA records at the authoritative DNS provider, then test TLS renewal, streaming, and the certificate chain.

Dated examples

Cost reference

01 · Discovery d2-4USD 0.0244/hour

Worldwide page example for 2 vCores, 4 GB RAM, and 50 GB storage, checked 2026-07-12; location, billing mode, currency, and tax affect the total.

02 · General Purpose b3-8USD 0.0605/hour

Worldwide page example for 2 vCores, 8 GB RAM, and 50 GB NVMe, checked 2026-07-12; the displayed rate may reflect selected pricing options.

03 · Floating IPv4USD 0.0032/hour

Worldwide public pricing example for a Floating IP /32, checked 2026-07-12.

HostNextJS is not affiliated with or endorsed by OVHcloud. Product names and dated public prices are included for independent evaluation.

OVHcloud Public Cloud is a good fit when European infrastructure, OpenStack compatibility, or a broader private-network design matters. It is not one uniform VPS screen: deployment mode, region, flavor, IP type, security groups, and billing mode are separate decisions.

Select the deployment mode before the flavor

The location selector can represent a 1-AZ region, a 3-AZ region, or a Local Zone. These modes differ in resilience and network capabilities, so do not choose only by city name. Keep the Next.js server near its database and object storage, and verify that the required instance flavor and services exist in the same location.

Discovery instances use shared resources and are positioned for testing and development. For a production application, start from observed CPU and memory needs and compare General Purpose or another appropriate flavor. OVHcloud allows upward resizing of regular instances but not normal downsizing; flexible instances have different disk constraints and permit both directions.

Treat networking as an architecture choice

A Basic Public IP is free and tied to the instance lifetime. A Floating IP is billed separately but can be reassigned, which is useful for replacement-based deployment and rollback. Private networks use vRack, and a private-only design may need a gateway. Document this before provisioning rather than retrofitting it during cutover.

OVHcloud Public Cloud security groups use the OpenStack model. Confirm the group associated with the instance and inspect its effective ingress rules. Public 80 and 443 belong at the reverse proxy; the Next.js process should listen privately. Restrict SSH to administrative sources and keep guest firewall rules aligned.

Verify backup and cutover behavior

The current creation flow enables automated backups by default, with a selectable retention rotation. Confirm that this is intended and priced for the chosen configuration. An instance backup does not replace database, object-storage, secret, or DNS recovery.

Before changing DNS, test the production hostname against the candidate IP, including dynamic routes, image optimization, streaming, cache behavior, and graceful shutdown. Keep the former instance or artifact usable until the rollback window closes.

Methodology

How this resource was produced

The guide maps OVHcloud's documented Public Cloud instance, OpenStack security group, public or Floating IP, vRack, backup, and DNS controls to a standard Next.js Node.js deployment. Price examples use the worldwide USD selector and are not quotes.

Limitations

01
OVHcloud Public Cloud exposes more OpenStack and network choices than a basic VPS; the team must understand the selected deployment and public-IP mode.
02
Discovery plans are described for development and sandbox use, so production suitability must be established with workload measurements.
03
Prices and included traffic vary by country, currency, location, commitment, and APAC terms; backups and additional resources are separate.

Evidence

Sources and review record

Primary documentation checked for the material claims on this page. Product behavior and prices can change after the checked date.

FAQ

Questions about host next.js on ovhcloud.

No fog. Just the practical details developers need before moving a production app.

Should I use OVHcloud VPS or Public Cloud for Next.js?

A VPS is a simpler fixed server product. Public Cloud provides hourly instances, OpenStack controls, private networking, reusable IP and broader cloud services. This guide covers Public Cloud only.

Should I choose a Basic Public IP or Floating IP?

Use a Basic Public IP for a simple instance-bound deployment. Use a Floating IP when a reusable address is important for replacement, failover, or controlled cutover.

Next step

Turn the resource into a deployment decision.

Plan an OVHcloud deployment