Community
Free
One local Worker
- 35 Source and 30 Destination adapters
- Visual Pipeline and combined routing
- Durable queues and failure replay
- Diagnostics, metrics and management API
- No dataflow-count limit
Full dataflow capabilities, with a clear Worker licensing boundary.
Free
One local Worker
Licensed by Worker quota
Multiple Workers · Offline activation
| Capability | Community | Commercial |
|---|---|---|
| Deployment | One local Worker | Remote Workers supported |
| Processing | Full dataflow capabilities | Includes Community capabilities |
| Operations | UI, API, metrics and activity | Manage and observe multiple Workers |
| Activation | Not required | Offline file with a Worker quota |
Yes. Collection, Pipeline, fanout, routing, durable queues, diagnostics and the management API are included. Community deployment supports one local Worker.
No. Import an offline file issued by LicRegister. Signature, cluster binding, validity and quota are verified locally.
No. Each Worker owns a local durable queue. Task takeover does not replicate queues or automatically move an old node’s backlog.
Source acknowledgement confirms local durable acceptance. Downstream acknowledgement follows each protocol. Retries may duplicate records, and there is no global transaction or ordering across destinations.
FlowPort focuses on remote ingestion. Use DataKit, Vector or another collector to collect local data and forward it over a supported protocol.
FlowPort does not import Vector configuration or claim full option or data-model equivalence. Its adapters are implemented natively in Go.