Mail for software that handles other people's money.

Your own domain. Mailboxes made from code. Sending and reading over HTTPS. Every message and attachment sealed at rest with a key only your firm holds. No inbox to babysit - unless you want one.

Open a lockbox   Read the API
First production customer: The Arena, which has no mail code of its own.
Settlement statement - Harrison v. ColeAttached: the signed CSA and the wire instructions. Please confirm receipt by Friday.

- Vera, JBI
L
at restplain textunsealed
Tap the envelope to seal it with the firm's key.

What a lockbox is

Three things most mail services get backwards.

01

Sealed, not just transported

TLS protects mail in flight. Lockbox also seals it at rest - every message, every attachment - with a key derived from your firm's secret. Our database holds ciphertext. Our staff can't read your mail.

02

An API before a UI

Create a mailbox with one request. Send with one. Read with one. The dashboard exists; software doesn't need it. Keys are hashed; revoke one and it stops that second.

03

DNS you don't have to guess at

MX, SPF, DKIM, DMARC: we check your domain and tell you exactly which record is wrong, and what to paste. Deliverability isn't luck.

Send mail in four lines

Every call is JSON. Every answer says ok or why not. Attachments go in as base64 and come back decrypted for that one request.

Every endpoint, with curl
# a mailbox, then a message
curl -X POST https://lockbox.pickmeos.com/api/v1/mailboxes -H "X-Api-Key: lb_…" \
  -d '{"address":"invites@yourfirm.com","name":"Invites"}'

curl -X POST https://lockbox.pickmeos.com/api/v1/send -H "X-Api-Key: lb_…" \
  -d '{"from":"invites@yourfirm.com","to":["sam@acme.com"],
       "subject":"Your invitation","text":"…"}'
# → {"ok": true, "id": 4812}

Built for the firm that can't afford a leak.

A workspace takes two minutes. Your domain takes the records we hand you.

Open a lockbox