Technology should serve humans, not the other way around.

I

Everything is a system.

Our daily life is steeped in systems that cross and overlap: the family system, the organizational system, the financial system, systemic oppression, and so on.

To survive and to meet their own operating needs, organizations have to put systems in place. A pile of software wired together to run the day-to-day: project management, accounting, invoicing, sales, communication, resource management, and the rest.

The problem?

Almost everything an organization does to function depends on computer systems it has no control over, supplied by companies with priorities of their own.

So organizations end up locked in golden cages, tenants of their own information system. Which leaves them here:

The mental load of running an information system is not a small thing, and some technology choices can become vital to the whole organization.

We have the illusion of choice and of freedom, but we only ever navigate from constraint to constraint, paying a high price in money, in time, in energy and in uncertainty.

That high price has a name: SaaS. A model where you rent your ability to function from someone who can switch it off, change what it costs, or take a piece away without asking you.

Every arbitrary limit, every update endured, every workaround bodged together is time stolen from what counts: understanding a trade, getting a detail right, repairing something before it breaks. We spent our days negotiating with the software instead of looking after people.

II

What if your information system belonged to you?

The first move was to separate the business from the infrastructure. We have always designed applications with the business logic sitting directly in the code. What if instead we structured the expression of a business information system, readable by an infrastructure that adapts to it?

That left defining what such an infrastructure should be able to do. We wrote the specification before the first line of code. It would take a tool that could:

III

Sovrium, the engine we wish we’d had.

After three and a half years of self-funded development (and the happy arrival of Claude Code), we are proud to present our own answer: Sovrium, a configurable web application engine. It is not sovereign. It is what makes you sovereign. A purely business configuration, read by an infrastructure that adapts to it, hosted by you.

Here is what that changes, said in the first person:

And what it really changes does not fit in a list. When the tool stops resisting, the time it was absorbing comes back where it does some good: listening to the person who uses it every day, fixing what slows them down before they give up on reporting it, keeping the promise we made a client.

That is what care is. And it is exactly what rented software never once let us do.

These are not idle words: we are our own client, and we will be our most demanding one.

If the Sovrium product breaks, the Sovrium company feels it directly. That puts us on the front line of the quality of the work we do, and makes us the first demonstration of what this technology makes possible.

IV

How we make a living.

We do not want our web application engine to be conditional on a payment in order to be used. We want its power available to any organization, whatever its means.

That position is what lets us offer a product that depends on no one, with source code 100% accessible and open to outside contributions. The engine is under the BSL today, with the intention of becoming 100% open source (AGPL) over time.

Even so, we have to be able to pay ourselves to keep working on it.

Sovereignty someone sells you is not sovereignty any more.

So we do not sell access to sovereignty: we sell acceleration and ease on the way to it.

We build with those who want to take back control, not with those who want to outsource everything.

For that, we stand on three services:

We will never…

The possibility of being sovereign, of having control over your data and over the features of your information system, and of being able to make it evolve over time, should not be for sale: it should be a right and a skill within easy reach.

Sovereignty, for us, is not only technical. It is financial too.

We are bootstrapped, self-funded, and against the idea of turning the Sovrium company into a financial product. No exit for us: we are here to stay. The people who steer the company are the people who work in it, who build Sovrium from the inside.

That is also your best guarantee of having, over the long run, guardians of the product’s quality and integrity.

V

Let’s build the future of sovereignty.

We are convinced that in the future, every organization will own the information system that lets it live and function day to day.

It will soon look absurd to pay for software you have no control over, when you can do what it does at home, easily, with quality, and for less.

We also believe that this technology, paired with AI, will make organizational problems easier to face, bringing calm and efficiency to teams that need to be properly equipped to carry out their mission.

And our third position on sovereignty is the human one.

We want to work with people and organizations seeking to be sovereign over themselves, autonomous in their capacity to do and to be, always hungry to learn and to grow, and to reconcile all of that with care.

It is easier to take care of others when you are able to take care of your own needs. And care is sorely missing from our professional world.

Let’s take care of our tools, of our organizations, of the people who keep them alive. Let’s become sovereign.