Basic
A first project, a bot or a small site.
- 1 vCPU · 2 GB · 40 GB disk
- 2 TB traffic · weekly backups · 1 save point
- HTTPS site address, firewall, IPv6
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.
A first project, a bot or a small site.
Most apps: an API, a database and a worker.
Heavier apps and busy sites.
Production, with a dedicated IP and a load balancer.
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.
Pick any you want and the plan buttons carry them to checkout. Add or remove them later from the panel.
Say what the server needs. Rig picks the plan and type that fit at the lowest price.
Deploy, run, store and control, on one bill, next to the Rig you already use on your Mac.
Get code from your Mac to the internet.
Keep it up, and know when it isn't.
Somewhere for everything your app keeps.
From Rig, a terminal, code or your AI agent.
Your servers, your rules, your bill.
What three common jobs cost at today's prices.
…Good server for two days
Start a server, ask The Duke to deploy the branch, and send the client its site address. Delete it once they've signed off.
…Epic server for a week
A copy of production to run a migration, a load test or a new dependency against, without touching the real thing.
…Good server all month
Keep the server running. By the hour it never costs more than the monthly price, so a full month is the monthly price.
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.
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.
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.
Keep it for production, or delete it when the job is done and the billing stops. A final backup is kept for 14 days.
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.
npm ciDonenpm run buildDonesystemctl restart coffee-clubWaiting for yousystemctl restart coffee-clubTarget coffee-club. Why: load the new build. Then: health check from rig.yaml.
Automatic backups on every plan, and save points to roll back to before a risky change.
A default firewall for web servers. Add your own rules, or reuse one firewall across servers.
Every server gets one, like coffee-club.rig.app. Add your own domains; HTTPS is issued for you.
Your own IPv6, and private networks so servers and databases talk off the internet.
CPU, memory, disk and down alerts by email, in the app and to Slack. Site checks every minute.
A web console and rescue mode, for when SSH is broken. Password login is always off.
Rig staff never look inside a server unless you grant access, for a time you choose.
Everything the panel does, from scripts, rig launch in the Rig CLI, Terraform or your AI agent.
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.
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.
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.
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.
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.
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.
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%.
Rig retries twice. If it still fails, you're refunded automatically and emailed, and we look into it.
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.