From eval to developer
The same engine JARs power evaluation and paid tiers — what changes is 4h-license.properties.
| Eval (90-day) | Developer (annual) | |
|---|---|---|
| Tier | EVAL |
DEVELOPER |
| Usage | Non-production trial | Non-production development |
| Codegen | Evaluation scope | Unlimited dev codegen |
| Package folder | 4h-eval-* |
4h-developer-* (after shop download) |
| Obtain | Free registration | Shop checkout |
What does not change
- ExampleBank and Lucid examples
SessionManagerand node startup flow- Spec → validate → codegen tooling in the package
Swap the licence file and restart — no re-integration of FIX wiring for tier upgrade alone.
Folder name after purchase
Shop downloads are built from the same base artifact but renamed to 4h-developer-<version>/ with a developer README and signed annual licence.
Production path
Developer is still non-production. Professional / Enterprise add production ROE, support, and pricing via contact.
Next steps
- Getting started — first eval run
- 4H Academy — licence gate
- Buy developer licence