Rig Launch · New

Servers for staging and deploys. The Duke runs them.

For when it works on your Mac and someone else needs to see it. Linux servers by the hour, to show a client, test a change or go live, with The Duke, Rig's AI agent, deploying one approved command at a time.

Balanced CPU and memory.

Basic

A first project, a bot or a small site.

LoadingReading today's prices
Choose Basic
  • 1 vCPU · 2 GB · 40 GB disk
  • 2 TB traffic · weekly backups · 1 save point
  • HTTPS site address, firewall, IPv6

Epic

Heavier apps and busy sites.

LoadingReading today's prices
Choose Epic
  • 4 vCPU · 8 GB · 160 GB disk
  • 5 TB traffic · daily backups · 5 save points
  • HTTPS site address, firewall, IPv6

Epic Plus

Waitlist

Production, with a dedicated IP and a load balancer.

LoadingReading today's prices
Join the waitlist
  • 8 vCPU · 16 GB · 320 GB disk
  • 6 TB traffic · daily backups · 5 save points
  • Dedicated IPv4 and Load balancer included

Leave your email and the options you want. Nothing is charged.

Prices in US dollars. By the hour, a server never costs more than its monthly price, and the hours are billed on your one bill date. Epic Plus is billed monthly. Add-ons are monthly. Prices are locked for 12 months from your order.

Add-onsDedicated IPv4, more disk, save points, longer backups, load balancer

Pick any you want and the plan buttons carry them to checkout. Add or remove them later from the panel.

Build your ownSet the vCPUs, memory and disk; Rig picks the cheapest fit, or a custom build

Say what the server needs. Rig picks the plan and type that fit at the lowest price.

Your serverGood · General2 vCPU · 4 GB memory · 80 GB diskPriced at checkoutChoose this server
Everything in Launch

More than a server. All in one panel.

Deploy, run, store and control, on one bill, next to the Rig you already use on your Mac.

Deploy

Get code from your Mac to the internet.

Run

Keep it up, and know when it isn't.

Data

Somewhere for everything your app keeps.

Work your way

From Rig, a terminal, code or your AI agent.

Stay in control

Your servers, your rules, your bill.

What it's for

Servers that last as long as you need them.

What three common jobs cost at today's prices.

…Good server for two days

Show a client a branch

Start a server, ask The Duke to deploy the branch, and send the client its site address. Delete it once they've signed off.

  • A site address with HTTPS from the start
  • Your own domain, if the client wants one

…Epic server for a week

Try a change before it ships

A copy of production to run a migration, a load test or a new dependency against, without touching the real thing.

  • A save point before every risky step
  • Or start it from last night's backup

…Good server all month

Run it in production

Keep the server running. By the hour it never costs more than the monthly price, so a full month is the monthly price.

  • Daily backups and uptime checks every minute
  • 99.9% uptime guarantee, with automatic credits
How it works

From your Mac to a live site.

  1. Order a server

    Pick a size, a region and an OS, or let Rig pick. You watch it build: payment, server, firewall, OS, SSH, backups, ready. It takes a few minutes.

  2. Connect

    Through Rig on your Mac with no keys and port 22 closed, with your own SSH key, or both. Keys can come straight from GitHub.

  3. Ask The Duke to deploy

    Say what you want in plain English. It reads the server, shows the plan with the expected downtime and how to roll back, and runs each command after you approve it. Then it checks the site is healthy.

  4. Keep it or delete it

    Keep it for production, or delete it when the job is done and the billing stops. A final backup is kept for 14 days.

rig cloud / launch / coffee-club / the dukelive

Deploy main to coffee-club

coffee-club is running; the last deploy was a41f9c2, two days ago. Plan: 3 steps, about 10 seconds of downtime. If the health check fails, I stop and you choose whether to roll back to a41f9c2.

  1. npm ciDone
  2. npm run buildDone
  3. systemctl restart coffee-clubWaiting for you
Step 3 of 3 · needs your approvalsystemctl restart coffee-club

Target coffee-club. Why: load the new build. Then: health check from rig.yaml.

Everything The Duke does
On every server

Nothing to bolt on before you start.

  • Backups and save points

    Automatic backups on every plan, and save points to roll back to before a risky change.

  • A firewall from the start

    A default firewall for web servers. Add your own rules, or reuse one firewall across servers.

  • HTTPS site address

    Every server gets one, like coffee-club.rig.app. Add your own domains; HTTPS is issued for you.

  • IPv6 and private networks

    Your own IPv6, and private networks so servers and databases talk off the internet.

  • Alerts and uptime checks

    CPU, memory, disk and down alerts by email, in the app and to Slack. Site checks every minute.

  • A console that always works

    A web console and rescue mode, for when SSH is broken. Password login is always off.

  • Support access you control

    Rig staff never look inside a server unless you grant access, for a time you choose.

  • API, CLI, Terraform and MCP

    Everything the panel does, from scripts, rig launch in the Rig CLI, Terraform or your AI agent.

Fair questions

Questions

How does billing by the hour work?

A server is billed for the hours it exists, from when it's ready until you delete it, and never more than its monthly price in a month. The hours are added up on your one bill date. Prefer a fixed price? Pay yearly and get two months free.

Is there a free starting credit?

Yes. New Launch accounts get credit to try a server, with a card on file. It must be used within 60 days, and we email you a week before it expires if some is left.

What does self-managed mean?

You run what is on your server: the OS packages, your app and its data. Rig runs the platform under it: the machine, the network, backups, the firewall and the panel. Rig staff never look inside your server unless you give them support access.

Can The Duke change my server on its own?

No. It reads status and logs without asking, but every command that changes a server waits for your approval, one at a time. Production also needs you to type the server's name.

What can I install on it?

Pick an OS image, an app stack, or let Rig pick. You get root, so you can install anything the acceptable use policy allows. A startup script of up to 64 KB can run on first boot.

Can I send email from a server?

Mail services that use port 587 or an API work straight away. Port 25 is closed on new servers to stop spam; ask in the server's Networking tab and we open it after a check.

What happens if I go over my traffic?

The site is slowed, not stopped, and you aren't charged extra unless you've turned on auto top-up. You're emailed at 90%.

What if setting up my server fails after I've paid?

Rig retries twice. If it still fails, you're refunded automatically and emailed, and we look into it.

What happens if a payment fails?

Your servers keep running for a week while we remind you. After 7 days unpaid they are powered off, with the disk, backups and IPs kept. After 30 days we take a final backup, keep it for 14 days, and delete them.