Self-hosted,or through a partner.

The software is free under the EUPL 1.2 and needs nobody’s permission. Some organisations want a name to call when a fleet stops behaving. Those are two different questions, and this page keeps them apart.

Nothing is held back from the free one.

There is no paid edition. The difference is who answers at two in the morning, not what the software can do.

Every feature
Self-hosted
Through a partner
Source and licence
Self-hosted EUPL 1.2
Through a partner EUPL 1.2
Seat count or expiry
Self-hosted
Through a partner
Where it runs
Self-hosted Anywhere, air-gapped included
Through a partner Anywhere, air-gapped included
Questions answered by
Self-hosted The issue tracker
Through a partner The partner you hired
Someone accountable
Self-hosted
Through a partner
Implementation and migration
Self-hosted Yours
Through a partner Theirs, if you buy it
Air-gapped networks
Self-hosted
Through a partner Yes, if you ask for it
Leaving costs you
Self-hosted Nothing
Through a partner Nothing, the fleet document is yours

Switching between the two moves nothing. The fleet document is a file in your own git, and it stays there either way.

Partners that offer Sextant as a service.

Each one sets its own scope and its own price. The project takes no cut and gives none of them a head start.

Steward of the project, and one of its partners

BB Open Solutions

Wrote most of the code and runs the release and security process. It also sells hosting, implementation and support, which is a separate role that carries no privileges. Every partner gets the same code, the same API and the same release, on the same day.

Room for more

One name on this list is one too few. That is a statement about how young the project is, not about how much room there is.

Put your company on this list.

The licence already lets you host, support and resell Sextant. Nobody has to approve that, and this page is not a gate. What the list asks is that you can actually do the work: you have imaged a fleet, you can read the code, and you answer the customer yourself rather than forwarding the question here.

  1. 1 Open an issue on Codeberg saying what you offer and where.
  2. 2 Point at something you have run, so the claim is checkable.
  3. 3 A maintainer adds you, or asks what is missing.

Not sure which of the two you need?

Describe the fleet: how many machines, what they run today, and what you have to prove to whom. Anyone here will say honestly whether this fits, including when it does not.

One document for every laptop.site.audit.

Take it, run it, help build it.

The software is yours under the EUPL 1.2 and needs nobody’s permission. What the project needs is people: a laptop model we have never imaged, a language nobody has translated, a bug found by running it for real.