Rivetport: keep an old API working on a new backend

My own B2B product. Teams upload the old and new OpenAPI specs, pick a GET operation from each, and map fields between them. An AI assistant can propose mappings, but every bridge is reviewed, tested against expected responses, and approved before it is published. Published bridges are deterministic, with no model in the request path, and include rollback, pause, and key rotation. I designed and built the whole product: the marketing site, docs, workspace app, plan limits, and the edge runtime. Stack: Next.js, TypeScript, shadcn/ui, Clerk, Convex, Cloudflare Durable Objects, Vercel.