License and service boundaries

May I use Free in production?

Yes. Every tier, including Free, permits real production use, including commercial use. The BSL 1.1 Additional Use Grant has no use-case, node/device/connection/message count or deployment-environment restrictions on production use. Read the exact license text.

The license remains BSL 1.1 with its stated change date and Apache 2.0 change license. Third-party components retain their own licenses.

What changes by tier?

The packaged capabilities, artifact access, updates and operating service commitments differ. Free runs a useful memory-backed MQTT node with selected webhook/custom delivery. Pro adds durable state; Max adds integration/device profiles; Enterprise adds governed standby operations and service commitments. See Tiers and the terms at checkout.

Permission to use the software creates no entitlement to private paid artifacts, updates, paid support or an SLA. Those follow the applicable product/service agreement. Prices and billing semantics remain as shown at checkout.

What does the grant guarantee about my workload?

Technical behavior follows the installed version and selected configuration. Free’s memory state is lost on restart. Durable state needs the configured PostgreSQL profile and verified recovery. Protocol/profile and provider limits remain explicit; production permission supplies no new runtime feature, throughput result or release-qualification evidence.

Use the operating skills to check the actual deployment and keep support/evidence within the scope it proves.