Skip to main content
The deployment type is the technology Replit uses to publish your app. You choose it in the Publishing tool under Adjust settings, in the Deployment type dropdown. Autoscale is the default and recommended choice, and most builders never need to change it.

​
Compare deployment types

TypeBest forHow it runsHow it bills
AutoscaleWeb apps and APIs with variable trafficAdds servers when busy, scales to zero when idleYou pay while requests are being served
StaticLanding pages, portfolios, documentation sitesServes files from a cached cloud server, no backendYou pay only for the data your site serves
Reserved VMBots, background work, always-on APIsOne dedicated server that never sleepsFixed monthly cost
ScheduledPeriodic tasks like backups and notificationsRuns a command on a schedule, then stopsYou pay for the duration of each run

​
Autoscale

Autoscale Deployments run on servers that scale up and down with your app’s traffic. When your app is busy, Replit adds servers to handle the load. When it’s idle, the count drops to as low as zero, so you don’t pay for quiet time. Ideal for:
  • Web applications with variable traffic, such as ecommerce sites
  • APIs and services
Configuration lives in Adjust settings: machine power and the maximum number of servers.

​
Static

Static Deployments host your app’s files, such as HTML, CSS, and JavaScript, on a cloud server that uses caching to deliver content quickly and economically. There is no backend server. Ideal for:
  • Marketing landing pages
  • Portfolio websites
  • Product and API documentation sites
Static Deployments are not compatible with Replit Apps created using Agent. Agent builds full-stack apps that need a backend server, so use Autoscale or Reserved VM for those.
Configuration includes the public directory to serve and an optional build command. For response headers, URL rewrites, and redirects, see advanced Static configuration.

​
Reserved VM

Reserved VM Deployments run your app on a dedicated virtual machine that never sleeps. You get consistent performance and a predictable, fixed monthly cost. Ideal for:
  • Memory-intensive background tasks
  • Chat bots that must stay connected
  • Always-on API servers
Configuration includes machine power, build and run commands, port mappings, and whether the app runs as a web server or a background worker.

​
Scheduled

Scheduled Deployments run a command on a schedule in your app’s environment, then stop until the next run. Describe the schedule in plain language, such as “every weekday at 9am”, and Replit converts it into a schedule automatically. You get an alert if a run fails. Ideal for:
  • Status checks and health reports
  • Sending notifications
  • Starting backups
Configuration includes the schedule, a job timeout, and build and run commands. Scheduled Deployments don’t serve a web page, so they have no public URL.

​
Next steps