Disclaimer: I work at Replit.

You can read all about our hosting changes here: https://blog.replit.com/hosting-changes.

TL;DR

- deprecating always on in favor of new deployments product

- migrate workspace URL to replit.dev from repl.co

- replit.dev is the new development URL. only available when someone is in the editor.

- deployments are the only way to host things on replit

From the blog:

> We remain committed to providing a powerful free development experience to anyone who wants to code. This post is only about the hosting experience, which we are migrating to our new Deployments product.

> deployments are the only way to host things on replit

Which is only paid, correct?

Correct. Deployments are paid. But we still have a free (development) tier.

Disclaimer: I work at Replit.

We recently added autoscale (scale-to-zero) & static deployments to our plans. It should be pretty easy for you to host simple sites if you're a sub. Hacker starts at $7/mo. Can read more at replit.com/site/deployments.

Alternatively, you can also just add a card and pay for autoscale overages directly.

The problem isn’t that you’re charging too much, or that there’s anything wrong with Deployments per se. The problem is the rate of change. If I have to keep up with a product that’s changing this often, I might as well self-host.

It might not be clear from this post, but nothing is changing (w/ deployments/always on/repl.co hosting) until January 1st, 2024.

Right, I did see that. I get to pick any evening I want during the next ten weeks to do my futzing with the thing I was hoping to pay to leave alone in perpetuity.

> I might as well self-host.

Then do that, nobody is stopping you.

My point is not “wah wah I have to self-host.” I maintain a CMS backend for a living. I know how to host a website. I’m just saying that this transition has been made particularly annoying for the hobbyists being left behind, because it’s costing not only money but also time. There’s no “just let me pay for the existing service” option. It’s like an acqui-hire where they shut the service down instead of just keeping it running and taking people’s money.

I wrote a Replit tutorial on sending Ethererum from wallet to wallet in Python. It takes only 19 lines of code and is super easy to set up!

How do you test it? I'd like to test without depending on some remote service, which could be unreliable.

You can create your own local eth network (i.e: with https://www.trufflesuite.com/ganache)

I link to the test transaction at the bottom of the post!