About Anonymily
Anonymily started as a frustration fix — too many hours lost to tunnels that quit, endpoints that expired, and payloads that vanished before they could be inspected. The goal was simple: make the whole loop from capture to fix fast, stable, and local.
Every developer who integrates webhooks hits the same wall: you need a public URL during local development. Tunnels work — until they don't. They restart, they expire, they lose events when your server is down for 30 seconds, and every tool swap means re-pasting a URL into five provider dashboards.
Beyond connectivity, the debugging experience is broken. When a webhook silently fails you get nothing — no captured payload, no clear error, no way to reproduce it without either firing a real event (which might charge a real user) or constructing a fake one by hand.
Anonymily flips the model. The endpoint is permanent— it captures every request even when your server is offline, stores the full exchange, and lets you replay it locally when you're ready. The CLI subscribes to your endpoint over SSE and proxies requests 1:1 — method, headers, body intact. Signature verification is automatic. Replay re-signs with your stored secret.
The AI layer came after the foundation was solid. Diagnosis reads the actual captured data — not a generic prompt — and produces a specific explanation. Handler generation is typed, correct, and based on the payload you actually received, not a template.
Design Principles
No signup, no config file, no cloud account setup. Run one npx command and a stable webhook endpoint is yours. The value should be obvious in under 60 seconds.
HMAC signature verification, raw-body preservation, per-provider signing — handled automatically. You should never have to guess whether your handler is receiving a genuine event.
Any HTTP webhook — Stripe, GitHub, Shopify, Razorpay, Twilio, SendGrid, or a homegrown service. No provider-specific setup; just point and capture.
Reproducing a bug shouldn't require asking a user to place another order. One-click replay re-sends the exact captured payload, re-signed, to your local server.
Developers live in terminals. The CLI is the primary interface; the dashboard is the visual layer when you need to inspect or share. Both are first-class.
AI diagnosis reads the actual captured exchange — signature result, response status, error body — and produces a specific fix, not a generic checklist. Handler generation is typed and correct.
Anonymily is built and maintained by Mahesh Srinivasan, a developer based in India. It's a solo project — designed, coded, operated, and supported by one person who uses it every day.
That's not a disclaimer — it's intentional. Small surface area means faster decisions, less abstraction, and tooling built for how developers actually work rather than what looks good in a feature matrix.
All infrastructure runs on anonymily.com. Payments are handled by Razorpay. Data stays encrypted at rest and in transit — see the Privacy Policy for the full picture.
Frontend
Next.js 15 · Tailwind CSS · TypeScript
Backend / API
Next.js Route Handlers · Supabase (Postgres + Auth)
Real-time
Server-Sent Events (SSE)
Billing
Razorpay Subscriptions
AI features
Anthropic Claude (API)
CLI
Node.js · published on npm as @anonymilyhq/cli
Hosting
Vercel (web) · anonymily.com (API edge)
MCP Server
Open source · inspect & replay from any AI IDE
Found a bug? Have an integration request? Just want to say the product saved you an afternoon? Reach out — I read everything.
One command. No account required. A permanent endpoint in under 10 seconds.