Source Code

Two parts of LyEve are MIT-licensed, and each image carries the MIT LICENSE for the code in it:

The engine. Content types and the Content API, users and roles, sign-in, draft and publish, revisions, and the PostgreSQL, MySQL and SQL Server support. Access rules are a feature, covered below.
The admin console.

Three parts are commercial, and their source is not public:

License verification. The server in the engine image includes it. It holds no secret, because verification is an offline Ed25519 signature check against a public key.
Every feature beyond the engine, including the ones included free. They are commercial software under the EULA. Free means free of charge, not open source.
The visual flow and schema editors in the admin image. They carry a commercial license of their own, which the admin image ships beside the MIT one as LICENSE-COMMERCIAL.md.

Check the licenses in the images

Each image says what it contains in its org.opencontainers.image.licenses label:

docker inspect --format '{{ index .Config.Labels "org.opencontainers.image.licenses" }}' \
  ghcr.io/lyeve-labs/lyeve-core:latest

Image	Label	Why
`ghcr.io/lyeve-labs/lyeve-core`	`LicenseRef-LyEve-Commercial`	The server in it also contains license verification and the features.
`ghcr.io/lyeve-labs/lyeve-admin`	`MIT AND LicenseRef-LyEve-Commercial`	The console is MIT, and the visual editors are commercial.

The engine image keeps its LICENSE and THIRD_PARTY_NOTICES.md in /usr/share/doc/lyeve/. Copy them out without starting the image:

id=$(docker create ghcr.io/lyeve-labs/lyeve-core:latest)
docker cp "$id":/usr/share/doc/lyeve/LICENSE ./LICENSE
docker cp "$id":/usr/share/doc/lyeve/THIRD_PARTY_NOTICES.md ./THIRD_PARTY_NOTICES.md
docker rm "$id" >/dev/null

Repositories you can read

Thirteen repositories are public on github.com/lyeve-labs, all MIT-licensed. The engine and the admin console are two of them:

Repository	What it is
`lyeve-core`	The engine
`lyeve-admin`	The admin console, without the visual editors
`lyeve-examples`	Runnable example applications
`benchmarks`	The performance benchmarks, to rerun on your own hardware

The other nine are the client libraries and the UI kit, each published on npm:

Repository	Published on npm as
`client`	`@lyeve-labs/client`
`client-rest`	`@lyeve-labs/client-rest`
`client-graphql`	`@lyeve-labs/client-graphql`
`client-grpc`	`@lyeve-labs/client-grpc`
`client-realtime`	`@lyeve-labs/client-realtime`
`client-react`	`@lyeve-labs/client-react`
`client-svelte`	`@lyeve-labs/client-svelte`
`client-vue`	`@lyeve-labs/client-vue`
`ui-kit`	`@lyeve-labs/ui-kit`

What this means in practice

The product you run is the image ghcr.io/lyeve-labs/lyeve-core, which carries the engine, license verification and every feature. A paid feature stays off until a license includes it. Verify Offline shows how to check the binary and that, given a signed token, it never calls home.
The MIT license covers the engine and admin code, including the right to modify and redistribute it. Read it, fork it and file bugs in lyeve-core and lyeve-admin. Support requests go through lyeve.com/contact.
The client libraries are fully open. You can read, fork and build every library your application links against.

Why this shape

MIT on the part that handles your data is what lets you keep running it, and change it, whatever happens to us. The features beyond the engine are where the product's commercial value is, and license verification is what enforces the plan you bought. Keeping both commercial is what makes a self-hosted license mean anything.