Community Edition
Citrix SecurSpaces™ Community Edition includes all SecurSpaces features, with limits on the number of users and workspaces. This page describes the limits, how the license stays valid, and what the platform sends to Citrix.
Limits
| Limit | Enforced | |
|---|---|---|
| Users | 20 | When a user is registered |
| Workspaces | 10 | When a workspace is created |
Both limits are part of the signed license and are enforced by the server. No configuration or Helm value changes them.
The limits count every user account and every workspace, whatever its state. A stopped workspace or an unused account still counts. To free a slot, delete a workspace or a user account you no longer need.
Important:
SecurSpaces does not back up workspace files. A deleted workspace stays in the recycle bin, where its owner can restore it, for 7 days unless an administrator changed that period. After that, it is removed permanently. Check what is in a workspace before you delete it.
When you reach a limit
The platform refuses the request with one of these messages:
[LicenseManager] Your license does not allow creating any more workspaces
[LicenseManager] Your license does not allow registering any more users
When you create a workspace from the Create Workspace page, the message appears in a general error notification. It is the expected limit, not a fault.
Community Edition limits cannot be raised. A higher limit requires a different license.
How the license stays valid
You choose Community Edition once, in the setup wizard, the first time an administrator signs in. See After the deployment.
After that, the platform renews its license from
api.enterprise.strong.network on port 443 every two hours, for as long as it runs. Each license it receives is valid for 21 days. The entitlement behind it is registered to your portal hostname and lasts ten years from the first request.
Important:
If the cluster loses its route to
api.enterprise.strong.network, the platform stops being licensed at most 21 days after the last successful renewal. Administrators do not see an expiry warning on this edition. Developers start to see Your license will expire soon about 7 days into the outage. Keep this destination on your permanent outbound allowlist, not one used only for deployment.
Check whether license renewal is failing
-
Get access to the cluster:
az aks get-credentials -g <managed-resource-group> -n <cluster>
kubectl get deploy -A | grep coordinator -
Read the coordinator log:
kubectl logs -n <namespace> deploy/<coordinator-deployment> --since=48h | grep -Ei 'license|usage stats'
A successful renewal writes nothing to the log, so an empty result means nothing has failed only if the pod has been running for more than two hours. This line is normal behind a proxy that does not allow gRPC, and is followed by a successful fallback:
failed to fetch license with GRPC with error: ...; using REST API
A failure is a following error that names
https://api.enterprise.strong.network:443/rest/license. To fix it, reopen the route. The next renewal restores the license on its own. Restarting the coordinator does not help, because it restarts the two-hour interval.
Data sent to Citrix
The platform uses the same connection to send a daily usage record and telemetry events. The usage record contains:
-
User counts, workspace counts and workspace run times
-
Organization and project counts
-
The mix of IDE, SSH and terminal sessions
-
VDI counts
-
Kubernetes versions for each region
-
Identifiers of the days each user was active
If your organization reviews data flows, review this one before you deploy.
Features
Community Edition includes all SecurSpaces features, among them SSH access to workspaces, the REST API, personal SSH identities and signed commits.