Fork and Self-hosting

Fork and self-hosting means copying someone else's program code so you can run it wherever you want, instead of on the company's own servers. Think of a restaurant that publishes its recipe. You can go to the restaurant (the company's server) and order the dish, or you can take the recipe and cook it yourself in your own kitchen (your own server or computer). Forking is copying the recipe wholesale and making it your own; self-hosting is actually running that copy somewhere you control.

This matters because of control. If the restaurant closes or changes its menu, you can still cook the dish as long as you have the recipe. In the same way, if the company that made a program shuts down its service or changes its pricing, someone who forked and self-hosted it can keep using the program on their own server exactly as before. It also matters because your data stays on your own machine instead of passing through someone else's server.

But self-hosting comes with a cost. Keeping a server running, maintaining it, and handling updates yourself means taking on work the original company used to do for you. That's why it's common to see both options offered side by side: the code is made public so anyone can fork it, while a polished, easy-to-manage hosted service is also offered for those who don't want the hassle.

In articles you'll see phrasing like, "They announced dedicated remote computers along with the freedom to fork and self-host, one after another." A common misunderstanding here is that self-hosting doesn't mean 'never using a cloud service at all.' In practice, it means you have a wide range of options: you can simply use the company's ready-made hosted service, or if you prefer, copy the code and run it yourself on your own server or even a five-dollar VPS.

Here's a hands-on process you can try:

1. Find the repository page for an open-source project you're interested in.
2. Check the license to see whether forking and self-hosting are allowed.
3. Fork the repository into your own account.
4. Download the code to your computer or server and follow the provided installation instructions to run it.
5. Compare your self-hosted version against the original service to see what differs.