Skip to content

Why your software should stay yours

Custom software you don't own is really just rent.

Ownership is not a detail

A lot of custom software runs on the builder's platform. As long as the collaboration goes well, you barely notice. But when you want to move on with someone else, or develop it further yourself, the code turns out not to be yours.

You often only find out at the moments that matter: during an acquisition, when your own team wants to take over, or when your supplier stops. By then it is too late to make arrangements.

What ownership means in practice

  • Source code. You get the code in common technology, Python and SvelteKit. Any developer can take it further.
  • Repository. The code is under your own control. If you have no GitHub, we offer it as a managed service.
  • Deployment. The application runs on its own and without a license check, on your servers or managed by us.

That stays true when we generate with Fractal Forge. Only regenerating from the model uses Fractal Studio. The application itself does not need it.

There is a clear line, though. Custom code made specifically for you may also be used elsewhere. You may use and further develop the generated code within your own organization, including for other applications. You just may not resell it.

What it gets you

Ownership keeps your options open. Heaten grew from 5 to 65 people and was acquired by INNIO. Heavy enterprise software decisions could wait until after the acquisition, and the new owner could then roll out its own blueprint without rebuilding everything.

Flipstream switched databases and moved from the cloud to on-premise, within days and without downtime. That was possible because the core of the software is not tied to the infrastructure.

With us or without us

With us you can get the source code, the repository and the deployment under your own control, even if we run it for you as a managed service first. You can always carry on yourself, with us or without us.