Self-Hosting or SaaS? How We Choose for Your Small Business

If you run a hair salon, a clinic, or a small office, you probably aren't looking for more software. You're looking to stop copying appointments by hand, answering the same questions over and over, chasing down documents, or ending the day with administrative tasks you couldn't get to.

That's why, when we design a solution, we start with your work. What you need to get done, what you repeat every week, and what we could simplify without taking away your control. Then we choose the tools and decide where it makes sense to host them.

Our preference is clear: all else being equal, we lean toward managed self-hosting. It gives us more room to adapt everything to your business, connect its applications, and keep it working if you change hosting or maintenance providers. But if a SaaS solves a specific need better, we use it. The priority is that you have less IT work, not that you learn a new technology.

First, what you need to solve in your business

A physical therapist working alone and an aesthetics center with five people may both need a calendar, but not necessarily the same setup. Hours, service duration, available resources, and the tasks each person can manage all vary. Those differences matter more than the name of the software.

We start by identifying where you're losing time. Maybe you get requests over WhatsApp and then transfer them into another application. Maybe you have to manually remember tomorrow's appointments. Or maybe you need to check which documents are missing before seeing a client.

We also ask what you want to keep deciding yourself. Automating doesn't mean the system should resolve every situation on its own. It can handle routine tasks and flag the exceptions for you, with the information you need to decide without hunting across several screens.

From that review we define the outcome: what work disappears, what steps get simpler, and how you'll use the solution. A business with one or two people can benefit enormously from that kind of tailoring, precisely because there's no one dedicated to coordinating all the tools.

When a SaaS application can be enough

A SaaS is an application you use as a service: the provider hosts it and keeps it running. You pay for access and use the features included in the plan. It can be a good option when you have a specific need that product solves well.

If all you need is a simple calendar and one application covers your services, your hours, and how bookings work, there's no reason for us to build something bigger. The same applies when you're already working comfortably with a specialized program: before replacing it, we assess what it offers and whether we can build on it.

The question is whether it covers your whole workflow or just part of it. A calendar can organize appointments, but you may also need a request to get logged, an invoice to reach your accountant, and certain alerts to go out without manual work. When several connected needs show up, it makes sense to design the whole thing rather than just stack subscriptions.

The client doesn't have to set any of that up on their own if we choose SaaS either. Our job is still to leave the solution tailored and connected. Choosing where to host it doesn't change the goal: that you can use it without becoming an IT specialist.

Photo by panumas nikhomkhai on Pexels

An agent that understands what you need and uses your tools

When it's useful, we build a custom assistant using a software development toolkit, known as an SDK. That toolkit helps us build its functionality and give it the ability to work with the business's applications. Once you get past that explanation, the important part is much simpler: it's your agent, set up to help you with your tasks.

We can design it with different capabilities: checking and managing appointments, working with the calendar, kicking off invoicing steps, preparing reminders, or triggering a review request under the rules we've agreed on. The idea isn't to include everything from day one, but to choose the capabilities you need and connect them to your tools.

For example, you might ask over WhatsApp: "Block off tomorrow from four to six and tell me what appointments we have in that window." If that feature is set up, the agent can check the calendar and help you with the corresponding changes. Actions that need your confirmation are presented before they're carried out.

Its value isn't that it can chat a lot, but that the conversation is useful for getting work done. Asking for a summary, checking a request, or starting a routine task can become a simple alternative to clicking through several screens.

Building and configuring it for your business lets us tailor its capabilities, its permissions, and how it responds. That doesn't make it infallible, nor does it mean building every component from scratch. What matters is reviewing and testing that it handles the intended tasks and knows when to leave a decision in your hands.

The agent and the automations do complementary jobs

The agent interprets what you ask it and uses the capabilities we've given it. The automations connect the tools and run defined steps. They're complementary functions: not every reminder or data transfer needs to depend on a conversation with artificial intelligence.

A scheduled alert can run through a simple automation. On the other hand, understanding a written request phrased in different ways and looking up the right information can be a useful task for the agent. We choose whichever combination makes the process clearer and easier to maintain.

n8n is one of the tools we can use to connect applications and organize those steps. For example, Baserow's official n8n guide documents its integration for querying, creating, and updating records. It's one option among those we consider depending on the project's needs.

Imagine an appointment request coming in to a clinic. The solution can gather the necessary details, check availability, log the booking according to the configured rules, and prepare a reminder. If an exception comes up, it lets you know. The clinic's client sees simple, smooth service; you avoid repeating the same information in every application.

That's the outcome we're after when we connect the pieces: a continuous way of working. Not a calendar on one side, messages on another, and a to-do list someone has to reconcile at the end of the day.

Why we usually consider a VPS when there are several needs

If the business needs an agent, automations, and several connected applications, it makes sense to look at a dedicated setup to host the main pieces. This usually means a VPS: a virtual server contracted to run the business's software.

That doesn't mean putting a machine in the clinic or asking you to learn how to administer it. The setup comes with a maintenance agreement so we take care of keeping it running. You use the solution; we handle the technical side.

In that environment we can host the agent, the automation software, and whatever applications need to be integrated. Keeping them under a single administration makes it easier to organize their connections and adapt the whole thing as your way of working changes.

We can also set up communications between the self-hosted tools so they happen within the setup itself. That avoids intermediaries the process doesn't need and gives more control over the internal exchange of information.

Sharing a server doesn't automatically connect the applications on its own. Integration is part of the configuration work: deciding what data each tool needs, how it's updated, and what should happen when information is missing. That work is exactly what turns several programs into a solution that's useful to you.

A foundation that can cover more functions over time

