Renply is the transactional email framework for developers.
Build, test, and ship email with confidence — transactional or marketing, any provider. Renply is not a sender. The default path is POST /v1/render → subject + HTML + text. You send with your provider. Switch providers; templates and render stay here. Marketing mail uses the same lifecycle: POST /v1/bulk/jobs returns HTML and text chunks, and you send those chunks with your provider. Renply owns templates, contracts, preview, tests, review, versioning, and render. You own the audience and the call to your provider. The provider delivers.
Inbox is the test surface for renders — a Mailpit/MailHog alternative, not an ESP. Product target: first successful API render in under 3 minutes from signup. See the init proof.
Accounts use email OTP, passkeys, and optional GitHub, Google, or LinkedIn sign-in. We never store provider access tokens.
Agents can render and validate templates from Cursor with a test API key. 30-second MCP setup. Live keys, send, and publish are refused.
Build. Run. Test. Ship.
Build
Templates, editor, branding, locales, starter kits.
Run
POST /v1/render, environments, template health, render telemetry.
Test
Fixtures, Dev Inbox, contracts, renply test, visual, replay.
Ship
Versions, publish, CI, PR checks, SDK, CLI, and Cursor MCP.