# A Premium key is not a support contract

---

`flisk up` does not need a key. Core is MIT. Most teams should stay there. Premium is optional, at $19 per developer per month, and it unlocks extras. It does not buy an SLA, a weekend page, or a promise that someone will join your incident.

The repo is explicit about what it does not publish: the price lives on the site, the licence terms for the premium code are not in the tree, and a premium key is a feature key. Read that again before you put the key in a runbook titled "support".

## What the key is for

The extras called out in the project docs are a local Verdaccio registry, a DDD scaffold, and idle stop. They are gated. The core path, including `flisk up`, is not.

Set the key in the environment the CLI already looks at:

```bash
export TDK_LICENSE_KEY="the-key-you-were-sent"
```

The variable still says `TDK_` because the on-disk names were not all renamed. That is the same CLI. See the post about `flisk` versus `tdk` if that bothers you. Do not invent `FLISK_LICENSE_KEY` and then wonder why the extra stayed locked.

A key is capped. The site says up to 100 project IDs on one key. A key posted in a public chat is not a team plan. It is a key you can no longer revoke per person.

## What you do not get

You do not get production hosting. You do not get Helm values. You do not get a measured onboarding number. The speed figures on the site are lab runs, including a 100-service health fixture that is not an ERP. The savings calculator is arithmetic on inputs you type.

You also do not get a second support tier because you paid. If `flisk doctor` fails, the fix is the `ℹ Fix:` line. A key does not change that line.

If you want a key, use the request on [flisk.sh](https://flisk.sh). If you do not want the extras, do not request one. The free CLI is the product. The $19 is a feature flag with a price, not a reason to migrate a monorepo.

[github.com/flisk-sh/flisk](https://github.com/flisk-sh/flisk)