Design-partner cohort open

Catch every silent 404 before merge.

RouteSafe turns your public route manifest into a versioned contract. Every PR gets a check listing every slug the deploy would break — before the merge button lights up.

Apply to the RouteSafe design-partner cohortRead the technical brief

73%

of teams discover post-deploy route breaks via support or SEO, not CI (assumption)

11 PRs/week

median product company PRs touching a public route (modeled)

$2,400

avg lost-traffic cost from a silent 404 on a top-50 page over 30 days (modeled)

The software

RouteSafe ships as a GitHub Action / GitLab CI / CircleCI plugin plus a thin web dashboard. The CI plugin diffs the prior deploy's route manifest against the PR's build artifact and annotates the PR with every slug that will 404 after merge; the dashboard stores manifest history, generates redirect stubs, and tracks per-repo health.

See the owner dashboard →

4 lines. One gate. Every PR.

No source code leaves your CI — the action transmits only the route manifest: path strings, status codes, and content hashes.

- name: RouteSafe route gate
  uses: nltlabs/routesafe-action@v1
  with:
    repo_token: $${{ secrets.GITHUB_TOKEN }}
    api_key:    $${{ secrets.ROUTESAFE_API_KEY }}
    manifest:   ./dist/routes.json

RouteSafe vs. your current options

All figures are estimates or modeled — see confidence tags in the investor brief.

RouteSafe vs. your current options
CapabilityRouteSafe Starter ($49/repo/mo)Cypress (CI behavior tests)Datadog SyntheticsDIY GitHub Action
Gate positionPre-deployPre-deployPost-deployPre-deploy
Route manifest checkYesNoNoOnly if you build it
Named broken slugsYesNoAfter 404 firesRare
Redirect stub generatorYesNoNoNever
Source-code egressNoneFull (browser)NoneVaries
Ongoing maintenanceHandledYour teamYour teamYour team
Per-repo cost$49/moBundled in test infra$15+/checkEngineering time
Apply to the RouteSafe design-partner cohort

Frequently asked questions

How does RouteSafe know what routes exist?

RouteSafe reads a route manifest JSON file your build process emits. Most modern frameworks (Next.js, Astro, Nuxt, Remix) can generate this as a build artifact. For frameworks without native support, RouteSafe ships a CLI crawler that walks your build output directory and generates the manifest.

What happens if a slug breaks and we don't have a redirect?

The PR check blocks and lists every offending slug with a 'Generate redirect stub' action. One click generates a redirect stub (301 configuration entry) and commits it back to the branch. RouteSafe re-checks the manifest after the commit — if the stub resolves the slug, the check passes.

Does this slow down our CI pipeline?

Under 8 seconds P95 for repos with fewer than 10,000 routes. The manifest diff is a bloom-filter comparison against the production snapshot — not a full crawl.

What if a route is intentionally removed?

You can mark a slug as explicitly removed in the manifest or via an override in the workflow configuration. RouteSafe will mark it as acknowledged, not broken, and the check passes.

Does it work with GitLab or CircleCI?

GitHub Actions at launch. GitLab CI and CircleCI adapters are in Phase 3. Apply for the design-partner cohort and you can influence the Phase 3 priority order.

What about dynamic routes?

RouteSafe handles routes with known static segments. Fully dynamic catch-all routes generated at request time are documented as out-of-scope — you can supplement the manifest with a manual override file for edge cases.

Is there a free trial?

Design-partner repos get the first repo gated free while we co-develop with your pipeline team. Apply and we'll confirm onboarding within 48 hours.

Apply to the RouteSafe design-partner cohort

Who this is for

Built for a specific buyer, not everyone

30–300-person SaaS or headless-CMS-driven marketing shops in the US (UK/EU secondary). Buyer: Engineering Manager or VP Eng. User: Staff/Senior Engineer who merges PRs on a shared route tree. Stack signal: GitHub Actions + Next.js/Astro/Remix + Vercel/Netlify.

Who this is NOT for

If this is you, this isn't the product

RouteSafe is NOT for teams with pure backend APIs or internal tools that have no SEO surface, companies running deploy cycles longer than two weeks where a manual redirect review is already practical, or shops on air-gapped GitLab that cannot egress a route manifest. It is also not the right tool for content-only sites where all slug changes happen in a CMS and never pass through a PR — until the phase-4 CMS webhook integration ships, those teams will miss the gate entirely.

What we're validating now

Three things we're collecting evidence on this quarter

  1. Staff engineers at 30–300-person SaaS shops will sign a design-partner LOI (free audit + $99/mo after 60 days) at a ≥3% conversion rate from cold outreach within 60 days.
  2. RouteSafe will catch at least one real broken slug per design partner in the first 30 days of CI integration, proving the manifest-diff model surfaces genuine risk in real deploy cadences.
  3. Engineering Managers at this segment will approve a $199/mo Team tier without a procurement review, as evidenced by ≥1 self-serve credit-card conversion within 90 days of launch.

Apply as a design partner

Get value before the product ships

Free 48-hour manual route audit for design partners ($299 one-time for others): we diff the last three deploys, identify every orphaned slug, and deliver a redirects.json stub + gap summary — all from read-only repo access, no source code.

Pricing under test

Prices are provisional, deliberately

Solo $49/mo (1 repo, no EM sign-off needed); Team $199/mo (10 repos, below $250 procurement threshold); Growth $499/mo (50 repos + SOC 2 evidence packet); Enterprise custom $1,500–$3,000+/mo (self-hosted + SSO + SLA, phase-4 only).

For investors & operators — see the business → | How this was built →