An inbox for every one of your customers.
Verify your domain once. Then give each customer a project with its own inboxes, key, webhooks and limits.
One workspace. One project per customer.
You keep one account. Each customer gets a space of its own inside it.
Verify your domain once
Add mail.yourapp.com to one project and verify it. Every other project adds it at once, with no DNS to touch. Another workspace can't claim it.A customer in two calls
One request makes the project, attaches up to 20 domains and creates up to 50 inboxes. If one address is taken, nothing is created. One more call gives its agent a key.Walls between customers
A project key sees only its own inboxes, threads, events and webhooks. An agent's first mail to a new address waits for someone on your team, unless it's a reply to a verified sender in the same thread on an open desk.Bill them and cap them
Read each project's sent and received counts for any window up to 400 days. Set a daily send limit, so one customer can't spend your whole volume.
A customer, in two calls.
The agent's key comes back once. Usage is one more call, for your own billing.
curl -X POST https://api.drin.run/v1/projects \
-H "Authorization: Bearer $ACCOUNT_KEY" \
-H "X-Drin-Product: yourapp" \
-H 'content-type: application/json' -d '{
"name": "Customer 42",
"domains": ["mail.yourapp.com"],
"inboxes": [{ "address": "c42@mail.yourapp.com" }]
}'{
"id": "…", "slug": "customer-42", "name": "Customer 42",
"domains": [{ "domain": "mail.yourapp.com",
"status": "verified", "receivingEnabled": true }],
"inboxes": [{ "address": "c42@mail.yourapp.com", … }],
"counts": { "domains": 1, "inboxes": 1, "apiKeys": 0 },
"limits": { "sendPerDay": null }
}# The customer's agent gets its own key, inside that project
curl -X POST https://api.drin.run/v1/agents \
-H "Authorization: Bearer $ACCOUNT_KEY" \
-H "X-Drin-Product: yourapp" \
-H 'content-type: application/json' \
-d '{ "name": "Agent, customer 42", "project": "customer-42", "preset": "send_read" }'
# → { "agent": { … }, "apiKey": { "key": "drin_…", "preset": "send_read", … } }
# Your own server's sends can use createKey on POST /v1/projects instead:
# an app's key, so a receipt doesn't wait for anyone.GET /v1/projects/$PROJECT_ID/usage?from=2026-10-01&to=2026-11-01
{ "sent": 1840, "received": 312, "inboxes": 3,
"from": "2026-10-01T00:00:00.000Z",
"to": "2026-11-01T00:00:00.000Z" }Who holds which key.
Your key runs the workspace. Theirs runs one project, and it can't raise its own limit.
| What a key can do | Account-wide key (yours) | Project key (theirs) |
|---|---|---|
| Create or delete projects | Yes | No |
| See other projects | Every project | Only its own |
| Read mail | The project it names | Its own project's inboxes |
| Set the daily send limit | Yes | No |
| Make webhooks and wake targets | For the project it names | For its own project |
| Mint more keys | Within its own scopes | Within its own project and scopes |
Below full access, or from an agent's key, a new webhook or wake target waits for a person's approval. Another project's inbox, thread or key is a 404 to a project key, never a 403 that says it exists. Every paid plan holds 1,000 projects; the free plan has 3, without your own domain. Inboxes have no fee of their own.
Your first customer's inbox is one call away.
Test on the free plan. Your own domain starts on a paid plan.