Skip to main content

Reserved IP

Introduction​

Normally, every time you launch or resume a VM it gets a fresh public IP from the pool. That's fine for most workloads, but it breaks anything that depends on the address staying put — DNS records, firewall allowlists, a hardcoded SSH config, a webhook target, and so on.

A Reserved IP is a public IP you reserve ahead of time and attach to a VM. Once a VM launches on it, that VM keeps the same public IP on every future pause → resume cycle — you never have to update DNS or your SSH config again.

Use a Reserved IP when you want to:

  • Point a domain or DNS record at a VM that you'll pause and resume regularly.
  • Keep a fixed entry in a firewall allowlist or a partner's IP allowlist.
  • Give a long-running inference endpoint or webhook target a stable address.

Availability​

  • Regions: Reserved IPs are only available in — IN1 and IN2. They are not available in EU1.
  • Instance type: Reserved IPs currently work with VMs only (GPU and CPU VMs). Container instances don't support them yet.
  • Ownership: a reservation belongs to the individual account that created it — it is not shared automatically across a team workspace.

Pricing​

A Reserved IP is a flat monthly fee, billed in 30-day cycles:

Monthly fee
Indian users₹475/mo
Everyone else$5/mo

Rules that apply to billing:

  • You pay the same fee whether the IP is idle or attached to a running VM. There's no discounted or free "idle" state — reserving it starts the billing, full stop.
  • The first 30-day period is charged immediately when you reserve the IP, deducted straight from your account balance.
  • Reserved IPs are paid from your real account balance only — grants and free credits cannot be used. If your balance can't cover one month's fee, reserving is refused and you're prompted to add balance first.
  • Payments are non-refundable once charged.
  • The reservation's rate is frozen at the time you reserve it — it won't change later even if pricing changes for new reservations.

Limits​

  • Quota: you can hold at most 2 reserved IPs per account, and this limit is global across all regions (not 2 per region).
  • Regional capacity: JarvisLabs always keeps a portion of each region's IP pool free for new instances. If a region's free pool would drop too low, new reservations in that region are temporarily paused until capacity frees up — reach out to support@jarvislabs.ai if you need one urgently.

Reserving an IP​

You manage reservations from the Reserved IPs page on the dashboard: jarvislabs.ai/dashboard/reserved-ips.

  1. Click Reserve IP.
  2. Review the monthly fee and billing terms shown in the dialog.
  3. Pick a region (IN1/India-01 or IN2/India-02). If only one region is available to you, it's locked in automatically.
  4. Click Reserve IP to confirm. The first month is billed to your balance immediately and the new IP appears on the page as Idle.

If you're at your 2-IP limit, or the region has no capacity right now, the dialog tells you so and the Reserve button is disabled.

Using a reserved IP on a VM​

Reserving an IP doesn't attach it to anything by itself — there's no separate "attach" button. You put a reserved IP to use from the VM launch or resume form:

  1. On the VM page, in an OVN-enabled region, find the Public IP section.
  2. Choose Reserved IP instead of the default Dynamic IP.
  3. Select one of your idle reserved IPs from the dropdown. If you don't have one in that region yet, click Reserve one to open the Reserve dialog without leaving the form.
  4. Launch (or resume) the VM as normal.

Rules that apply to attaching:

  • It takes effect on the next launch/resume, not instantly. Selecting a reserved IP doesn't change the address of an already-running VM.
  • Once a VM has launched on a reserved IP, it stays on it automatically — every later pause → resume brings the VM back on the same IP, with nothing to reselect.
  • Choosing "Dynamic IP" on a resume does not detach a reserved IP that's already in use. If a VM is currently on a reserved IP, it keeps that IP on resume regardless of what you pick in the form. The only way to move a VM off a reserved IP is to release the reservation from the Reserved IPs page (see below).
  • A reserved IP can only be used by one VM at a time. If you try to launch a second VM on an IP that's already attached elsewhere, the launch is rejected — pause or destroy the first VM (or pick a different IP) before retrying.
  • Only reserved IPs that are currently idle and in the same region as the VM show up as selectable options.

What happens when the VM is destroyed​

Destroying a VM that's using a reserved IP does not release the reservation. The reservation simply goes back to Idle — it's still yours, and you're still billed for it every month — ready to be attached to another VM whenever you like.

Releasing a reserved IP​

Release a reservation from its card on the Reserved IPs page. Unlike attaching, release always works immediately, even while a VM is using the IP:

  • Billing stops the moment you release it.
  • If the IP is idle, it returns to the pool immediately and your quota slot frees up right away.
  • If a VM is currently using the IP, the reservation still ends (and billing still stops) right away, but the address itself stays with that VM until it next pauses or is destroyed — at that point it returns to the pool.
  • You may not get the same address back if you reserve again later — releasing returns the IP to the shared pool for anyone.

FAQ​

Can I attach a reserved IP to a container instance? Not yet — Reserved IP currently supports VMs only.

Can I pick which specific IP address I get? No. Jarvislabs assigns one automatically from the region's free pool when you reserve.

Do I keep paying for a reserved IP I'm not using? Yes. The fee is the same whether the IP is idle or attached to a running VM.

What happens if I don't have enough account balance to reserve? The reservation is refused with a message asking you to add balance. Reserved IPs can only be paid from real account balance — grants/free credits don't count toward it.

If I select "Dynamic IP" when resuming a VM that already has a reserved IP, does that detach it? No. The VM keeps its reserved IP on resume regardless of that choice. To free the VM from a reserved IP, release the reservation itself from the Reserved IPs page.

Will releasing a reserved IP interrupt my running VM? No — if the VM is still running on that IP when you release it, the VM keeps running on that address uninterrupted. The reservation just won't renew, and the address returns to the pool the next time the VM pauses or is destroyed.

Is the monthly fee refundable if I release early? No, charges are non-refundable.

Is a reserved IP shared across my team workspace? No — a reservation belongs to the individual account that created it.