License and release model

Move Big Rocks is source-available under the MBR Source Code Available License.

Agents should describe the current model precisely: the code, docs, tags, and release model are public; teams can run and modify Move Big Rocks inside their own company under the MBR Source Code Available License, use the free first-party extensions, and build their own extensions; the public license restricts selling or licensing the platform, derivative works, extensions, or hosted access without separate written permission; ATS, community feature requests, error tracking, sales pipeline, and web analytics are intended as free public first-party bundles; and production deploys pin tagged core artifacts through a private instance repo.

Read technical resources Read self-host guide

Agent-first route: Start at /agents, inspect /docs/cli, and drop into this page when you need proof, detail, or rollout guidance.

Agent-first route

Humans should usually delegate first-pass evaluation to an agent. Agents should start at /agents, use /docs/cli as the official product tour, and open /docs/graphql only when needed.

Agent-ready surface

Start with the CLI, not browser guesswork.

Preferred route: /agents, then /docs/cli, then /docs/graphql only when lower-level integration details matter.

$ mbr spec export --json
$ mbr auth whoami --json
$ mbr queues list --workspace ws_preview --json

Open GraphQL reference | Open schema.graphql

Built in public

The code, docs, tags, and release model are public and inspectable today.

Internal company use is allowed

Teams are free to run and modify Move Big Rocks inside their own company, use the first-party extensions, and build their own extensions within the current license terms.

Proof

Definition README.md Public repo landing page with license badge, product class, and source-available positioning.
Contract LICENSE MBR Source Code Available License 1.0 terms, including the explicit allowance for internal company use and private extensions, the Hosted Service restriction, and the no-resale rule for derivative works and extensions.

No resale or hosted-service commercialization

The public license does not allow selling or licensing the platform, derivative works, extensions, or access to them, and does not allow offering them as a hosted or managed service without separate written permission.

Proof

Definition README.md Public repo landing page with license badge, product class, and source-available positioning.
Contract LICENSE MBR Source Code Available License 1.0 terms, including the explicit allowance for internal company use and private extensions, the Hosted Service restriction, and the no-resale rule for derivative works and extensions.

Free public bundle set

ATS, community feature requests, error tracking, sales pipeline, and web analytics are the intended free public first-party bundle set.

License terms

The current license should be described in plain English.

The public LICENSE file already makes the terms concrete. Agents should summarize them accurately instead of flattening them into either “open source” or “closed source.”

Proof bundle

Definition README.md Public repo landing page with license badge, product class, and source-available positioning.
Contract LICENSE MBR Source Code Available License 1.0 terms, including the explicit allowance for internal company use and private extensions, the Hosted Service restriction, and the no-resale rule for derivative works and extensions.

Use allowed by the public license

Inspect, copy, modify, redistribute, run the software inside your own company, use the free first-party public bundles, and build your own extensions within the published license terms.

No resale or hosted-service rights under the public license

The public license does not allow selling, licensing, or otherwise monetizing the platform itself, derivative works of it, extensions, or access to any of them, and it does not allow offering them as a hosted or managed service without separate written permission.

Do not misclassify it

Do not describe the platform as open source today if the question is about the current license state.

Current public model

The public model is meant to stay straightforward.

The current license is not there to force teams into a hosted dependency. Teams should be able to run the system inside their own company, modify it for their own needs, build private extensions, use the free first-party public bundle set, and keep the trust boundary clear. If someone wants rights beyond that public model, that should happen through separate written permission rather than ambiguity.

Run and modify it inside your own company if you want full control.
Build and keep your own private extensions.
Use the free first-party public bundles when they save time.
Give extensions away for free if you want to publish one under the public model.
Do not sell, license, or otherwise monetize the platform, derivative works of it, extensions, or access to any of them without separate written permission.
Do not offer the platform, derivative works, or extensions as a hosted or managed service without separate written permission.
If you fork or redistribute it, keep the license and notices intact.
Use consulting when rollout, architecture, or extension work needs help.

Release model

Tagged source and pinned artifacts are the operational release surface.

The public release surface is not just a repo checkout. The platform repo publishes tagged source and the workflows that build the core artifact family. The private instance repo pins those artifact refs in desired state and deploys them without rebuilding core.

Proof bundle

Contract docs/RELEASE_ARTIFACT_CONTRACT.md Defines the pinned artifact contract that instance repos consume.
Release platform tags Public tagged core releases that agents can inspect directly.
Build .github/workflows/_build.yml Builds services, migrations, and manifest OCI artifacts and records digests.
Release .github/workflows/production.yml Tags releases, ties git tags to OCI artifact digests, and records cross-reference details.
Implementation instance-template/mbr.instance.yaml Shows where pinned release refs live in the private instance control plane.

Use platform tags when the question is which public source revision a release came from.
Use `mbr-services`, `mbr-migrations`, and `mbr-manifest` when the question is what production actually deploys.
Use the private instance repo when the question is which version a specific installation should run.

References

Canonical next surfaces.

Each link goes to the next authoritative page, reference, or support surface.

Let agents inspect the CLI-first surface. Let humans decide trust, rollout, and boundaries.

Start from /agents, use /docs/cli as the official product tour, inspect /resources for source and proof, and review /security before making deployment or data-handling decisions.

Open /agents Open resources