# SEAM Commercial Licensing

SEAM is source-available proprietary software. Public source access is provided so people can review, evaluate, learn from, and contribute to the project. Public source access does **not** grant commercial, hosted, SaaS, embedded, redistribution, resale, managed-service, customer-deployment, or closed-source product rights.

The controlling terms are the [SEAM Source-Available License](LICENSE). This file summarizes the commercial boundary in plain language.

## Permitted without a separate commercial license

Subject to the license, you may:

- read and review the source code and documentation;
- run SEAM locally for personal, educational, research, or non-commercial evaluation;
- fork SEAM to prepare contributions back to this repository;
- modify SEAM locally for permitted non-commercial evaluation; and
- use SEAM in a non-commercial open-source project that does not host, resell, embed, redistribute, commercialize, or expose substantial SEAM functionality to third parties.

## Not permitted without a separate written commercial license

You may **not** do any of the following without a separate written commercial license from the project owner:

- host SEAM, modified SEAM, or substantially similar SEAM functionality as a service;
- offer SEAM as SaaS, a hosted API, a managed service, a cloud service, or a customer-facing product;
- embed SEAM in a closed-source, proprietary, or commercial product;
- use SEAM for paid consulting, integration, support, operations, or customer deployment;
- sell, rent, lease, sublicense, redistribute, or charge for access to SEAM;
- use SEAM to build, operate, or market a competing hosted product or service;
- remove or obscure copyright, ownership, license, or notice files; or
- imply that SEAM endorses your product, service, benchmark, or derivative work.

## Commercial permission

Commercial use is available only through a separate written agreement with the project owner. If your use could make money from SEAM, help a customer make money from SEAM, expose SEAM functionality to third parties, or place SEAM inside a paid product or service, get written commercial permission first.

## Public vs private project boundary

The public repository is intended to prove the product shape, support evaluation, and accept contributions. Advanced commercial modules, private benchmark holdouts, enterprise connectors, hosted-service components, and unreleased methods may live outside this public repository.

That split is intentional. The public repository should be useful enough to evaluate and contribute to SEAM while keeping commercial-only implementation details under separate access control.
