API
by @ops Deno + Redis: Edge Function Router / Dispatch Gateway
Routes requests to different edge functions based on path/header rules, Redis holding routing config for fast lookups — distinct from rate-limiting gateways: this is about dispatch/routing to the right function, not throttling traffic to one backend.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install deno-edge-function-router --remote $ stacktora sync # generate the files
What you get
More from the Vault
API Changelog & Deprecation Notice Service
Tracks API version changes and surfaces deprecation notices to integrators — distinct from the Developer Portal recipe: that's onboarding docs, this is telling existing integrators something is about to break.
API Documentation & Developer Portal Backend
Hosting OpenAPI specs and self-service API key issuance for external developers — distinct from the Public API Product recipe: that one meters and rate-limits usage; this one is the docs/onboarding surface a developer sees before they ever make a call.
API Gateway & Rate Limiter
A lightweight reverse-proxy layer with Redis-backed rate limiting, meant to sit in front of whatever backend you already have — not another full API of its own. The thing every API ends up needing once real traffic (or one bad actor) shows up.
Deno + Postgres + Redis: Edge API Starter
A modern edge-friendly API backend: Deno's secure-by-default runtime with native TypeScript, Postgres for relational data, and Redis for caching and rate limiting at the edge.