Not open source everywhere. Here's exactly where, and why.

The questions people actually ask

Why isn't the whole thing open source?

The FSL gives you nearly everything open source does — read, self-host, modify, run for any purpose — while preventing a well-funded third party from reselling Comebye-as-a-service against us before we have a moat. Straight MIT/Apache-2.0 on day one has a well-documented failure mode for small teams: a cloud vendor with more infrastructure than you forks the project and out-competes the people who wrote it. FSL is a deliberate, time-boxed trade, not a "look how open we are" trick — see fsl.software for the license's own reasoning.

Can you use my FSL usage against me — audit, revoke, sue for internal use?

No. FSL's only restriction is offering the software as a competing commercial product. Running it internally, self-hosting it for your own fleet, modifying it, and reading every line — all explicitly permitted, no exceptions, no "contact sales" gate.

What happens if the company disappears?

The FSL clock keeps ticking regardless of whether we're around to enforce it. Every released version converts to Apache-2.0 two years after release, automatically, release by release — a structural backstop that doesn't depend on anyone's goodwill or business continuing.

Can a license expiring remotely stop my containers?

No, by construction. License keys are Ed25519-signed files verified offline by the binaries — there is no online revalidation call and no kill switch. A lapsed license blocks new actions (like enrolling more hosts) after a grace period; it never touches a workload that's already running. We are technically incapable of remote revocation, and so is any future owner of the company — the guarantee is the absence of the mechanism, not a promise we're trusting ourselves to keep. See the pricing page's "2 AM rule" for the billing side of this same commitment.

What does the Solo "Lifetime" license actually cover?

Perpetual use of the Solo tier, all future updates including major versions, all future Solo-tier features, and security patches unconditionally — a lifetime that stopped covering v2 would be a trap, so it doesn't. It does not cover an SLA (community support only), Team/Enterprise features, or any future hosted service (a lifetime price only makes sense for near-zero-marginal-cost self-hosted software). It's offline-verified the same way every license is — no kill switch, no exception for "lifetime" pricing making it more revocable, if anything the opposite.

Why is the agent a different license than the server?

The agent runs with root-equivalent access on machines we don't own. That's exactly the code you shouldn't have to trust a license to audit — Apache-2.0 means you can read every line, compile it yourself, and verify what it does before you ever run it as root. The control plane doesn't run on your infrastructure the same way, so it's the one piece with a commercial restriction attached.