editions

Self-hosted. Free to start, free to evaluate.

Both editions run from the same images. One setting on the admin container decides which you get.

Community

Apache-2.0

$0free forever

Open source, commercial use included. No caps on routes, requests, projects or seats.

1 worker · serves every project, routes and workflows

Every built-in block, custom blocks, middlewares
Routes, workflows, schedules
PostgreSQL, MySQL, MongoDB · Redis, Memcached
Redis Streams and RabbitMQ triggers
Four roles, test suites, tracing, OTLP and Loki
Kit, Docker production stack, Helm

Self-host Community

Enterprise

v1.0 early access

$0free during alpha, until 1.0

Everything in Community, plus the below. A key on your own instance, not a subscription. Free forever for non-commercial use.

no worker cap · any type, any project, autoscaling

Kafka, NATS JetStream and Amazon SQS — triggers and Send Message
Single sign-on with OIDC and SAML
30-day grace on expiry; SSO sign-in is never cut off
Key checked on admin only, stored encrypted, shown as a fingerprint

Turn on Enterprise

Workers per edition — on the Admin + Workers setup; the Kit always runs one built-in worker
Edition	Workers	What they can be
Community	1	One worker serving every project, doing route and workflow work
Non-commercial	2	Any type, for any project
Enterprise	No limit	Any type, any project; claims can autoscale, bounded by the instance node pool

Compare editions

Feature	Community	Enterprise
Routes, blocks, custom blocks and the visual editor
Workflows, schedules (cron, intervals, one-shot), batching
Redis Streams and RabbitMQ triggers and Send Message
Roles: system admin, project admin, creator, viewer
Test suites, tracing, Loki and OTLP export
AI harness (alpha) with your own model keys
Kafka, NATS JetStream and Amazon SQS — triggers and Send Message
Single sign-on — OIDC and SAML
More than one worker; autoscaling claims

Routes, blocks, custom blocks and the visual editor

Community ✓ · Enterprise ✓
Workflows, schedules (cron, intervals, one-shot), batching

Community ✓ · Enterprise ✓
Redis Streams and RabbitMQ triggers and Send Message

Community ✓ · Enterprise ✓
Roles: system admin, project admin, creator, viewer

Community ✓ · Enterprise ✓
Test suites, tracing, Loki and OTLP export

Community ✓ · Enterprise ✓
AI harness (alpha) with your own model keys

Community ✓ · Enterprise ✓
Kafka, NATS JetStream and Amazon SQS — triggers and Send Message

Enterprise only
Single sign-on — OIDC and SAML

Enterprise only
More than one worker; autoscaling claims

Enterprise only

enterprise

Turn on Enterprise today.

There's no license server before 1.0, so there's nothing to sign up for. Use NON_COMMERCIAL, or mint a self-signed evaluation key from the repo. Restart admin and the log prints “edition: enterprise (license active)”.

Personal, education or non-profit

.env

# admin (or Kit) container .env — personal, education or non-profit use
LICENSE_KEY=NON_COMMERCIAL

Every Enterprise feature, no signing, no expiry.

Evaluating for a business (pre-1.0)

shell + .env

# 1) from the Fluxify repo root: mint a self-signed key (pre-1.0 only)
bun run --cwd packages/common license:mint -- --licensee your-org --days 30

# 2) admin container .env
LICENSE_ISSUER_KEY_PATH=.license/issuer.pub
LICENSE_KEY=<the key printed by step 1>

Tests expiry, a licensee name and feature subsets. Self-signed licenses

Questions

Is there a hosted Fluxify cloud?

No. Fluxify is self-hosted only: the Kit image, the Docker production stack or the Helm chart, on your infrastructure. No hosted tier, no usage-based billing.

What does “free during alpha” mean for Enterprise?

Fluxify doesn't issue license keys before 1.0. Until then you can evaluate every Enterprise feature with a self-signed key, and personal, education and non-profit use is free with LICENSE_KEY=NON_COMMERCIAL — that one doesn't expire at 1.0.

What will Enterprise cost after 1.0?

Pricing after 1.0 isn't set yet. At 1.0, keys are issued by Fluxify and verified against a public key built into the release; the self-signed path stops applying.

Can I run Fluxify commercially for free?

Yes, on Community. Leave LICENSE_KEY unset and everything you run is Apache-2.0, commercial use included. Enterprise code (ee/ folders and *.ee.* files) needs a key for commercial use.

What happens when a license expires?

A 30-day grace period: existing connectors keep running and a banner counts down, but you can't create connectors or change SSO settings. After that Enterprise features stop and Community keeps working. SSO sign-in never stops, so admins aren't locked out.

Where does the key go?

In the admin container's .env (or the Kit's), or under Instance Settings → License. Workers learn the edition from admin and never hold the key.

Full terms: Editions · Licensing