Connectivity for services behind private networks
rstream publishes local services and privately connects applications, operators, and machines without opening inbound ports. Agents connect out from the private environment, while the edge handles identity, access policy, routing, and connection logs.
One model for public and private access
A service can be exposed on a public endpoint or remain private and be dialed by an authenticated CLI or SDK client. In both cases, the origin keeps an outbound-only connection and policy is evaluated before traffic reaches the private side.
This shared model avoids rebuilding identity, routing, and observability each time a workload moves from local development to internal access or production.
A multi-protocol connectivity runtime
rstream carries HTTP, WebSocket, WebTransport, TCP, TLS, QUIC, DTLS, and private stream or datagram workloads through one runtime. WebTTY extends the same connectivity model to remote terminal access, while APIs, SDKs, MCP tools, and Agent Skills make it usable from applications and automation.
One operating model from development to production
A developer can start with one CLI command. Platform teams can then move tunnel definitions into YAML, Docker labels, or Kubernetes resources, add scoped credentials and access policy, and inspect connections through logs, metrics, events, and webhooks without changing the basic network path.
About the founder
Founded by @uartnet
software engineer
rstream was founded by @uartnet, a software engineer focused on networking, embedded systems, distributed infrastructure, and automation. The product grew from working with environments where access, transport, identity, and observability were handled by separate tools despite belonging to the same operational problem.
rstream is developed in Europe with feedback from developers, operators, customers, and security reviewers. Product claims and edition boundaries are documented so teams can evaluate what exists today without relying on roadmap promises.