Editions & Plans

This page documents edition and plan differences that are visible in the codebase. It is not a pricing page. The intent is to clarify which subsystems exist in community versus enterprise builds and which features are gated by configuration.

rstream has two engine build families. Community Edition is the public baseline engine. Enterprise Edition extends the same core with additional listeners, backends, and plan-gated controls used by managed and licensed deployments.

Community edition

Community Edition runs the core engine with the TLS listener, HTTP and TLS tunnel support, static certificate configuration, JWT authentication, and Prometheus metrics.

In this build, datagram tunnels, QUIC and DTLS listeners, HTTP/3 upstream and downstream, GeoIP policies, trusted IP policies, custom ALPNs, custom TLS ciphers, rstream Auth, challenge mode, automatic certificate management, PostgreSQL authentication, Influx metrics, package distribution, and persistent event storage are not available.

Enterprise edition

Enterprise Edition extends the community build with additional configuration sections and integrations. The configuration surface includes QUIC and DTLS listeners, ECH configuration, identity provider integration, PostgreSQL-backed auth and events, GeoIP support, package distribution, CertMagic certificate automation, and Prometheus or Influx metrics.

Plan gates are enforced by the runtime. In the current engine matrix, Pro and Enterprise projects can use private tunnels, datagram tunnels, QUIC tunnels, DTLS tunnels, HTTP/3 upstream, GeoIP policies, trusted IP policies, custom ALPNs, custom TLS ciphers, rstream Auth, and challenge mode. Basic projects have HTTP/3 downstream support when the QUIC listener is enabled, but the other advanced tunnel and policy features remain gated.

Some enterprise integrations are mutually exclusive. For example, Prometheus and Influx metrics cannot be enabled simultaneously in the same engine configuration.