We’re excited to announce Autoscale + Static deployments. This is our biggest release yet, and it makes Replit the fastest place to go from idea to production for your next app. Deployments scale reliably with pricing that is cost-effective and transparent.
Here’s how it works:
Autoscale Deployments: Servers will automatically scale from zero to any level of demand, making it inexpensive for most apps, and effortless for when you go viral.
Static Deployments: Perfect for your HTML sites. Lightning-fast, super reliable, and free for Hacker and Pro subscribers. With support for Static Site Generators like Hugo, Svelte, and Vue.js, you can get started even faster.
Reserved VM Deployments: Customize your CPU and RAM to fit your needs and get fixed pricing every single month.
With these new offerings you can choose exactly which deployment type is the right one for your app. Every deployment comes with:
Scalable power: Easily upgrade the CPU and RAM of your app servers
Analytics: Stay current on your app’s growth with detailed request statistics
Logging: Monitor all of your builds and app processes in one place
Trusted security: Backed by Google Cloud’s industry-leading cloud security
Autoscale and Static Deployments are accessible today for Pro and Hacker builders, so upgrade your account to try it out. And, as always, comment below to let us know what you think!
I feel a bit left out here.
How is this a good thing? I was really looking forward to static Deployments that were free (like Glitch). Most users on replit are on free plans, doesn’t this make them a little left out?
With Autoscale, the app can go to sleep to save CPU (and money), but it will restart very quickly if a new request comes in
It’s very interesting, does that mean that a Python app may stop and restart even if it is deployed ?
I thought that a deployed app would really be always on and never stop and start.
If I understand correctly, if there is a relatively long initialization at the start of the app, it may do it again after a stop caused by no usage ? I thought it would do it only once after the deployment (or any unexcepted crash of course)