SAML SSO, SCIM deprovisioning, IPs reserved to your contract, attributed audit history and a residency region you choose, on a single-tenant fleet.
0.00%
Uptime SLA
0
Dedicated IPs per contract, minimum
0
Months of audit log retention
Most outbound tools fail the review before anyone reads the feature list.
Identity, isolation and evidence are the three questions, and consumer-grade tooling answers none of them.
No SAML means an unmanaged account
Without SSO and SCIM, every hire and every departure becomes a manual line on somebody's offboarding checklist.
Shared IPs share the blame
On pooled sending infrastructure, a neighbour's complaint rate lands on your reputation and you have no lever to pull.
No attribution, no sign-off
A reviewer will not approve a system that cannot say which account changed which setting, and when.
Identity, isolation and evidence, in that order.
Each one is a control your reviewer can test, not a bullet on a datasheet.
Identity provider
SAML 2.0
SCIM synced
Provisioned in real time
SSO with SCIM behind it
Connect the identity provider once; access grants and deprovisioning follow your directory instead of a checklist.
Reserved to your contract, never shared
IPs reserved to your contract
Your fleet sends from a pool no other customer touches, so reputation stays a function of your own volume.
audit --tail 3
Every change attributed and exportable
Configuration edits and sign-ins are timestamped against a named account and export on demand for review.
Residency you pick, not inherit
Pin mailbox and log data to US, EU or APAC infrastructure to match the obligation you're already under.
Commitments, not aspirations.
0.00%
Uptime SLA
0+
Enterprise sending fleets managed
0
Months of audit log retention
0
Regions available for data residency
The questionnaire, answered up front
Yes, on enterprise contracts. SSO connects to any standards-compliant identity provider, and SCIM keeps provisioning and deprovisioning in step with your directory.
Yes. Enterprise contracts include an IP pool reserved to your sending fleet alone, with no shared reputation exposure.
You choose the residency region (currently US, EU or APAC), and mailbox and log data stay inside it.
Twelve months of attributed history by default, exportable at any point if your own retention window is longer.
A 99.99% uptime SLA with defined incident response times, written into the contract.
Every control your reviewer will ask to see.
Identity, audit history, dedicated IP allocation and residency, readable in one place and backed by single-tenant architecture.
SSO + SCIM
Identity provider connected
Audit log
Dedicated IP pool
6 IPs
Reserved, not shared
Region residency
Dedicated sending architecture
Single-tenant sending fleet, isolated per contract
“Sign-off took a week because the audit export and the dedicated IP allocation were both there on day one. Nothing had to be built for us.”
What legal and security ask for after the demo
SAML and SCIM without a custom build
Works against your existing identity provider with no bespoke integration work.
A named engineer, not a queue
Incident response goes to someone who already knows your fleet.
MSA, DPA and questionnaires
Contract terms and security reviews are handled directly by our team, not a web form.
Dedicated network paths
Sending traffic can be routed over private peering where your policy requires it.
Quarterly reputation review
A standing session on fleet health with the deliverability contact on your account.
Region-specific DPAs
Data processing agreements matched to the region your data is pinned to.
Turn the security review into a formality.
Talk to our team about SSO, dedicated IPs, residency and the audit export your reviewers will ask for.
Built for other teams too
