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).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
RunR
Self-hosted serverless on Kubernetes and Knative
RunR is an open-source (MIT) serverless platform you install on your own Kubernetes clusters. Functions, containers and WebAssembly with scale-to-zero, versions and rollbacks, runc/gVisor/Kata sandboxes, multi-region, GPUs and MCP built in. Try it: https://demo.runr.sh
RunR is software you install, not a hosted service. The control plane comes as a Helm chart (one required value: your domain) or as a Docker Compose stack for a single host, air-gapped hosts included. Then you register any Kubernetes cluster as a region and RunR installs Knative Serving, Traefik, a registry, Redis, Prometheus and Loki there.
From then on you write a function in the browser, git push a project, or bring a container image or a Wasm module, and RunR builds it and runs it with scale-to-zero. Every code or configuration change is a version you can deploy, compare and roll back with the configuration it ran with. Projects have dev, staging and production environments, blue-green and canary rollouts with automatic rollback, and can run in several regions behind one host name.
A few things that are less common in this space: each project type of a region runs under runc, gVisor or Kata Containers; every language is a plugin (Python, Node.js, Go, PHP, PyTorch and TensorFlow come built in); GPU workers and Hugging Face model services; a built-in MCP server so agents can operate RunR within their token's permissions; and a Sandbox API for code that agents write. RBAC, SSO, an audit log, secrets that stay in the region and signed-image admission are included; multi-tenancy is an optional module.
I'd like to hear where getting a first region up took longer than it should have.
About RunR on Product Hunt
“Self-hosted serverless on Kubernetes and Knative”
RunR was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #152 on the daily leaderboard. RunR is an open-source (MIT) serverless platform you install on your own Kubernetes clusters. Functions, containers and WebAssembly with scale-to-zero, versions and rollbacks, runc/gVisor/Kata sandboxes, multi-region, GPUs and MCP built in. Try it: https://demo.runr.sh
On the analytics side, RunR competes within Open Source, Developer Tools, GitHub and Tech — topics that collectively have 1.3M followers on Product Hunt. The dashboard above tracks how RunR performed against the three products that launched closest to it on the same day.
Who hunted RunR?
RunR was hunted by Burak Faruk ŞAHİN. 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.
For a complete overview of RunR including community comment highlights and product details, visit the product overview.
Hi, I'm Burak, the developer of RunR.
RunR is software you install, not a hosted service. The control plane comes as a Helm chart (one required value: your domain) or as a Docker Compose stack for a single host, air-gapped hosts included. Then you register any Kubernetes cluster as a region and RunR installs Knative Serving, Traefik, a registry, Redis, Prometheus and Loki there.
From then on you write a function in the browser, git push a project, or bring a container image or a Wasm module, and RunR builds it and runs it with scale-to-zero. Every code or configuration change is a version you can deploy, compare and roll back with the configuration it ran with. Projects have dev, staging and production environments, blue-green and canary rollouts with automatic rollback, and can run in several regions behind one host name.
A few things that are less common in this space: each project type of a region runs under runc, gVisor or Kata Containers; every language is a plugin (Python, Node.js, Go, PHP, PyTorch and TensorFlow come built in); GPU workers and Hugging Face model services; a built-in MCP server so agents can operate RunR within their token's permissions; and a Sandbox API for code that agents write. RBAC, SSO, an audit log, secrets that stay in the region and signed-image admission are included; multi-tenancy is an optional module.
Try it without installing anything: https://demo.runr.sh (credentials are on the sign-in page). Docs: https://runr.sh/docs/ - code: https://github.com/BRF-Tech/runr
I'd like to hear where getting a first region up took longer than it should have.