Introducing Replit Deployments 🌐

Welcome! Updates
1

Hey Replit users,

Today we’re excited to announce Replit Deployments, the fastest way to go from idea to production in any language. It’s a ground up rebuild of our application hosting infrastructure. Here’s a list of features we’re releasing today:

  • Your VM will rarely ever restart, keeping your app running and stable. You’re Always On by default. No need to run pingers or pay extra.
  • Say goodbye to the “Repl Waking” screen because your VM doesn’t go to sleep.
  • Dedicated VM resources for your app so you aren’t sharing machines with resource abusers.
  • Control when you release to users so you can fix your app without breaking production.
  • Link your custom domain in seconds, or pick a custom subdomain under the .replit.app domain.

Replit Deployments allows you to build separation between your development environment and production environment. This means you can work on your app without affecting live users. You can release any repl you’re working on into production by running a Deployment. You can customize the Build command, Run command, and set production-specific secrets values separate from development values.

For small projects like simple web servers and bots, Replit Deployments start as low as $0.20/day per Repl. However, if you wind up building the next viral generative AI app, you can go up to 4 dedicated CPU and 16 GiB RAM.

We know that you may have some questions about these changes, so we’ve prepared a list of FAQs:

Is the current hosting product (sharing repl.co URLs) being removed?

“Beta Hosting”, where you share your development environment’s repl.co URL, is now in maintenance mode. We will not be adding any new features to Beta Hosting, but applications will continue to run.

Instead, our time will be spent making Replit Deployments a best in class product. That means adding more features, offering new deployment types, and helping you grow from idea to full fledged business.

Is sharing Repls to the Replit community changing?

No. Community sharing will continue to work as it does today. This launch doesn’t impact that. In the future, we’d like to bring the same level of hosting quality to community sharing, but we don’t have those details ready yet.

Why isn’t there a free tier for Replit Deployments like there is for Replit Hosting?

We’re still working on how our free tier should be structured. We want to make sure:

  • Sharing to the community remains accessible and exciting. Getting a Repl on trending should be fun, not a financial scare.
  • You feel free to experiment with lots of small ideas before they take off and need higher levels of resources.

We’ll have more details to share here soon.

What’s happening to repl.co sites?

Nothing is happening to repl.co websites today. It’s still possible to share the repl.co URL backing your development environment. But we think you’ll have a better experience using the new workflow and explicitly releasing your apps.

Are pingers banned from accessing repls?

No. Pinger sites like UpTimeRobot can be a good way to monitor your app for unexpected crashes. In the past, users also used those sites to keep repls “warm” for smooth wake-ups. That’s no longer necessary as the app is always warm and running.

We’re excited to launch Replit Deployments, and we look forward to hearing your feedback. Feel free to leave any comments below. You can also join our pro dev discord server if you prefer to leave feedback there. You can learn more about Replit Deployments in our announcement blog post as well.

Thanks,

The Replit Team

30 Likes
2

Awesome, Ty! I am glad that you guys clarified that people would still have free domains. :rofl:

EDIT: Wow first comment!

15 Likes
3

Seems like some really good changes! So many people have come to replit needing huge AI tasks but we have to tell them to go somewhere else because all repls fall asleep, now that is fixed!

11 Likes
4

this is a good upd :+1: was worried they would be dooming us to an eternity of only cover page iframes

10 Likes
5

That link uses http://, doesn’t replit redirect repl.co domains to https://?

5 Likes
6

so repl.co will keep working the same…?

4 Likes
7

I participated in the beta, and I would love to say this is amazing!

11 Likes
8

Wait, it worked for you? I never really got it to work more than once, even a simple expressjs repl failed to deploy.

6 Likes
9

It worked really well for me in the beta!

6 Likes
10

as a fellow participant, it looks good

EXCEPT I CAN’T DEPLOY MY APP BECAUSE THE FREAKING LAYERS WON’T PUSH OR SOMETHING

4 Likes
11

Maybe the part of the deployments process that runs in the user’s repl only really works on paid clusters. You used the deployments beta on your alt, which has a month of free paid plan, right? (I never got it to work on my account, and that’s the only difference between me and @bigminiboss and people like you and @bddy that I can think of)

6 Likes
12

No, I used the beta on my main account.

4 Likes
13

I do have paid clusters as a hacker but I got an error lol it said that it was fatal: failed to push layers or something can’t figure it out ;-; if someone could help that would be great

5 Likes
14

Thanks for participating in the beta! We have been bug-fixing like crazy for the last couple weeks. If there is any repl you’re unable to deploy, let me know and I’ll look into it for you!

9 Likes
15

yeah it’s called replit-bot I’ll invite you

4 Likes
16

ok you’re invited to the repl :pray: please help

4 Likes
17

Can you share the repl ID?

4 Likes
18

here you go: a4a79258-5169-4889-8ae2-63f04e0f7f0c thx for helping

4 Likes
19

@replitconner Just confirming, repl.co still works like before (and will for the forseeable future), right? (The quotes are from a PM that some of us are in)

7 Likes
20

oh it’s not free anymore so I might not deploy but I’d like to figure out what’s wrong so I’ll deploy it for 20 cycles for a day

6 Likes