This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Publish services to the internet or reach them privately through outbound-only tunnels, with identity, access policies, and connection logs managed at the edge. Use rstream tunnels for local webhooks, private databases and homelabs, LLM and GPU meshes, real-time video, or remote fleet operations with rstream WebTTY. Control these workflows through the CLI, SDKs, APIs, Docker, and Kubernetes.
Today is an important moment for me. rstream is the result of several years of work, and I deliberately waited before launching it here,
“Launch early” is common advice, and often good advice. But rstream carries real traffic and sits on a security boundary. I wanted to trust it with my own traffic before asking anyone else to trust it with theirs. For several months, rstream has carried both my own traffic and partners’ production workloads, and I know it is mature and ready for wider use,
I built rstream so the same connectivity model can follow a service from a laptop into production,
You can start with a simple command:
rstream forward 8080
That gives a local service a public HTTPS endpoint. The same tunnel can be configured in YAML, run in Docker or Kubernetes, or embedded through APIs and SDKs. A service can also remain private, reachable only by authenticated users, applications, or agents under explicit credentials and policies, including through MCP and Agent Skills. Connections originate inside the private environment, so no inbound port is opened and access remains limited to that service,
rstream WebTTY extends the same tunnels from temporary remote terminals to registered fleets, with recordings, live collaboration, and optional end-to-end encryption,
Something important for me: all rstream client code that runs on your machines is open source and inspectable,
Much of the work went into protocol correctness, security, performance, connection lifecycle, and observability. Identity, mTLS, access policies, and connection logs are enforced at the edge,
At launch, rstream runs on a global edge network spanning four regions,
ngrok opened this category and remains an excellent product. As it has evolved into a powerful programmable ingress and API gateway, I took rstream in another direction. Public exposure, private dialing, non-HTTP and real-time traffic, WebTTY, and application-owned connectivity are all first-class parts of the same runtime,
Basic is free. Pro is a flat $49 per project during launch, including 50 simultaneous tunnels and 200 GB, and early users keep that price forever. It remains predictable as usage grows. Enterprise runs on dedicated rstream infrastructure, with unlimited tunnels and bandwidth under contract,
If you try rstream, I would genuinely value your feedback on what you connected, where it got in your way, and what you would need for your application,
Thank you for taking the time to look at something that has mattered to me for a long time,
rstream tunnels was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #30 on the daily leaderboard. Publish services to the internet or reach them privately through outbound-only tunnels, with identity, access policies, and connection logs managed at the edge. Use rstream tunnels for local webhooks, private databases and homelabs, LLM and GPU meshes, real-time video, or remote fleet operations with rstream WebTTY. Control these workflows through the CLI, SDKs, APIs, Docker, and Kubernetes.
rstream tunnels was featured in API (98.6k followers), Developer Tools (518.7k followers) and Security (2.9k followers) on Product Hunt. Together, these topics include over 99.6k products, making this a competitive space to launch in.
Who hunted rstream tunnels?
rstream tunnels was hunted by @uartnet. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how rstream tunnels stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
@uartnet
Hello Product Hunt 👋
Today is an important moment for me. rstream is the result of several years of work, and I deliberately waited before launching it here,
“Launch early” is common advice, and often good advice. But rstream carries real traffic and sits on a security boundary. I wanted to trust it with my own traffic before asking anyone else to trust it with theirs. For several months, rstream has carried both my own traffic and partners’ production workloads, and I know it is mature and ready for wider use,
I built rstream so the same connectivity model can follow a service from a laptop into production,
You can start with a simple command:
rstream forward 8080
That gives a local service a public HTTPS endpoint. The same tunnel can be configured in YAML, run in Docker or Kubernetes, or embedded through APIs and SDKs. A service can also remain private, reachable only by authenticated users, applications, or agents under explicit credentials and policies, including through MCP and Agent Skills. Connections originate inside the private environment, so no inbound port is opened and access remains limited to that service,
rstream WebTTY extends the same tunnels from temporary remote terminals to registered fleets, with recordings, live collaboration, and optional end-to-end encryption,
Something important for me: all rstream client code that runs on your machines is open source and inspectable,
Much of the work went into protocol correctness, security, performance, connection lifecycle, and observability. Identity, mTLS, access policies, and connection logs are enforced at the edge,
At launch, rstream runs on a global edge network spanning four regions,
ngrok opened this category and remains an excellent product. As it has evolved into a powerful programmable ingress and API gateway, I took rstream in another direction. Public exposure, private dialing, non-HTTP and real-time traffic, WebTTY, and application-owned connectivity are all first-class parts of the same runtime,
Basic is free. Pro is a flat $49 per project during launch, including 50 simultaneous tunnels and 200 GB, and early users keep that price forever. It remains predictable as usage grows. Enterprise runs on dedicated rstream infrastructure, with unlimited tunnels and bandwidth under contract,
If you try rstream, I would genuinely value your feedback on what you connected, where it got in your way, and what you would need for your application,
Thank you for taking the time to look at something that has mattered to me for a long time,
Regards / uartnet