Renply

Transactional first. Marketing uses the same lifecycle.

Renply owns templates, contracts, preview, tests, review, versioning, and render. You own the audience and the call to your provider. The provider delivers.

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.

Objections

  • Renply does not store your contacts or run campaigns.
  • Renply is not a sender. You send with your provider.
  • Renply does not upload audiences, segment them, schedule sends, or own deliverability.

Application email

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

Newsletter template

Edit, fixture, preview, review, version. POST /v1/bulk/jobs returns HTML and text chunks. You send those chunks with your provider.

Product announcement

Same review path as a newsletter. POST /v1/bulk/jobs returns HTML and text chunks. You send those chunks with your provider.

Promotion or event

The template and the contract live here. POST /v1/bulk/jobs returns HTML and text chunks. You send those chunks with your provider.

Re-engagement template

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

Engineering and Marketing review

Both sides review the version. CI checks the contract before publish.

Multi-language

Locales stay on the template. Each locale renders to chunks you send.

Provider switch

Switch providers; templates, tests, and render stay in Renply.

Pick the workflow, then start free or read how the product fits.

Start freeSee how it works