Replit’s publishing costs are designed to scale with your app’s needs. Choose from usage-based billing that charges only when your app serves requests, or predictable flat-rate options for consistent workloads.

​
How billing works

All publishing costs are deducted from your monthly credits. You only pay usage-based fees after your monthly credits are fully used.
Credits apply automatically to all publishing costs. Unused credits don’t roll over to the next month. Learn more about usage-based billing.
For a hands-on understanding of publishing costs, explore our interactive pricing calculator.
Interactive publishing costs calculator showing cost breakdown by deployment type

​
Deployment types

Choose the deployment type that best fits your app’s traffic patterns and resource needs.
Perfect for apps with variable traffic. Pay only when your app serves requests—nothing when idle.Best for: Web apps, APIs, and services with unpredictable traffic patternsLearn more about Autoscale Deployments
Predictable monthly costs with dedicated resourcesGuaranteed compute resources that run continuously. Choose shared or dedicated VMs based on your performance needs.Best for: Production apps with steady traffic or guaranteed resource requirementsLearn more about Reserved VM Deployments
Cost-effective for background tasks and automationRun code on a schedule without maintaining persistent infrastructure.Best for: Background jobs, data processing, and automated tasksLearn more about Scheduled Deployments
Minimal costs for static content with global distributionPublish static sites with CDN distribution and pay only for data transfer.Best for: Documentation sites, portfolios, and single-page applicationsLearn more about Static Deployments

​
Understanding request-based billing

With Autoscale Deployments, you only pay when your app is actively working. When no one visits your app, you pay nothing.
Autoscale Deployments use request-based billing—you’re charged only when your app serves traffic. Here’s how it works:
  1. App starts up when the first request arrives (if idle)
  2. Processes the request using compute resources
  3. Goes idle after 15 minutes of inactivity
Billing time: Often just 1-2 seconds per request, even for complex apps.

​
Request-based Billing Timeline

When no one visits your app, you pay nothing. When your app is busy, you pay for the compute resources used. Here’s a timeline of what happens when someone visits your app:

Request-based Billing Timeline

Instance
Running
Requests
Billable
StartedStopped
First, the server starts up. Then, it processes the requests. Finally, it goes idle. You only pay for CPU and memory during request processing.
When multiple requests arrive simultaneously (like the stacked blue bars), they share the same compute resources.Your billing time extends to cover all concurrent requests, but you don’t pay separately for each—just for the total time the server is working.
The gaps between green bars represent cost savings during idle time. At the end of the session, the server shuts down.

​
Compute units explained

Compute units measure the computational work your app performs:
  • CPU time: Processing power used (1 CPU second = 18 compute units)
  • Memory time: RAM consumed (1 GB-second = 2 compute units)
  • Duration: How long your app works on each request

​
Pricing breakdown

Pay only when your app serves requests. Automatically scales based on demand.
ComponentPrice
Base fee (per month)
Compute units (per million units)
Requests (per million requests)
Execute background tasks and scheduled jobs.
ComponentPrice
Base fee (per month)
Compute units (per million units)
Scheduler
Dedicated compute resources with predictable monthly costs.

​
Shared VMs

ConfigurationPrice (per month)
0.25 vCPU / 1GB RAM
0.5 vCPU / 2GB RAM

​
Dedicated VMs

ConfigurationPrice (per month)
1 vCPU / 4GB RAM
2 vCPU / 8GB RAM
4 vCPU / 16GB RAM
Host static sites with global CDN distribution.
ComponentPrice
HostingFree
Data transfer (per GB)

​
Cost examples by app type

These examples show realistic costs for different types of applications.
Traffic: 50 visitors/day, 3 page views each = 4,500 requests/month
ComponentUsageCost
Base feeMonthly
Compute units13,500 units~$0.04
Requests4,500~$0.01
Total~$1.05
Traffic: 500 visitors/day, 5 page views each = 75,000 requests/month
ComponentUsageCost
Base feeMonthly
Compute units600,000 units~$1.92
Requests75,000~$0.15
Total~$3.07
Traffic: 10,000 API calls/day = 300,000 requests/month
ComponentUsageCost
Base feeMonthly
Compute units3.96M units~$12.67
Requests300,000~$0.60
Total~$14.27
Usage: Daily data processing with Scheduled Deployments
ComponentUsageCost
Scheduled deploymentBase fee
Compute units50,000 units~$0.16
Total~$1.16

​
Monitor and control costs

Set spending controls

Configure spending alerts and budgets to prevent unexpected charges.

Monitor usage

Track real-time consumption and costs in your Usage dashboard.

Monitor published apps

View logs, track performance, and monitor published app status.