Skip to main content
Published on November 14, 2026 You build your VPS, networks, DNS zones and hosting by hand, one click at a time, and start over every time you need a copy of an environment? Since November 10, 2026, the OnetSolutions Terraform provider lets you describe your infrastructure in configuration files. terraform apply creates it, changes it or removes it. The same configuration works with OpenTofu.

What is a Terraform provider?

A provider connects Terraform to a platform. You write the state you want in HCL; Terraform compares it with what exists, shows you a plan, then applies the changes. Your configuration becomes the source of truth. Kept in Git, it can be reviewed, shared and replayed: a test environment identical to production is one command away. Terraform and OpenTofu both install the provider from their own registry, as onetsolutions-net/onetsolutions.

What you can manage as code

Version 0.2.0, released on November 11, 2026, covers compute, networking, domains and web hosting. Data sources help you choose before you declare anything: onetsolutions_instance_sizes, onetsolutions_images, onetsolutions_tlds, onetsolutions_domain_availability and onetsolutions_hosting_plans.

Reboot, reinstall and restore from your configuration

The provider also ships actions: reboot an instance, reset it, reinstall it from an image or restore one of its backups, straight from your configuration.
Actions need Terraform 1.14 or later; OpenTofu does not run them. Every resource and data source works with both Terraform and OpenTofu.

Get started with the OnetSolutions Terraform provider

You need an OnetSolutions account, an API key, and Terraform 1.5 or later, or OpenTofu 1.6 or later.

1. Create an API key

Create an API key in the console. It acts with your rights, in every organization and project you can reach. Keep it out of your configuration files by passing it in an environment variable:

2. Describe your infrastructure

An SSH key and a private network, in a main.tf file:

3. Apply

When your account has several organizations or projects, set organization_id and project_id on the provider, or on each resource.
Creating an instance, a web hosting or a domain places an order, billed like an order from the console. The plan tells you before anything is ordered or cancelled.

Bring what you built in the console under code

Everything you created in the console can be imported, with an import block or terraform import. Each resource page of the provider documentation gives its import ID:
Import your existing resources first, then run terraform plan: an empty plan confirms your configuration matches your infrastructure.

Go further

Not an OnetSolutions customer yet? It all starts at onetsolutions.net.