Once that infrastructure exists, we can use it for other real needs. It might make sense to add the business's website, an app for organizing information, or an analytics tool. There's no need to contract a separate server for every function if the capacity and configuration allow sharing it.

This changes how you should think about the initial cost. Setting up the agent and the automations can become a foundation for handling more tasks, instead of starting each need from scratch. The shared cost of the VPS gets spread across the solutions it hosts.

We can consider tools like Baserow for data or Matomo for analytics, as long as their features fit. Their free and paid tiers need to be taken into account: self-hosting doesn't mean every commercial feature comes at no cost.

Behind the scenes we also use deployment and monitoring tools, such as Coolify, Beszel, or Uptime Kuma, when they're a good fit for the setup. These aren't programs you have to learn or a list of products you need to buy. They're part of the work involved in managing and monitoring the solution.

The rule is to add what brings value. If your business doesn't need a feature, installing it doesn't save anything. If the whole system needs more capacity, that gets built into the planning. We want to make good use of a shared foundation, not pile up applications that make the service more complicated.

Photo by Towfiqu barbhuiya on Pexels

How sharing infrastructure can improve the bill

The financial comparison should include what you actually need: hosting, any required licenses or subscriptions, setup, and maintenance. On the SaaS side you also have to count the configuration and professional support the whole thing requires.

n8n, for example, has a free Community edition for self-hosting. That makes it possible to consider a solution without that software fee, as long as the features and terms of use fit. External services we connect to it can still carry a cost.

Hypothetical example: if the required SaaS subscriptions add up to 240 euros a month and a self-hosted alternative covers those same needs for 120 euros a month, including the VPS, the necessary subscriptions, and maintenance, the difference is 120 euros a month. That's 1,440 euros a year.

With that saving, an initial setup cost of 600 euros would pay for itself in five months, assuming there were no other initial or additional costs that would change the comparison. This isn't a rate or a promise for every client: the numbers are meant to show how we work out the math.

The savings can become more noticeable when several tools replace fees you were already paying and make use of shared resources. But the value doesn't stop there. It also matters that you stop copying data by hand, coordinating tasks manually, or checking several applications to get an answer the agent can prepare for you instead.

External services have their place too

Preferring self-hosting doesn't mean ruling out external services. If you use Gmail, your email runs through Gmail. If we communicate over WhatsApp, the messages use its platform. And if a specialized program covers part of the business well, we can keep it and integrate it wherever possible.

What we're after is not depending on additional services when they don't add a needed function. If two self-hosted tools can exchange information internally, there's no need to bring in another intermediary just to move it between them.

The solution can be self-hosted in some parts and external in others. What matters is knowing what job each piece does, how it connects, and what costs it carries. The client should get an understandable explanation of the whole thing, without having to learn its technical details.

When the outcome is equivalent, our preference will be to host the pieces that give us the most room to adapt and continue over time. When an external tool offers a clear advantage, we'll bring it in. The decision is made based on the work it solves, not on keeping a technology label.

We take care of maintenance, and you keep the choice

The self-hosting we propose is managed. We take care of setting up the tools, maintaining them, checking that everything's working, and preparing for recovery if something goes wrong. The client has a point of contact and an agreed service — not an obligation to look after a server.

Security and backups are part of that management. Having more control over the setup lets us tailor access and safeguards to the solution, though the type of hosting on its own doesn't guarantee security or legal compliance. What matters is applying what's needed and keeping it up throughout the system's use.

If you decide to switch to a different provider, we prepare the handover so you can carry on with your tools, your data, and the configured automations. If you need to change hosting, we can arrange the migration of the setup while keeping the same software. That technical work shouldn't force you to learn another application just because you're changing providers.

This ability to carry things forward is one of the reasons for our preference. We want the business to be able to keep the solution it has invested in, and to keep working with us because the service is genuinely useful to them.

For a hair salon, a clinic, or a small office, that setup should translate into practical peace of mind: knowing who's in charge, how to ask for an adjustment, and what steps are followed if something needs to change.

Photo by Ivan S on Pexels

How we choose the solution together with you

First we listen to what you need to achieve and why. We review the repetitive tasks, the interruptions, and the applications you already use. Then we identify which processes are worth automating and where an agent can make your work easier.

From there we design a concrete proposal: tools, capabilities, connections, and a simple way to use it all. It doesn't have to be the same for every business in the same industry. Two clinics might share some needs and still require different rules for their calendars or their client service.

Next we compare hosting options and the costs of the whole package. If one or two SaaS applications handle it well, we consider them. If several needs would benefit from a connected agent and automations, we look at a managed self-hosted foundation. A combination can also make sense.

The setup is organized so the solution is up and running within a month, with the scope and steps agreed from the start. We test the planned processes and show you how to use them. You don't need to know how the agent is programmed or how the VPS is administered in order to ask it a question or manage a task.

What we want to check once it's done is simple: whether it saves you work, whether it fits your business, and whether you know how to use it when you need it. Those answers matter more than the number of applications installed.

Our preference: less work for you, more freedom to adapt

We don't start by selling a VPS, an agent, or a subscription. We start by designing a way to take repetitive, technical work off your plate so you can focus on your business.

When several needs call for connected tools, a custom agent, and automations, managed self-hosting is usually an option worth considering. It lets us tailor the whole thing, make use of shared infrastructure, and keep your applications if you ever change hosting or maintenance providers.

And, all else being equal, that's our choice: we prefer self-hosting for the room it gives us to customize, the control, and the continuity it can provide. If a SaaS answers a specific need better, we use it or combine it with our own tools.

For you, the result should show up as fewer pending tasks, fewer steps between screens, and a simpler way of working. The technology and its maintenance stay on our side; the decisions about your business stay on yours.

Cover image: panumas nikhomkhai on Pexels