Skip to content
Odinex Cloud

For DevOps engineers

Production infrastructure as code, at a fraction of hyperscaler prices

Private networks, NAT gateways, label-based firewalls and load balancers in Frankfurt, managed with Terraform, the odx CLI or the REST API. Plan a change, see its monthly cost, apply it.

Internet
Load balancerlb11 · role=web
private · 10.0.0.0/16
web-1role=web
web-2role=web
web-3role=web
db-1m2 + volume
NAT gatewayoutbound
Firewall applied to every server labelled role=web
A typical stack: no public IPs on the servers, one way in, one way out.

Infrastructure as code

Your whole stack in one plan

Three web servers on a private network behind a load balancer that finds them by label. Scale with count; the load balancer picks up new servers on its own.

  • Terraform and OpenTofuAn open-source (MIT) provider that covers every resource type.
  • ComposerDescribe a stack in one document or ask the AI assistant, review the plan and its monthly cost, then apply.
  • Labels everywhereSelect firewall and load balancer targets by label, and filter every list in the API and CLI.
main.tf
resource "odinex_network" "private" {
  name     = "private"
  ip_range = "10.0.0.0/16"
  location = "fra1"
}

resource "odinex_server" "web" {
  count       = 3
  name        = "web-${count.index + 1}"
  server_type = "s2"
  image       = "ubuntu-24.04"
  location    = "fra1"
  labels      = { role = "web" }
  network { network_id = odinex_network.private.id }
  public_net {
    ipv4_enabled = false
    ipv6_enabled = false
  }
}

resource "odinex_load_balancer" "web" {
  name               = "web"
  load_balancer_type = "lb11"
  location           = "fra1"
  network_id         = odinex_network.private.id
  service {
    protocol    = "http"
    listen_port = 80
  }
  target {
    type           = "label_selector"
    label_selector = "role=web"
  }
}

Networking

The network building blocks of a real cloud

Everything you need to separate public and private traffic, in the same location and the same API.

Security and operations

Built for teams that are on call

Access control, recovery tools and data residency, without an enterprise contract.

Move your next environment to Odinex

Same Terraform workflow, standard Linux images, and list prices up to 84% below AWS, Azure and Google Cloud.

DevOps questions

Clear answers about location, infrastructure and billing.

Is there a Terraform provider?
Yes. The odinex provider works with Terraform and OpenTofu and covers servers, volumes, networks, NAT gateways, Elastic and floating IPs, firewalls, load balancers, placement groups, snapshots, SSH keys and reverse DNS.
Can servers run without a public IP address?
Yes. Put them in a private network with a NAT gateway for outbound traffic, and reach them through a load balancer, an Elastic IP or a bastion host.
How do I give a CI pipeline access?
Create a project API token in the console. Choose read or read-write scope and an expiry date, store it as a CI secret, and use it with the CLI, Terraform or the API. Each token sees only its own project.
How do I keep a team’s costs under control?
Billing is prepaid with a monthly cap per resource, so nothing runs up an open-ended bill. Members get roles (owner, admin, billing or member), and Composer shows the monthly cost of a change before you apply it.