Expand Workers. Keep activation offline.

Start with Community

Community supports one local Worker with no dataflow-count limit. Existing collection, processing, routing and management capabilities remain available. Remote registration and task assignment require a commercial license.

Offline activation

Copy the cluster ID from System settings → Edition and license and ask the issuer for a cluster-bound LicRegister offline file. Import and preview it, review validity, Worker quota and affected nodes, then activate.

Activation does not contact a remote server. Release builds pin trusted public keys. A license does not replace Source tokens, node authentication, TLS or the administrator password.

Join and schedule

With a valid license, generate a join credential in Workers and deploy nodes. Quota includes local, offline and draining nodes. Stopping a container does not release a slot; drain and remove it.

Push, shared messaging and exclusive polling have different placement rules. Takeover follows leases and stop confirmation; it is not a promise of uninterrupted ingestion. Old backlog stays on its original Worker.

Expiry and runtime boundaries

Expired or insufficient licensing restricts new remote ingestion while persisted data keeps processing and delivering. Data is not automatically deleted or migrated. Remote input stops when its control lease expires after a manager disconnect.

Use matching manager and Worker builds and reliable server time. Offline signatures and validity depend on the server clock.