Where you stand and why self-hosted

▸MODULE 1 / ORIENTATION

What we are talking about

In "Automate Yourself" you automated your own workflows, handing tasks to an AI assistant that you used to do by hand. Until now that assistant ran whenever you started it, on your computer, with the program open. In this lesson you take the next step: an assistant that keeps running on its own even when your laptop is closed and you are somewhere else entirely. That is what "around the clock" means, often written as 24/7, meaning twenty-four hours a day, seven days a week.

For an assistant to do that, it needs a home that never switches off. That home is a server, a computer that runs continuously and is never shut down. The interesting question is who that computer belongs to. You can rent a ready-made service where another company handles everything. Or you take your own server and run the assistant yourself. Running it yourself is called self-hosted, meaning on a place you control rather than on someone else's infrastructure. This lesson explains what that means in practice, why it is worth it, and what you are taking on.

Your own server, as an everyday picture

Imagine you like to build things and you need a workshop. You have two options. The first: you rent a spot in a large, shared hall. The electricity, heating, and keys come from the operator, you walk in and get to work. Convenient, but it is not your hall. The operator has a master key, they can see what you build, and when they change the rules, those rules apply to you.

The second option: you set up your own workshop. You decide who has a key, only you can see what is inside, and nobody tells you how to organize your shelves. In return you are responsible for the electricity, the lock, and keeping things in order. That is self-hosted. Your own server is your own workshop, and the rented service is the spot in someone else's hall.

In practice, that own server is usually not a machine at your home but a rented virtual computer in a data center, often called a VPS, meaning a virtual private server. That may sound contradictory at first, but it is exactly the point: you are renting the walls and the electricity, but inside it is only you. It is your workshop in someone else's building, not a shared desk in someone else's business. You will learn how to set up the server itself in the next module. Here the focus is on the why.

Why you would run this yourself

Three reasons speak for it, and all three can be illustrated with the workshop.

The first is control. In your own workshop you decide what goes where and who is allowed in. For the assistant that means: you determine what it is allowed to do, which services it is connected to, and when you change it. Nobody switches off a feature overnight or adjusts the rules without your input.

The second is data sovereignty, meaning ownership over your own data. Everything your assistant processes, your notes, your client names, your workflows, stays on your server and does not drift unintentionally to an outside provider. In your own workshop nobody can look into your drawers. With a rented service everything runs over someone else's machines, and you have to trust that they handle it properly.

An honest caveat belongs here, and we take it seriously. This data sovereignty applies to what sits on your server. Which AI model your assistant uses for its responses, and where that model sends data for processing, is a separate question. If your assistant uses a model that runs at a provider abroad, the data leaves your server for processing despite self-hosting. This exact distinction, your own server versus the model in use, is something we examine honestly in the module on data privacy. It is the core question of whether your data sovereignty actually holds up in practice.

The third reason is cost. A small server of your own costs a fixed, predictable monthly amount, much like a small workshop rental, regardless of how much you work inside it. Many hosted assistant services charge by usage instead, and for an assistant running around the clock that adds up. I am deliberately not naming specific prices here because they change monthly and you will check them directly with the provider anyway. The principle holds: one fixed, planned expense rather than a running bill whose amount others control.

The honest trade-off: you are the operator now

Now for the part most tutorials leave out. In your own workshop there is no caretaker. When the lights go out, you go to the fuse box yourself. When a door is left open, it is your door. It is the same with your own server: you are no longer just the user, you are now the operator. If something does not work, you handle it. If a door is open, meaning an unsecured access point, it is your responsibility to close it.

This is not a threat, it is an honest heads-up so you know what you are getting into. The good news: this kind of operating is learnable, step by step, and that is exactly what this course is for. You do not need to be able to program. You just need to be willing to adopt a few reliable habits, the same way you would naturally lock up your own workshop at the end of the day.

What this course is and what it is not

There is one thing you should know from the start, so you are not paying for something available for free. The pure installation of the assistant, meaning setting up the open-source personal agent you pull onto your server, is available free of charge in many languages as video walkthroughs online, including in English. (Open-source, often called open source, means the software's blueprint is openly visible and free to use. A personal agent is simply a personal AI assistant that handles tasks for you.) Charging for that would not be honest.

What this course is for is the layer those free videos leave out: running it securely, framing it correctly from a privacy standpoint, and keeping it reliably running over months. In other words: not "how do I switch it on" but "how do I operate it without putting myself or other people's data at risk." That is the work that corresponds to the lock, the order, and the regular walk-through in your own workshop.

Check whether self-hosted is your path

Before we go deeper, answer a handful of questions honestly for yourself. Copy the text below into your AI tool, the same program you used in "Automate Yourself." It will ask you the questions one by one and tell you at the end whether the self-hosted path fits you.

I am considering running an AI assistant around the clock on my own
server, rather than renting a ready-made hosted service.
Ask me these questions one at a time, one after the other, and summarize
at the end whether the self-hosted path fits me:

1. Do I want to decide for myself what the assistant is allowed to do
   and which services it is connected to?
2. Is it important to me that my data stays on my own server and does
   not pass through a third-party provider?
3. Am I willing to adopt a few reliable habits to operate the server
   myself (the way you would lock up a workshop at the end of the day)?
4. Does it bother me that with my own server there is no outside
   caretaker, and I am responsible for any problems myself?
5. Do I want to understand what is happening under the hood, or do I
   just want a finished result without any insight?

If I answer the first three mostly with yes, question 4 is fine by me,
and for question 5 I want to understand: the self-hosted path fits.
If I mainly want convenience and prefer not to manage things myself:
tell me honestly that a hosted service would be the better choice.

If after these questions you can state in one sentence why self-hosted makes sense for you, or consciously does not, you have reached the goal of this lesson.

The honest assessment

Self-hosted is not the right path for everyone, and that needs to be said plainly. If you want a convenient, ready-made service where a company handles everything and you just type, this is not the right place. This course does not take the managing off your hands, it teaches you how to do it. Anyone who puts convenience above control is better served by a hosted assistant, and that is not a failing, it is a legitimate decision.

The price of the independent path is responsibility. You gain control, data sovereignty, and predictable costs, and in return you become the operator who is accountable for the security of their server. Precisely because that is true, we do not start with switching it on, we start with an honest look at the security situation. In the next lesson we frame exactly that: what it means to operate an assistant that is in principle reachable from the internet, and why one single principle, never choosing the open path into the network, decides more than almost anything else.