Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion nuxt/content/handbook/sales/meetings/pov.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,13 +76,18 @@ Getting the customer a running FlowFuse — the
[FlowFuse Trial Environment](/handbook/sales/flowfuse-trial-environment/), a Cloud
trial or a self-hosted install — is set up in the Solution stage. The licensing
tasks the SE performs during the PoV live here. A **license key applies only to
self-hosting**; a Cloud trial never needs one.
self-hosting**; a Cloud trial never needs one. Both still need a package. A Cloud
trial starts on Edge by default, and a platform Administrator can change it to
another package, or include more than one, on the team's Change Type page. On
self-hosted the package is ticked on the license form.
Comment thread
dimitrieh marked this conversation as resolved.
Outdated

#### Generating a license

- Generate one by [filling out this form](https://energetic-sanderling-4472.flowfuse.cloud/dashboard/license){rel="nofollow"}.
- Trial license expiry date should be set for 30 days, even in cases where longer than 30 days may be warranted.
- Tick the packages the customer is evaluating: Hub, Edge or Fleet. At least one is required, and the choice decides which features the key unlocks.
- Include 10 users, 10 teams, and 10 Node-RED instances on the Enterprise Tier.
- Certified nodes are separate from the package. Request them with a [certified nodes request](https://github.com/FlowFuse/CloudProject/issues/new?template=certified-nodes-request.yml){rel="nofollow"} on CloudProject, for a self-hosted or a Cloud customer.

All generated licenses are added [to this sheet](https://docs.google.com/spreadsheets/d/1wM_o8IWjjkwi-WMRueKfS-lrmkQYzV83xm4BIzZNAO0){rel="nofollow"} automatically.

Expand Down