Infrastructure and cloud 7 min

Self-hosting: which tools to move out of SaaS first

The tools to self-host first are those that cost a lot per user and whose self-installed equivalent is mature: CRM, process automation, web analytics, electronic signature and invoicing. You start with a non-critical tool to get operations up to speed, then move on. Email, office software and payroll generally stay on SaaS.

Contents8
  1. 01Why you do not leave everything at once
  2. 02The criteria for choosing the order
  3. 03The order we recommend
  4. 04What stays on SaaS
  5. 05What you need before the first service
  6. 06The honest limits
  7. 07Where to start
  8. 08Frequently asked questions

Why you do not leave everything at once

Which tools should you self-host first? Not all at once. You first move a low-risk tool to learn how to run a server, then the tools where the cost gap is largest, and you keep on subscription whatever is critical and hard to maintain.

From the field

Our own server runs a dozen services

Behind a Traefik router run the Twenty CRM, which we have operated since early 2025, n8n automation, Matomo web analytics, electronic signature (Docuseal, Documenso), invoicing (InvoiceNinja) and AI models (Ollama).

The order below is the one we would recommend to a company of 20 to 500 people starting from scratch. It is also the logic of our SaaS exit, where your tools switch over one by one and the old one stays available until the new one has proved itself.

The criteria for choosing the order

Before listing any software, four questions per tool:

  1. How much does it cost, and how? A tool billed per user weighs more and more as the team grows. A fixed plan, much less.
  2. Is the open-source equivalent mature? An active project, up-to-date documentation, regular releases, a community that answers.
  3. What happens if it goes down for a day? A statistics dashboard that stops for a day blocks nobody. A mail system that stops for a day blocks the whole company.
  4. Is the data sensitive? Customers, contracts, figures: that is an argument for keeping it with you, but also a reason to demand impeccable backups.

The full financial calculation, tool by tool over three years, is detailed in our article on the real cost of leaving SaaS.

The order we recommend

1. Web analytics, to get operations up to speed

Matomo replaces an audience-measurement tool hosted by a third party. Its FAQ on costs and prerequisites states that no licence is due to run it on your own server, and that it needs a web server with PHP and a MySQL or MariaDB database. It is a good first service: it is not very critical (an hour’s outage loses measured visits, not sales), it forces you to put in place everything the following ones will need (domain name, certificate, database, backup), and it brings back in-house browsing data that you may not want to entrust to a third party. If the first service goes badly, better that it be this one.

2. Process automation

n8n can be deployed self-hosted and connects your tools to one another: form to CRM, invoice to accounting, alert to a messaging tool. The benefit is twofold. Hosted automation plans are often paid by volume: n8n’s own was, in October 2026, by the number of executions per month, according to its pricing page, so the bill rises when processes work well. And an automation tool on the same server as your other tools calls them without going out onto the internet.

Watch out

An automated process that stops does not always warn you

Monitoring failed executions is part of the deployment, not an optional extra.

Also check the licence: n8n is used under its community licence, officially the Sustainable Use License, and according to the FAQ of that licence, use is unrestricted as long as the automations are created or modified by you or by people in your organisation.

3. The CRM

A hosted CRM is most often paid per user, and the whole sales team uses it: the gap widens with every hire. Twenty is an open-source CRM that you deploy yourself; its pricing page offered in October 2026 a hosted version billed per user, and specified that the open-source core can be self-hosted without a licence, with single sign-on (SSO) and row-level permissions requiring the paid Organization plan. For needs broader than a CRM (invoicing, stock, projects), other open-source software exists, with very different scope and deployment effort.

The CRM comes third and not first because it is a living tool: salespeople use it all day, importing the data takes care, and an interruption shows. Operations need to be up to speed first.

4. Electronic signature and invoicing

Open-source tools exist for getting documents signed and issuing invoices. They plug naturally into the CRM and the automation. Two checks before moving them: the legal value of the signature for your uses (and the level of signature your contracts require), and your country’s electronic invoicing obligations, which are changing. In France, the French tax authority’s page on electronic invoicing sets out the timetable:

  1. 1 September 2026

    All companies must be able to receive electronic invoices. Large and mid-sized companies must also issue them.

  2. 1 September 2027

    Small businesses and micro-enterprises must in turn issue electronic invoices.

