Platform / Control & API
Run it from one place. Or automate it by API.
Infrastructure you can't operate safely is infrastructure you don't really control. The console and API put the entire estate under deliberate, attributable management: domains, mailboxes, routing, access, events.
Email operations have a tooling problem. The actual controls live in a dozen places: registrar panels, provider dashboards, server configs, spreadsheets. Each has its own login and its own permissions model, and no audit trail connects them. So nobody can answer "who changed what, when?", and every change is a small act of faith.
We consolidated the controls. One console and one API over DNS, mailboxes, routing preferences, provider connections, and team access, with the permissions, MFA, and audit logging that consolidation demands. See it yourself at console.egressif.io.
The model
One hierarchy, every object accountable.
Capabilities
What the control plane gives you.
A hierarchy that matches reality
Organizations contain teams. Teams own domains. Domains carry mailboxes and routing preferences. Every sending identity is a first-class object with its own configuration, isolation, and history. Works the same whether you are one company with three streams or an agency with two hundred brands.
Role-based access control
Granular, per-capability permissions across organizations, teams, users, domains, DNS records, and mailboxes. An account manager sees their clients and nothing else. A billing role sees invoices and no infrastructure. Offboarding someone is one action. Custom roles let you express your actual org chart instead of ours.
Authentication worth the name
Multi-factor authentication with authenticator-app and email factors, session management, and scoped API keys for automation. The console protecting your email infrastructure is held to the same standard as the infrastructure.
Provider connections
Connect Google Workspace and Microsoft 365 through their official OAuth flows for domain verification and administration. Bring your own accounts at the big sending platforms where that fits your architecture. Credentials and tokens are stored encrypted, scoped to the minimum, and deleted on revocation.
Routing preferences in plain language
Decide how mail bound for Google, Microsoft, security gateways, consumer webmail, and everything else should be handled. Per team, with per-domain overrides and ordered fallback preferences. Routing differs per domain, so you can run controlled experiments: try a strategy on a test domain, compare outcomes, roll out the winner. The engine executes your intent. You never touch a server.
Bulk operations everywhere
Domains, mailboxes, users, and records support batch create, edit, and delete, with CSV import where it makes sense. Onboarding thirty domains is the same workflow as onboarding one, plus a column.
Audit logs on every action
Every administrative change records who did it, on whose behalf, from where, when, and what changed. The attribution survives async background jobs too. The trail your security review will ask for already exists.
A REST API over the whole estate
Domains, mailboxes, configuration, and delivery events are all addressable programmatically. Build provisioning into your product, wire events into your warehouse, or drive the entire platform from your own tooling. The console and the API are two views over the same system.
Webhooks, if you can use them
Subscribe your systems to delivery events: accepts, deferrals, bounces, suppression hits. Pushed to your endpoints as they happen. CRMs stay honest, dashboards reflect reality, and automated workflows (including AI agents) get the feedback loop they need.
See the console with your own domains.
Tell us where you are today: domains, volume, providers, what hurts. We will come back with a concrete way forward.