Secrets manager

Envless sends every account emailthrough OpenEmail.

Envless keeps environment variables encrypted, versioned and in sync. Every email it sends, from a sign-in code to a security alert, goes through two calls to the OpenEmail SDK.

Visit envless.cloud
libs/openemail/SendBatchEmails.ts
for (let i = 0; i < recipients.length; i += OPENEMAIL_BATCH_LIMIT) {  const chunk = recipients.slice(i, i + OPENEMAIL_BATCH_LIMIT)  const payload: Array<EmailSend> = chunk.map((to) => ({ from, to, subject, html, text }))   const results = await OpenEmail().emails.sendBatch(payload)  sent += results?.sent ?? 0   for (const item of results?.items || []) {    if (item.status === 'error') {      Console.Error('SendBatchEmails', `${item.error.code} ${item.error.message}`)    }  }}

Release news and team alerts go out 100 recipients per call. Each person gets a separate message, and a failure is logged for that recipient alone.

36

email templates, every one sent through OpenEmail

100

recipients per batch call, each in a message of their own

Sep 2026

The month it started on OpenEmail

What runs through it

What Envless runs
on OpenEmail.

  • Sign-in codesA six-character code, valid for ten minutes, sent while the person waits on the sign-in screen.
  • Verification codesA fresh code before any of the 43 actions Envless guards with a second check.
  • Security noticesAlerts when two-factor changes, a CLI device is approved, an API key is created or rotated, or an environment is exposed.
  • Team invitationsInvitations to a workspace, with a reminder a day before one expires.
  • BillingUpgrades, renewals, plan changes, cancellations, and payments that failed or recovered.
  • Release newsA note when a new version of the Envless CLI, env package or SDK is published.

How it was built

How Envless
put it together.

  1. 01

    One client for the API

    Envless creates a single OpenEmail client from its API key and reuses it for every send.

  2. 02

    Render, then send

    Each of its 36 React Email templates becomes HTML and plain text, then goes out with emails.send.

  3. 03

    Batch the announcements

    Release news and team alerts use emails.sendBatch, 100 recipients at a time, so nobody sees anyone else's address.

  4. 04

    Opt-outs, except for security

    People can mute categories such as release news. Sign-in codes and API key security notices always arrive.

Features in use

The OpenEmail features
Envless relies on.

Email API

Send one message or a hundred per call, now or later, and retry without sending twice.

Typed SDKs

TypeScript, Python and Ruby clients, one method for every operation.

/threads?query=invoice
{ "threads": 12 }
Same mailbox, whether a person or a program is holding it.
API keys

A key per job, limited to the scopes and senders it needs, with every call logged.

Multiple domains

Point several domains at one inbox, subdomains included.

acme.comacme.devteam.acme.comhey.acme.io

Questions

Questions about
Envless and OpenEmail.

Mint a key.
Send something.

Full API, MCP and SDK access on every plan, the free one included.