# Pricing and Evaluation Policy

This page defines the commercial packaging policy for Nexamas UI. It is documentation of the product's business boundary and does not replace `LICENSE.md`, a signed order form, an invoice, or legal review.

## Commercial position

Nexamas UI is proprietary commercial software. The default business model is:

- short evaluation access before purchase,
- paid commercial use after evaluation,
- customer-specific terms through written order form or agreement,
- third-party notices handled separately in `THIRD_PARTY_NOTICES.md`.

## Seven-day evaluation

The default evaluation period is seven consecutive calendar days.

The evaluation period starts on the earliest date the evaluator downloads, receives, installs, restores, accesses, or otherwise uses any Nexamas UI package, source distribution, private feed, documentation pack, or related SDK asset.

Evaluation access is allowed only for:

- internal technical evaluation,
- compatibility testing,
- learning,
- non-production prototype work.

Evaluation access is not allowed for:

- production use,
- customer delivery,
- paid client work,
- distributing applications that include or depend on Nexamas UI,
- publishing or sharing Nexamas UI packages, source, credentials, or documentation packs,
- repeated trial cycles intended to avoid purchase.

After the evaluation period ends, the evaluator must buy a commercial license or stop using Nexamas UI and delete unlicensed copies, except for records retained for legal, accounting, or compliance reasons.

## Important implementation boundary

This source snapshot documents the seven-day evaluation as a legal/commercial term. It does not implement runtime license activation, online entitlement checks, customer portal billing, telemetry metering, or automatic seven-day technical lockout.

Safe wording:

> Nexamas UI includes a seven-day evaluation term in its license policy.

Unsafe wording without adding and verifying a runtime licensing system:

> Nexamas UI automatically expires after seven days.

> Nexamas UI includes online activation and license enforcement.

## Suggested offer tiers

The exact prices can be changed before public launch. The repository should not hard-code final public prices until the sales policy is final.

| Tier | Intended use | Suggested commercial boundary |
|---|---|---|
| Evaluation | Internal review before purchase | Seven days, non-production, no redistribution |
| Indie / Solo | One developer, one product line | Binary package license, basic updates during license term |
| Small Team | Small commercial team | Multiple developer seats, permitted product/app list, update/support term |
| Company | Company adoption | Written order form, seats, permitted products, support/update terms |
| Source Access | Special commercial delivery | Requires explicit written source-access terms |

## Order-form fields

Every paid license or extended evaluation should define:

- customer or legal entity,
- license type,
- license term,
- evaluation period if different from the default seven days,
- developer seat count,
- permitted products or applications,
- binary package access,
- source access if included,
- private package feed access if included,
- support level,
- update entitlement,
- redistribution rights for runtime binaries,
- confidentiality and source-control restrictions,
- effective date.

## Release policy

The current internal package line can remain `0.0.x` during packaging work. The first public commercial lane should promote to:

```text
Release candidate: 1.0.0-rc.1
First stable release: 1.0.0
```

Do not publish the first stable commercial release as an internal build number such as `0.0.41`.