Skip to content
Odinex Cloud
DELog inSign up

Infrastructure as a document

Composer: draw your infrastructure, see the cost, apply it

Composer turns a complete setup into one document called a stack: networks, a NAT gateway, servers, volumes, firewalls, load balancers and IP addresses. You build it in a visual editor, as JSON or YAML, or by asking the AI assistant. Odinex shows a plan of what will be created, changed or deleted and what it costs per month, then applies it in the right order.

Get started Read the docs

At a glance

Formats
Visual editor, JSON, YAML
Resources per stack
Up to 100
Servers per entry
Up to 20 with count
Plan output
Create, update, delete, keep + monthly cost
Interfaces
Console, API, odx CLI
Price
No extra charge

Key features

  • Visual editor

    Place resources on a canvas and connect them. Your existing resources in a location can be shown as a graph to start from.

  • AI assistant

    Describe what you need in plain words and the assistant drafts the stack for you to review.

  • Cost before you commit

    The plan lists every change with its monthly price and the cost of the whole stack before and after.

  • Applied in order

    Networks before servers, servers before load balancers: everything is created through the normal API, in one step.

  • Change it later

    Edit the document, plan again and apply. Firewall rules, load balancer targets, volume sizes and server counts change in place.

  • Ordinary resources

    What a stack creates shows up in the console, API and CLI like any other resource. No lock-in to the stack.

What it is used for

  • A complete web stack

    A private network with a NAT gateway, three web servers without public addresses, a firewall and a load balancer, all in one document.

  • Repeatable environments

    Keep staging and production as two stacks from the same document and know what each costs per month.

  • Learning by example

    Let the assistant draft a setup, read the plan, and adjust it before anything is created.

Try it

odx CLI
odx stack create --name shop --location fra1 --file stack.yaml
odx stack plan shop     # changes and monthly cost
odx stack apply shop --wait

Documentation

Works well with

Composer: questions and answers

Clear answers about location, infrastructure and billing.

What is a stack in Odinex Composer?
A stack is a document that describes the resources of one setup in one location. Odinex compares it with what already runs, shows a plan with costs, and applies the changes in dependency order.
Does Composer cost extra?
No. You pay only for the resources the stack creates, at their normal prices.
Is Composer a replacement for Terraform?
It covers the same idea for a single location without any local tooling. If you already use Terraform or OpenTofu, the Odinex provider works too; both use the same API.
What happens when I delete a stack?
By default the stack and all its resources are deleted. You can choose to keep the resources, which then remain as ordinary resources.

Build it in Frankfurt today

Create an account, top up from €5 and pay by the hour, never more than the monthly price.

Deploy your first server See all plans