Cloud servers, storage and Postgres, billed by the second.
Aldridge runs your app on plain Linux servers in Ashburn, Columbus, Dallas and Hillsboro. Egress is included, Postgres rewinds to any second, and an engineer answers the phone.
No card needed. Credit lasts 60 days.
console.aldridge.run/servers
Terraform
GitHub
Docker
Kubernetes
Pulumi
GitLab
Ubuntu
NGINX
Three products, one bill, and nothing surprising on it.
Servers, object storage and Postgres share one private network, one console and one invoice. Every line on that invoice is per second, per gigabyte or per month, and all of it is on the pricing page.
Servers that boot in 20 seconds and stop billing the second they stop.
Shared or dedicated vCPU, NVMe disks and NVIDIA L4 GPUs in Dallas. Resize without a rebuild, snapshot on a schedule, and stop anything you are not using.
From $4 a month for 1 vCPU and 1 GB
NVIDIA L4 GPUs at $0.80 an hour
Private networks between regions, free
console.aldridge.run/servers/worker-gpu-1
console.aldridge.run/storage/media-prod
Object storage that speaks S3 and never charges for egress.
Use the AWS SDK, rclone or anything else that talks S3. Keep 18 TB or 18 GB, pay $5 per terabyte a month, and read it back as often as you like.
$5 per TB a month, no request fees
Versioning and replication to a second region
Works with every S3 client you already run
Postgres you can rewind to any second in the last 14 days.
Managed Postgres 17 with a standby in a second region, automatic failover and point-in-time restore that creates a new cluster, so the broken one is still there to compare.
Failover drills every Thursday, results in the console
Restore to a second, not to last night
Stock Postgres, so pg_dump always works
console.aldridge.run/postgres/app-db
Four US regions, each on its own power and network.
Pick one region per app, or run in two and let Aldridge fail over. Latency below is the median from a server in New York City, measured this morning.
Region
Code
Latency from NYC
Ashburn, Virginia
iad-1
6 ms
Columbus, Ohio
cmh-1
14 ms
Dallas, Texas
dfw-1
38 ms
Hillsboro, Oregon
hio-1
71 ms
All four regions ran at 99.99% or better over the last 12 months. GPU servers are in Dallas only for now.
Moving off AWS takes a week, and most of it is waiting on DNS.
The importer reads what you run today, shows you the same setup on Aldridge with its monthly price, and copies your data while the old stack keeps serving.
Point the importer at your AWS account
Give it read-only keys. It lists your EC2 servers, RDS databases and S3 buckets and maps each one to an Aldridge equivalent.
ald import aws --region us-east-1
Check the plan and the new bill
Nothing moves until you approve. The plan shows every resource it will create and the monthly cost next to what AWS charged you last month.
ald plan --compare
Deploy, then switch DNS when you are ready
Servers start, data copies in the background and the old stack keeps serving. Switch DNS when the health checks pass, not before.
ald deploy --all
Terminal, ~/fieldnote
Plugs into the rest of your stack.
Deploy from GitHub or Terraform, watch it in Grafana or Datadog, and hear about it in Slack. Each integration takes minutes and lives in its own page with setup notes.
Pay a flat plan fee, then per second for what runs.
Every plan gets the same servers at the same list prices. What changes is how much egress is included, how far back Postgres can rewind and how fast a person answers.
What changed for teams that moved.
Our AWS bill was $11,400 in May. The same stack on Aldridge cost $4,120 in July, and most of the gap was egress we had stopped noticing.
Priya Raman
Head of Platform, Tallgrass Health, Kansas City
We restored a dropped table to 14:02:37 on a Friday afternoon. It took four minutes and nobody had to open a runbook.
Marcus Ellery
Staff Engineer, Northloop, Minneapolis
I called the support line at 2:40am during a GPU driver problem and was talking to the engineer who later shipped the fix.
Dana Whitfield
CTO, Quill Robotics, Pittsburgh
Shipped in the last few weeks.
We post every change that touches your servers or your bill, with the date it went live.
v2026.38
GPU servers in Dallas are generally available
NVIDIA L4 servers in dfw-1 are out of beta, at $0.80 an hour billed per second.
v2026.37
Budget alerts can now stop servers
A budget alert can pause the servers you tag, not just send an email.
v2026.35
Point-in-time restore goes to 35 days on Scale
Scale plans can now restore Postgres to any second in the last 35 days.
Before you move anything.
Something else on your mind? Write to hello@aldridge.run and an engineer replies, usually the same day.
Start with $100 in credit and move one service first.
No card for the first 60 days. Bring a Dockerfile, a database dump or just a question, and a real engineer takes it from there.