Each company must also choose an approved platform. Before moving your invoicing, check how the chosen tool exchanges with that platform. A tool that does not keep up with these obligations becomes a problem, whatever its cost.

What stays on SaaS

  • Email and office software. Email deliverability, spam protection and availability are full professions in themselves. The gain does not pay for the risk.
  • Payroll and statutory accounting. The rules change often, and your accountant probably works in a specific tool.
  • Any critical tool with nobody to maintain it. If nobody, in-house or at a provider, can step in quickly when something breaks, the subscription remains the right answer.

What you need before the first service

A server is more than a machine switched on. Before putting a first tool on it:

  • a router that manages the certificates and domain names of each service;
  • backups held off the server, and a restore already tested (we detail what breaks in practice in our guide to backing up your own server);
  • scheduled updates, with a way of rolling back;
  • monitoring that warns you when a service stops responding;
  • operating documentation that someone other than the person who installed everything can read.

These building blocks form the common foundation for all your projects: our guide to the cloud infrastructure foundation details them.

The honest limits

A single server running all your tools is also a single point of failure. We have lived it:

From the field

A cleanup command deleted the containers of ten services at once

The data, stored in volumes, was saved, and our operating rules were born from it.

A single server remains acceptable for an SME if the backups and the restore are solid and if an interruption of a few hours does not stop the business. Otherwise you need redundancy, which costs more and requires more operating effort.

And sovereignty comes in degrees: a server rented from a European host is not the same thing as a server on your premises. We discuss this in our article on Europe’s dependence on the American cloud.

Where to start

Start with an inventory of your subscriptions, then a first low-criticality service, such as web analytics, to bed in backups and monitoring before touching the CRM. If you want to know which tools to start with in your own case, our SaaS exit starts with an audit of your subscriptions and their real cost over three years. The other infrastructure choices, from the cost of an exit to backups, are gathered in our Infrastructure and cloud section.

Frequently asked questions

Which open-source software can you host yourself?

For an SME, most management tools have an equivalent that installs on a server of your own: CRM, web analytics, electronic signature, invoicing, document management, and even AI models. The criterion is not the list, it is the maturity of the project (regular releases, up-to-date documentation, active community) and your ability to run it. Also read each licence: some restrict commercial use.

Do you need a VPS or a dedicated server?

A virtual private server (VPS) can be enough to start with: ours runs a dozen containerised services, behind a router, on a single machine. There is no need for a server per tool, but you must watch resources and isolate the databases. A dedicated server is justified when the load grows or you want the machine to yourself. In both cases, backups go elsewhere.

Can you go back if the self-hosted tool does not suit?

Yes, provided you plan the way back before the switch. Keep the subscription active until the new tool has proved itself, check that your data exports in a format the old tool can read back, and decide in advance what will trigger the return: a deadline, an incident, a use that does not take. In our SaaS exit, the old tool stays available until that point.

Sources

  1. The FAQ of that licence (new tab)docs.n8n.io
  2. Pricing page (new tab)twenty.com
  3. The French tax authority’s page on electronic invoicing (new tab)impots.gouv.fr
Source 1

The FAQ of that licence

Read on docs.n8n.io(new tab)
Source 2

Pricing page

Read on twenty.com(new tab)
Source 3

The French tax authority’s page on electronic invoicing

Read on impots.gouv.fr(new tab)

Jim · founder of Brain Plus AI

Also in infrastructure and cloud

  • Choose and price8 min

    Leaving SaaS: the real three-year cost for an SME

    Before you drop a single subscription, you need to compare two full costs over three years, human hours included. Here is the method, line by line, and what the calculation does not see.

  • Practical guide7 min

    Backing up your own server: what really breaks

    Everyone knows the 3-2-1 rule, but what loses data is more mundane: a backup never restored, a forgotten volume, a global clean-up command run in production. Here is what we learned from operating our own server.

  • Stepping back11 min

    Sovereign cloud: can you do without the American giants?

    European providers now hold only 15% of their own cloud market. Full sovereignty is out of reach; selective sovereignty starts with sorting your data and planning an exit.

WhatsApp