Zero-config flat-fee API forwarding and webhook relay

Overview

A zero-config, flat-fee API forwarding and webhook relay for indie developers and small SaaS teams: point it at a target URL, get a stable public endpoint, and let Stripe, Shopify, Telegram or any third-party service reach your local or internal server.

Pain Point

Local dev machines have no public address, and cross-origin calls to restricted APIs need a proxy. Cloudflare Workers requires code and route config with metered billing that is hard to predict; ngrok's free URLs change on every restart; webhook.site is a debug toy, not production infrastructure. Developers want one form, one stable domain, and a bill that does not surprise them.

Target User

Indie developers, 1-5 person SaaS teams, and freelance integration engineers currently wiring up payment callbacks, ecommerce webhooks or bot message pushes.

Market Opportunity

The signal comes from CurlShip's minimal API submission design, which shows developers value low-configuration interfaces, while the pricing-unpredictability complaint about Cloudflare Workers remains unsolved. Flat pricing is a clean positioning wedge.

Monetization

Free: fixed subdomain, 1,000 relays/month, 24h logs. Pro $9-19/mo: custom domain, 100k relays, 7-day logs, retries. Team $49/mo: multi-seat and Slack/email alerts. Pricing is inferred from comparable developer tools; needs validation.

Technical Complexity

Medium. The hard parts are reliability, not features: no dropped requests, idempotent retries, log storage cost, multi-tenant isolation, automatic HTTPS for custom domains, and abuse prevention so the relay is not used as an open anonymous proxy.

Competition

• ngrok: the best-known local tunnel tool; random free URLs and relatively high pricing.
• Cloudflare Workers: maximally flexible but code-heavy and metered, so costs are hard to forecast.
• Hookdeck / Pipedream: webhook relay and workflow platforms; heavy, team-oriented, overkill for solo devs.
• webhook.site: great for debugging, not production-grade. Entry barrier: medium. Engineering is modest; the real moat is operational trust (no lost requests) plus developer word-of-mouth and SEO content.

GTM Strategy

• Primary channel: long-tail SEO plus developer communities (inferred).
• Cold-start tactic: Show HN launch paired with Product Hunt, leading with a free fixed domain and no credit card required.
• Content leverage: "How to test Stripe webhooks locally", "Cloudflare Workers vs a webhook relay", "n8n webhook forwarding tutorial", plus a free browser-based webhook inspector as a lead magnet.

Execution Plan

• MVP core features: (1) create a fixed URL that forwards requests verbatim; (2) request log with one-click replay; (3) automatic retries.
• What NOT to build: visual workflow orchestration, API schema transformation, multi-region failover, team permissions.
• Tech stack suggestion: Cloudflare Workers + Durable Objects (or Fly.io + Hono) for the relay, Supabase Postgres for logs, Next.js on Vercel for the dashboard, Stripe for billing, Cloudflare for SaaS for custom domains.
• Estimated time to launch: medium, roughly 3-5 weeks for a single-purpose product.