Documentation
Licensing
Walnut is proprietary software. Community builds show branding; Commercial
builds (splash off) need a signed license. A free packages.walnutlang.com
account is required for all use — run walnut login after install.
Editions
| Edition | Branding | Unlock |
|---|---|---|
| Community | Splash and credits on launch | Registry account + walnut login |
| Commercial | Splash and credits off | Signed license for an entitled org |
During early access, Commercial is invite / grant only — not a self-serve product. Request a founding seat at walnutlang.com/pricing after you create an account and ship something that isn’t a toy.
There is no published list price and no Checkout. Community stays free with splash and credits but is not anonymous.
After a grant: create a registry account → walnut login (pick your org) →
walnut license status.
Signed license files
The package registry issues short-lived signed license files for orgs with a commercial entitlement. Prefer browser login so token and license land together:
walnut login # browser: API token + optional Commercial license
walnut license status
walnut logout # shared machine: drop token + license
# or later:
walnut license login # prompts for org if omitted
walnut license login --org acme
License path: ~/.walnut/license (override with WALNUT_LICENSE).
Credentials: ~/.walnut/credentials. Use walnut logout (not only license logout) on a shared computer.
walnut check / test / run / simulator / device / TestFlight require a registry login. CI: walnut login --token wn_….
walnut license status re-checks the registry when logged in; if the org is no longer entitled, the local file is removed and the edition falls back to Community. Builds soft-check about once a day and send a CLI heartbeat so the registry can see active users. Offline, a signed Commercial file is trusted until expiry; Community still needs a prior login.
If walnut license status asks you to upgrade walnut, install a newer CLI
(e.g. brew upgrade walnut) and try again.
Without a valid Commercial license, build / simulator / device stay on Community (with splash). With a valid license, they run as Commercial.
Related
- splash-credits.md — Community splash, mark, and credits
- registry.md — login, publish, commercial seats
- homebrew.md — install the toolchain
- app-store.md — shipping to the store