Solidean Licensing: Simple, Flat, and Predictable

Solidean exists for one reason: reliable geometry processing.

In practice that means three things: operations must be robust, exact, and fast enough for real production pipelines.

Robust mesh operations are notoriously fragile. Small numerical issues turn into topological errors, and once those enter a pipeline they tend to propagate and get worse over time. The goal of Solidean is to remove that risk.

If the geometry kernel is supposed to be the reliable foundation of a system, the licensing should not introduce a different kind of fragility.

So we redesigned the licensing around the same idea: make it predictable, boring, and hard to get wrong.

Infrastructure software should have boring licensing

Many developer tools come with licensing models that add uncertainty instead of removing it.

Seat counting.
License servers.
Telemetry requirements.
Subscriptions that break deployment when they expire.

Those mechanisms might make sense for some products, but they feel wrong for infrastructure. If your build pipeline depends on a component, you should not have to worry about whether a license daemon is reachable or whether an expired subscription suddenly blocks shipping a patch.

For Solidean we wanted something simpler.

A flat annual license.
No seat counting.
No telemetry.
No license server.
No kill switches.

While the license is active you receive updates and basic support.
Any version obtained during that time can be used and shipped indefinitely.

In other words: if your system works today, the license should not make it stop working tomorrow.

Internal vs redistribution

The only distinction we could not reasonably avoid is internal use vs redistribution.

These are fundamentally different use cases.

Many teams use Solidean purely inside their own workflows: engineering pipelines, internal geometry processing tools, simulation preparation, or level editors used by their team.

Other teams embed Solidean in software that they ship to customers.

Those two cases have different economics and risk profiles, so they have different licenses.

The tiers look roughly like this:

Community
Indie (internal / redistribution)
Educational commercial
Pro (internal / redistribution)
Enterprise

The Community Edition remains generous on purpose. We want people to experiment, prototype, and build with Solidean without friction.

Indie and educational tiers exist because ecosystems grow from small teams and early projects. The goal is to make those paths accessible.

Guardrails

At the same time, Solidean is infrastructure that required years of engineering work to build. There are a few boundaries where standard licensing stops making sense.

For example:

• standalone geometry modeling tools built primarily around Solidean
• boolean-as-a-service platforms
• SDK-style wrappers that effectively repackage the kernel itself

Those uses are closer to redistributing the core technology rather than embedding it in a larger system.

There is also the practical side of support. Some deployments require SLA guarantees, custom engineering work, or formal agreements with procurement and legal teams.

That is where Enterprise licensing comes in.

Enterprise is not a company-size tax. It exists for cases where the standard terms genuinely stop fitting.

The bigger picture

Our goal is simple.

We want Solidean to become a piece of infrastructure that people can rely on for geometry processing. Something that removes a class of problems instead of adding new ones.

The licensing should reflect that philosophy.

Reliable geometry operations.
Reliable licensing.

Both should be boring in the best possible way.

If you want to try Solidean, the Community Edition is available now.

And if you are building something interesting on top of it, we would love to hear about it.

Getting Started

If you want to try Solidean, the Community Edition is available now.
Download it and see how it fits into your workflow.

If you are evaluating Solidean for commercial use, a detailed licensing overview will be published shortly.
Licensing Overview

And if your use case sits near the boundary of the standard licenses, or you simply want to talk through an integration, feel free to reach out.
Contact us.