Build. Run. Test. Ship. Any provider.

Proof

• POST /v1/render returns subject, HTML, and text. You send with your provider.
• POST /v1/bulk/jobs returns HTML and text chunks. 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.

Objections

• Renply is not a sender. You send with your provider.
• Renply does not store your contacts or run campaigns.
• Visual comparison and send adapters are not claimed here.

Build

Templates, brand, locales, and the contract the payload must match.

Run

POST /v1/render returns subject, HTML, and text. You send with your provider.

Test

Fixtures, renply test, Dev Inbox, and replay. The inbox is a test surface, not an ESP.

Ship

Version, review, and publish. CI checks the render before the deploy.

Marketing artifacts

POST /v1/bulk/jobs returns HTML and text chunks. You send those chunks with your provider.

renply init

Select transactional flows. This proof does not create an account or call the CLI.

The sender secret is a hidden prompt. It is never a flag and never written to renply.yaml. Renply is not a sender.

After init

• Test

  renply test and renply validate are offline and must not set RENPLY_API_KEY. The workflow init writes has contents: read and runs on pull requests.

• Provider switch

  Switching adapters keeps templates, fixtures, and tests. You still call the provider.

• Inbox

  renply dev listens on http://127.0.0.1:8025 and does not accept SMTP. The hosted inbox is the test environment.

• Doctor

  renply doctor checks this directory. It does not send.