Capacity decisions.
Already made.

Plan server capacity. Watch for matches. Keep infrastructure changes within your team's limits.

For Hetzner Cloud and the Hetzner server auction.

Early access: requests and matching work today. No real server orders are placed.

One request. Clear boundaries.

Watching for capacity

+1 worker server

Minimum
8 vCPU · 16 GB RAM · x86
Locations
FSN1 or NBG1
Quantity
1 server

Your approval

Monthly cap
€20.00, net
Valid for
72 hours
Billed to
Your Hetzner account

The brief in motion

  1. Requirements saved
  2. Limits approved
  3. Watching for a match
Illustrative request with example values. Early access stops at matching; no real order is placed.

Capacity moves.
Approval takes time.

Popular server types disappear. Auction machines are one of a kind. Checking another console becomes someone's other job.

By the time a purchase is approved, the capacity may be gone. Capture the decision in advance: what you need, what you will pay and how long the approval holds.

Set the boundaries first

From intent
to a watched request.

Make the decision while you have time. Keep its limits attached when availability changes.

  1. Connect your account

    Add a Hetzner Cloud project token. Provira verifies its access and stores it encrypted. Read-only access is enough for inventory.

  2. Define the brief

    Choose server specs, acceptable locations, quantity, monthly and setup price caps, and an approval window.

  3. Approve the limits

    A second person approves the request. Or choose to review each matching offer before anything proceeds.

  4. Watch for a match

    Provira checks Cloud types and the auction feed, then rechecks matching offers against your requirements and account pricing.

Matching is available in early access. Real server ordering is planned.

For the infrastructure
you run today.

Capacity planning shares a workspace with your existing Hetzner Cloud projects.

Your estate,
in one view.

See servers, volumes, networks, firewalls, load balancers and IP addresses, grouped by server with monthly costs and a map per location.

Keep the context around a capacity decision close to the infrastructure it will support.

Every change has context.

Inventory
Resources, locations and monthly costs
Activity
Server changes from the last 90 days
Resizes
Type changes with explicit approval
Guardrails
Order value, daily limits and quantity caps

Capability summary, not a live account snapshot.

  • Requests and approvals

    Save requirements, price caps and a time window. Give each request a clear approval record.

  • Market watch

    Inspect Cloud types by location and server auction listings, each labelled with its source.

  • Controlled resizes

    Plan a Cloud server type change with approval. Real resizes require write access, adoption and every execution gate enabled; otherwise they stay dry runs.

  • Server activity

    See what changed, including actions outside Provira. Investigate with the server's activity history.

  • Email notifications

    Follow approvals, offers, resize steps and external changes. Each person chooses their optional emails.

  • Organizations and roles

    Keep teams isolated with viewer, requester, approver and admin roles. Work across more than one organization.

Your account.
Your boundaries.

Control stays with your team. Credentials, permissions and the record of each decision have explicit boundaries.

Create your organization
  • Your account, your bill

    Your infrastructure stays in your Hetzner account. Provira does not resell capacity. Future orders will be billed by Hetzner directly.

  • Credentials sealed per team

    API tokens are envelope-encrypted with a per-organization key, never logged, and decrypted only by the executing worker. Only the last four characters are shown again.

  • Observe before acting

    Existing resources are observed by default. Management requires adoption; every execution rechecks approval, limits and platform caps.

  • A record you can inspect

    Decisions enter an append-only, hash-chained audit log per organization. Row-level security enforces organization isolation in the database.

Planned, not available yet

These are future capabilities or integrations. They are not available as complete workflows today, and plans can change.

  • Real server orders

    Buy matching Hetzner Cloud capacity within an approved request's guardrails.

    Planned
  • Dedicated server purchases

    Connect Hetzner Robot accounts and purchase dedicated or server auction machines.

    Planned
  • Node pools and scaling

    Manage groups of interchangeable servers with minimum, maximum and desired sizes.

    Planned
  • Cluster-aware resizes

    Build on the implemented Kubernetes agent foundations to coordinate node draining with server resizes.

    Planned integration
  • Automation and channels

    API keys for scripts and CI; notifications by webhook, Slack and Telegram.

    Planned
  • More providers

    Extend beyond Hetzner, including OVH, with provider preferences and fallbacks.

    Planned

Make the decision.
Keep the limits.

Sign up, create your organization and connect a Hetzner Cloud project.

Sign up