Shoehorn - Intelligent Platform for Engineering

2 min read Original article ↗

Launching

-- Days

-- Hours

-- Min

-- Sec

The Intelligent
Developer Platform.

Opinionated and ready to run. Point it at Github, cloud vendors and your kubernetes clusters; 15 minutes later you've got a catalog, search, and docs.

Built-in i18n Supports en, sv, fr, es, de, fi, nl

Why Shoehorn?

Shoehorn runs as part of your stack. No portal team needed just to keep it alive.

Days of setup before you see anything useful

Point it at your repos. 15 minutes.

Portal maintenance becomes an ongoing side job

Just another service in your stack

Common platform needs still require extra assembly

Catalog, search, docs, and governance ship together

Adoption often depends on how much rework is required

Backstage compatible. Your catalog-info.yaml files just work.

How It Works

Three steps, and you're running.

1

Connect Your Stack

Point Shoehorn at your GitHub org, clusters, and repos. About 15 minutes of setup, then it runs like any other service you operate.

Shoehorn crawls your repos directly. For clusters, drop in our k8s-agent and it pushes workloads to Shoehorn, with no inbound access required. You end up with what's running, who owns it, what it depends on, and where the docs live, without writing any of it.

Search across everything, see what depends on what, and know who to page when something breaks, without first asking around in Slack.

The questions your team asks every Tuesday

The three that come up most in Slack.

"Who owns this service?"

It's 2am, something's down, and nobody knows who owns the payment service.

Auto-discovered service catalog with team ownership, dependencies, and contact info

Instant search finds services, APIs, and owners in under 200ms

"What breaks if I change this?"

You want to deprecate an API endpoint. How many things call it?

Impact analysis at configurable depth (1–5 levels)

Dependency graph shows blast radius before you make changes

"How do I scaffold consistently?"

Every new service starts with copy-pasting. Someone always forgets the CI config.

Forge molds: reusable templates to scaffold repos and provision infra

Approval gates ensure the right people sign off first

Built for any team

Terraform, CLI, REST API, or the UI. Pick whatever fits your workflow.

Version-controlled and repeatable. Pick your interface.