Authorization notice. Sentio is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Credentials. The admin key has wildcard scope and platform:admin, which reaches every tenant, so store replacement keys in a secret manager.
Who it is forA platform team running an agentic product or selling email as a feature, where each customer needs its own domains and inboxes.
The problemSeparate email systems per customer are costly to run, and shared ones risk mixing sending reputation and data.
The outcomeEach customer has its own tenant with isolated domains, mailboxes, API keys, rate limits and suppression lists on one deployment.
What you need first
- Docker Engine 24+ with the Compose plugin, about 4 GB RAM and 8 GB disk, or a Linux host with PostgreSQL 18+, Redis or Valkey, NATS with JetStream, and S3-compatible storage
- A terminal and curl
- Rotation of the bootstrap admin API key before the host is reachable by anyone else
Steps
- Run
docker compose up -din the cloned Sentio directory. - Rotate the bootstrap admin key by minting a replacement with
POST /v1/tenants/{id}/api-keysas the README describes. - Delete the bootstrap key once the replacement works, using
DELETE /v1/tenants/{id}/api-keys/{key-id}. (inferred, check the README) - List existing tenants with
curl -H "Authorization: Bearer <admin-key>" localhost:8080/v1/tenants. (inferred, check the README) - Create one tenant per customer and mint a scoped API key for each, following the API reference at /openapi.json. (inferred, check the README)
Prompt for your agent
Using the truespar/sentio repo running on localhost:8080, rotate the bootstrap admin key and create a tenant for <customer-name> with its own API key. Report the new tenant ID and confirm that GET /v1/tenants lists it. Verify that the bootstrap key no longer authenticates.
Caveat. Tenant creation calls shown in the README are limited to listing tenants and minting API keys, so confirm the create-tenant endpoint in /openapi.json before scripting it.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page