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
Shoehorn
Backstage without the platform team
Where Backstage needs a platform team, one person runs Shoehorn. It's an Intelligent Developer Platform that auto-discovers your services from Kubernetes (via our k8s-agent, YAML manifests still work), GitHub, and your IdP. Tenant isolation by RLS. Forge, our scaffolding engine, spins up new services from reusable templates. Fast fuzzy search across everything. Manage it via UI, CLI, or Terraform same API behind all three. The IDP for the 95%.
We're a tiny team launching Shoehorn after a year of building it.
We built it because we spent years working with Backstage, It's a great product, but it needs a dedicated platform team to run. Most companies don't have one, so the portal becomes a thing you maintain instead of a tool your developers use.
So we built the opposite: opinionated defaults, fewer knobs, working catalog inside an afternoon. Small enough that one person can run it.
Who it's for
The 95% of teams who want a developer portal but don't have a dedicated platform engineer to babysit one. If you've ever bounced off Backstage's setup, this is for you.
What's in the box:
- 🔎 Service catalog
That auto-discovers from Kubernetes, GitHub, and your IdP. A small push-based agent (~50m CPU, <150 MB) runs in each cluster. New services show up within minutes, no manifests to write (unless you want too).
- 🏗️ Forge
A scaffolding engine. Spin up new services from templates via UI or `shoehorn forge run`.
- 🔐 Multi-tenant at the database layer
Postgres row-level security
- 🛠️ UI, CLI, and Terraform same API behind all three. The CLI is one Go binary (`brew install shoehorn`). The Terraform provider lets you declare entities, teams, scorecards, and Forge molds as code.
- 🤖 Built-in MCP server.
Your IDE agent (Claude, Cursor, whatever) can search the catalog and answer "who owns this service?" but the index lives in your cluster. The AI provider sees the question and answer, never the data.
- 🎨 A UI we're proud of:
Judge it yourself in the demo.
The install story
One `terraform apply` from a fresh kubeconfig to a running, populated, scored, owned developer platform. The module generates secrets, installs the helm chart, wires up your OIDC provider: Okta, Zitadel (more coming), deploys the K8s agent, and the catalog starts populating from your cluster.
Shoehorn was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #125 on the daily leaderboard. Where Backstage needs a platform team, one person runs Shoehorn. It's an Intelligent Developer Platform that auto-discovers your services from Kubernetes (via our k8s-agent, YAML manifests still work), GitHub, and your IdP. Tenant isolation by RLS. Forge, our scaffolding engine, spins up new services from reusable templates. Fast fuzzy search across everything. Manage it via UI, CLI, or Terraform same API behind all three. The IDP for the 95%.
On the analytics side, Shoehorn competes within Productivity, User Experience, Developer Tools and GitHub — topics that collectively have 1.6M followers on Product Hunt. The dashboard above tracks how Shoehorn performed against the three products that launched closest to it on the same day.
Who hunted Shoehorn?
Shoehorn was hunted by Anders. 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 Shoehorn including community comment highlights and product details, visit the product overview.
Anders
Hey Product Hunt 👋
We're a tiny team launching Shoehorn after a year of building it.
We built it because we spent years working with Backstage, It's a great product, but it needs a dedicated platform team to run. Most companies don't have one, so the portal becomes a thing you maintain instead of a tool your developers use.
So we built the opposite: opinionated defaults, fewer knobs, working catalog inside an afternoon. Small enough that one person can run it.
Who it's for
The 95% of teams who want a developer portal but don't have a dedicated platform engineer to babysit one. If you've ever bounced off Backstage's setup, this is for you.
What's in the box:
- 🔎 Service catalog
That auto-discovers from Kubernetes, GitHub, and your IdP. A small push-based agent (~50m CPU, <150 MB) runs in each cluster. New services show up within minutes, no manifests to write (unless you want too).
- 🏗️ Forge
A scaffolding engine. Spin up new services from templates via UI or `shoehorn forge run`.
- 🔐 Multi-tenant at the database layer
Postgres row-level security
- 🛠️ UI, CLI, and Terraform same API behind all three. The CLI is one Go binary (`brew install shoehorn`). The Terraform provider lets you declare entities, teams, scorecards, and Forge molds as code.
- 🤖 Built-in MCP server.
Your IDE agent (Claude, Cursor, whatever) can search the catalog and answer "who owns this service?" but the index lives in your cluster. The AI provider sees the question and answer, never the data.
- 🎨 A UI we're proud of:
Judge it yourself in the demo.
The install story
One `terraform apply` from a fresh kubeconfig to a running, populated, scored, owned developer platform. The module generates secrets, installs the helm chart, wires up your OIDC provider: Okta, Zitadel (more coming), deploys the K8s agent, and the catalog starts populating from your cluster.
👉 Demo: https://demo.shoehorn.dev
👉 Docs: https://docs.shoehorn.dev
👉 Repos: https://github.com/shoehorn-dev
— Anders & team