Self-Hosted
Run the rstream engine in private infrastructure.
Self-hosted deployments run the rstream engine in private infrastructure. This is useful when traffic entrypoints must be controlled directly, when a deployment must operate without the hosted control plane, or when compliance requirements prevent the use of a hosted service.
The community edition engine binary is rstream-engine-ce. Enterprise builds extend the configuration surface with additional listeners and services.
This section documents the deployment shape, the configuration schema, and the operational interfaces exposed by the engine. It is intentionally focused on the engine data plane; hosted account, workspace, billing, and managed credential flows remain part of the hosted platform unless the selected enterprise deployment provides an equivalent integration.
Scope
Self-hosted engines act as a data plane entrypoint. Projects, credentials, and other control plane features depend on the hosted platform unless explicitly implemented in the chosen engine edition.
Related pages
Deployment covers runtime prerequisites and listener exposure. Configuration covers the engine configuration file. Operations covers health checks, metrics, and event streams.