Documentation
Licensing
Walnut is proprietary software. Community builds show branding; Commercial seats turn branding off.
Editions
| Edition | Branding | Unlock |
|---|---|---|
| Community | Splash and credits on launch | Default (no valid license) |
| Commercial | Splash and credits off | Signed license from the package registry |
Pricing (annual only)
| Offer | Price | How |
|---|---|---|
| Early Adopter | $99 / seat / year | Self-serve at walnutlang.com/pricing |
| Commercial | $249 / seat / year | Self-serve (list price) |
| Enterprise | Custom | Talk to sales |
There is no month-to-month plan. Above the published revenue / funding threshold in the commercial agreement, Commercial is required to ship store builds without Community branding. There is no per-install runtime fee in v1.
Buy seats: Pricing → sign in on the registry → Stripe Checkout → walnut license login --org <slug>.
Signed license files
The package registry issues short-lived signed license files for orgs with a commercial entitlement. Log in as an org member and download a file the CLI trusts offline:
walnut license login --org acme
walnut license status
walnut license refresh
License path: ~/.walnut/license (override with WALNUT_LICENSE).
If walnut license status asks you to upgrade walnut, install a newer CLI
(e.g. brew upgrade walnut) and try again.
Without a valid license, build / simulator / device stay on Community. With a valid license, they run as Commercial.
Registry admin
See registry.md for issuing seats and marking orgs commercial (including Enterprise deals closed offline).
Related
- registry.md — login, publish, commercial seats
- homebrew.md — install the toolchain
- app-store.md — shipping to the store