elements
Manual Licenses

Licenses

elements man licenses Read as markdown

The runtime packages are MIT licensed. @elements/app is MIT licensed, and it includes the runtime that Elements HTML runs on, which is where most of an app's code is written. @elements/style is MIT licensed too. You own everything you build, and a built app runs on plain Node.js.

You pay for the tooling: the project server, build, test runner and deploy. The tooling is a subscription, per machine. The price is predictable per month, not based on traffic, requests or revenue.

What Is a License

A license grants one machine permission to run the elements tooling. One license, one machine. Any machine that runs the elements command needs one: your laptop, a CI runner, a deployment box.

The Trial

When your trial ends, run elements purchase to keep building. We hope you've had a great experience. Come join us.

License Files

The tooling installs two files next to its binaries, in the elements directory: LICENSE.txt, the license notice with the address of the Elements License Agreement, and THIRD-PARTY-NOTICES.txt, the license of every open source project linked into the elements binaries, including the TypeScript compiler the tooling is built on.

elements license

Shows the current license on this machine.

Terminal
elements license

Use this when you want to confirm a license is in place, or when an elements command mentions the license and you want to see the details.

Alias: elements l.

elements license checkout

Fetches a license for this machine.

Terminal
elements license checkout
elements license checkout <token>

Run it with no arguments to grab a license from your own account. This is what runs automatically after elements purchase, on every renewal, and when you check a license back in on another machine.

Pass a token when you're joining someone else's account. The token comes from the account administrator. It tells Elements which account the license should come from, so the seat counts against their subscription. This is how teams invite new developers to use Elements.

Deployment handles tokens automatically. The deploy command carries your account token to the deployment machine, so the license checks out on its own.

Alias: elements license c.

elements license checkin

Releases the license on this machine. The license becomes available for checkout on a different machine.

Terminal
elements license checkin

Use this when you're retiring a machine, moving development to a new laptop, or rotating a deployment box. After checkin, this machine drops back into the same state as a finished trial. After checkout on the destination machine, the new machine has full access.

Aliases: elements license release, elements license r.

Related