Quick Estimate
Answer the simple prompts below. We translate the technical bits (like compute units) into plain language so you can focus on your idea.
Try a preset:
Total
$0.00
Details
Deployment glossary
Plain-English explanations for the terms you’ll see on Replit deployment bills.
- Autoscale deployment
- A web app hosted on Replit that stays online and automatically adds power when more visitors show up.
- Scheduled deployment
- A task that runs on a schedule (like nightly or hourly). Handy for reminders, cleanup jobs, or reports.
- Reserved VM
- A dedicated virtual machine with fixed CPU and memory. Billed by active hours; choose a size that fits your workload.
- Static deployment
- A simple site made of HTML, CSS, and images with no server code. Replit currently lists no extra fees for static deployments.
- Compute units
- A way Replit measures how much work your code actually does. More requests or heavier processing equals more compute units.
- Requests
- Each time someone or something asks your app for data. More users equals more requests.
- Compute hours
- The amount of time a database or virtual machine spends doing work. One compute hour means it was actively running for an hour.
- GiB (Gibibyte)
- A measure of digital size, similar to a gigabyte. 1 GiB is enough for roughly 300 music tracks or 250 high-quality photos.
- Outbound data transfer
- The amount of data sent from your app to visitors. Video or large downloads increase this number.
- PostgreSQL storage
- The space used by your app’s database tables, indexes, and backups.
- App storage
- Replit’s object storage for files, images, and documents you want to keep online.
- Basic file operations
- Simple storage actions like checking a file exists, reading small chunks, or listing folder contents.
- Advanced file operations
- Heavier storage actions such as large uploads, downloads, or complex searches.