Capabilities
Operate the full email lifecycle
OppenMailer connects the work before, during, and after a send: infrastructure, audiences, content, controlled warmup, approvals, delivery, replies, retries, reconciliation, and operational access.
Controlled domain warmup
Run mailbox-centric warmup with explicit schedules, private or platform-managed pools, provider-aware limits, reply threading, cooling, and reconciliation. Warmup supports a measured ramp; it never guarantees inbox placement.
Personal AI and assistant connections
Connect a private AI provider or your preferred MCP client, including ChatGPT, Claude, Cursor, and VS Code, to draft templates, prepare campaigns, map audiences, explain delivery results, and suggest follow-ups. Keep material outputs review-first, choose scoped permissions, inspect access logs, and revoke connections at any time.
Capability-based provider routing
Manage SMTP, Resend, SES, SendGrid, Gmail, SendByte, and platform routes behind one provider contract that considers sender compatibility, health, quotas, message needs, and fallback eligibility.
Mailbox and reply operations
Connect Gmail, Microsoft, or standards-based IMAP mailboxes, keep warmup traffic separate from customer replies, preserve thread identity, and project matched messages into the right workspace workflows.
Reliable background work
Campaign, warmup, provider, billing, retention, notification, and export work uses leased jobs, retries, cancellation, dead letters, replay controls, reconciliation, and process heartbeats instead of hidden browser state.
Campaigns, audiences, and templates
Import CSV or XLSX data, reconnect Google Sheets, map dynamic variables, build reusable HTML and text templates, attach hosted assets, prepare campaigns, and keep everything isolated by workspace.
Delivery and operational visibility
Track delivery events, replies, bounces, failures, route decisions, queue pressure, provider health, warmup progress, billing reconciliation, and assistant access from one operational system.
Security and approval boundaries
Use workspace-derived tenancy, recent-auth checks for sensitive changes, encrypted credentials, scoped tokens, safe redirects, request limits, audit records, and explicit operator approval for consequential AI actions.
Pay with cards, bank, or crypto
Pay for your plan using supported regular currencies or cryptocurrency, giving your team more flexibility across local and international payment methods.