maiLane is more than a UI. Under the hood, it's a composable platform for inboxes, routing, identity, and observability — so the client your team uses every day is also the substrate your business runs on.
A fast, keyboard-first email client your team opens every morning — threads, search, snooze, send-later, and the shortcuts you'd expect.
A declarative engine for assigning, forwarding, transforming, and dispatching mail to webhooks. Versioned, previewable, and observable.
Workspace, team, and inbox-level access tied to your IdP. Roles, scopes, and audit trails for every action — built in, not bolted on.
The client is one surface on top of a deeper platform. The same primitives that power the inbox are exposed through APIs and configuration — so admins, operators, and developers all reach for the same building blocks.
Multi-tenant by design. Domains belong to a workspace, with isolated routing, policies, and observability per workspace boundary.
Rules are typed, validated, and versioned. Promote changes through dev → staging → prod with dry-run preview against historic mail.
Encode retention, MFA, sharing, and access constraints as policies — applied automatically when inboxes and users are created.
Every action emits a structured event. Stream to S3, Datadog, Splunk, or your warehouse with no rate limits.
REST API with idempotent operations, OpenAPI spec, and signed webhooks. Generate ergonomic SDKs from the contract.
IMAP, SMTP, SPF, DKIM, DMARC, ARC, and TLS-RPT — all implemented to spec. No proprietary client required.
The fast, focused inbox your team opens every morning.
Run support, billing, and ops queues without leaving the client.
Triage, assign, and route — all from inside the same app.
SSO, time-zone aware SLAs, and async-friendly internal notes.
Operate dozens of brands and domains from a single workspace.
Per-client routing, branded signatures, and clean audit trails.
People ops, IT helpdesk, and finance queues — without buying another tool.
External communication with policy boundaries and full lineage.
Resources are predictable. Errors are typed. Idempotency keys are first-class.
curl https://api.mailane.net/v1/inboxes \
-H "Authorization: Bearer $MAILANE_TOKEN" \
-H "Idempotency-Key: $REQ_ID" \
-d '{
"address": "support@acme.io",
"type": "shared",
"domain": "acme.io",
"owners": ["maria@acme.io"],
"policies": ["mfa_required", "retention_7y"]
}'
// 201 Created
{
"id": "inb_01HZK9...",
"address": "support@acme.io",
"type": "shared",
"status": "active",
"created_at": "2026-04-12T10:18:42Z"
}