Rig Launch · Servers

Linux servers, ready in minutes.

Self-managed Linux servers on AWS. You get root and run what you like; Rig runs the machine, the network, the backups and the panel. This page covers everything a server comes with, and the rules behind it.

Sizes · USD

Four sizes, three shapes.

Every size has the same features. Billed by the hour, never more than the monthly price; or yearly with two months free.

SizeCPU and memoryDiskTraffic a monthBackupsPrice
Basic1 vCPU · 2 GB40 GB SSD2 TBWeekly, 1 save point…Choose Basic
Good2 vCPU · 4 GB80 GB SSD3 TBDaily, 3 save points…Choose Good
Epic4 vCPU · 8 GB160 GB SSD5 TBDaily, 5 save points…Choose Epic
Epic Plus8 vCPU · 16 GB320 GB SSD6 TBDaily, 5 save points…Join the waitlist
  • GeneralBalanced CPU and memory.
  • CPU-optimisedTwice the vCPUs, for builds, workers and compute.
  • Memory-optimisedTwice the memory, for databases and caches.
Ordering

What you choose, and what happens next

Four choices, then a few minutes

Pick the size and shape, the region, the operating system (an OS image, an app stack, or Rig's pick) and a name. Everything else has a sensible default, under Advanced:

  • Hostname, and how you connect over SSH
  • A private network and a firewall, new or one you already have
  • A shared or dedicated IPv4, and how long backups are kept
  • A startup script of up to 64 KB that runs once on first boot
rig cloud / launch / new serverlive

coffee-club · Good · General · London

  1. Payment receivedDone
  2. Server createdDone
  3. Firewall and networkDone
  4. Operating systemDone
  5. SSHDone
  6. BackupsDone
  7. Ready at 203.0.113.24coffee-club.rig.app
Next

Open the panel, copy the SSH command, or ask The Duke to deploy.

Your email and card are checked before anything is created, and pressing the button twice never makes two servers. If setup fails after you pay, Rig retries twice, then refunds you automatically.

SSH and console

Connect the way you like

One choice, change it any time

Password login is always off. Whatever you pick, the web console works, so nobody is ever locked out.

  • Keys pasted in, imported from a GitHub account, or saved on your account for every server
  • ed25519, ECDSA, or RSA of 3072 bits or more
  • Key changes reach the server in seconds; removing a key removes it everywhere
  • The root password is never emailed: a reset shows it once
OptionWhat it means
Through RigConnect from Rig on your Mac. No keys to manage, and port 22 stays closed to the internet.
With my SSH keyNormal SSH with your own key, from anywhere.
BothThe two together.
The SSH and console guide
Network

Addresses, domains and the firewall

Online with HTTPS from the first minute

Each server has a site address such as coffee-club.rig.app with HTTPS, a shared IPv4 and its own IPv6.

  • Custom domains, with HTTPS issued automatically and help with DNS
  • Firewall rules in and out, reusable across servers; removing the last SSH rule warns you first
  • Private networks between your servers
  • A load balancer on Epic, included in Epic Plus
AddressReverse DNS
Shared IPv4Rig's, fixed
Your IPv6You set it
Dedicated IPv4 (add-on)You set it, once the name points back at the IP

Port 25 is closed on new servers to stop spam. Mail over port 587 or an API works straight away, or ask in Networking to open 25.

Backups and resizing

Undo, restore, grow

Backups and save points

Backups run at a time you set and are kept 7, 14 or 30 days. Save points are snapshots you take before a risky change.

  • Back up now, any time
  • Restore in place: a save point is taken first, so a restore can be undone
  • Start a new server from any backup, or download it
  • Delete and rebuild protection, per server

Resizing

Basic to Good to Epic to Epic Plus, or a custom size. The server restarts, which takes about a minute, and a save point is taken first.

  • Change CPU and memory only, so you can size back down later
  • Or grow the disk too; a disk can grow but never shrink
  • Now or at a time you schedule
  • The price change is shown before you confirm
Monitoring

Know before your users do

Alerts with sensible defaults

Alerts go by email, in the app and to Slack. Change any threshold per server.

  • Uptime checks on the site address every minute from 3 locations: an alert after 2 failures in a row, and another when it recovers
  • Spend alerts: an email when this month's bill passes an amount you set
  • Maintenance notices at least 7 days ahead, except for security fixes
  • Rig Launch and each region on the public status page
AlertDefault
CPUOver 90% for 10 minutes
MemoryOver 90%
DiskOver 90%
DownFor 2 minutes
Uptime guarantee99.9% a month, credits applied automatically
Self-managed

Staff stay out. Unless you let them in.

Grant support access for the servers, level and time you choose: 1 hour, 24 hours or 7 days. A banner shows while it is on, revoking is one click, and you are emailed when it starts, when staff first use it and when it ends.

LevelWhat support can do
ViewSee status, metrics, logs and config. No shell.
OperateAlso reboot, power on and off, restore backups and change the firewall.
ShellAlso use the console and SSH as root, with short-lived credentials made for that session.

Without a grant, staff see only billing, the server's size, region, status and IPs, and host-level usage. For abuse or a legal order they can power a server off but never open it, and you are emailed the reason at once.

Teams

Who can do what

ActionOwnerOperatorMemberViewer
See servers and their statusYesYesYesYes
Power, reboot, console, SSH keys, firewall, backups, save pointsYesYesNoNo
Order, resize, add-ons, rebuild, delete, transferYesNoNoNo
Grant support accessYesNoNoNo

Team servers belong to the team and the owner pays. Each member adds their own SSH keys, and removing someone from the team removes their keys from its servers. Group servers into projects and tags.

If something goes wrong

What happens when

WhenWhat happens
The disk fills upThe server stays up and writes fail. You're warned at 80% and 95% and offered more disk or a bigger size.
You reach your trafficThe site is slowed, not stopped, and never charged extra unless you turned on auto top-up.
A payment failsServers keep running for 7 days, then are powered off with everything kept. At 30 days a final backup is kept for 14 days.
You delete a serverUndo it from the panel until the deletion runs. Its final backup is kept for 14 days.
You move regionIt takes about 10 minutes and the shared IP changes; you're warned to update DNS first.
The provider has an outageThe server is marked degraded on the status page and staff are alerted.
Developers

Script it, or let your agent do it

Everything the panel does, from code

A REST API with scoped tokens, rig launch commands in the Rig CLI, a Terraform provider, and Rig's MCP tools for AI agents.

  • CLI: create, list, ssh, power, resize and backup
  • Terraform: servers, firewalls, volumes and more
  • MCP writes wait for your approval in Rig, like every Rig MCP write
rig launch ssh coffee-club