SMTP-first email marketing platform
Build campaigns, manage audiences, and send from the customer’s own email ID.
MailForge gives teams one operating surface for SMTP connections, contacts and groups, email designs, campaigns, timestamp automation, analytics, and workspace governance while the customer’s email provider performs the actual send.
What is included
The modules that match the current MailForge workflow
Every public section below maps to a real app area in the current workflow, from SMTP setup to campaigns, automation, analytics, and governance.
Dashboard
Readiness, usage, SMTP health, audience, email design, campaign, automation, and audit summaries.
Email Connections
SMTP, API key, or OAuth setup for the customer email ID with encrypted credentials, From metadata, and throttles.
Contacts and Groups
Create contacts, create audience groups, import CSV/XLSX files, attach groups, and download CSV/XLSX exports.
Email Designs
Create reusable HTML email assets with live preview and approved merge tags.
Campaigns
Plan one-time or scheduled marketing sends that go out through the selected customer email ID.
Automation
Create timestamp or recurring sends through customer SMTP with specific recipients, contact groups, individual/bulk mode, and To/CC/BCC routing.
Reporting and Governance
Review analytics, deliverability, billing limits, workspace users, security settings, 2FA, and audit logs.
Campaign workflow
Move from SMTP setup to a reviewed marketing send
The platform is designed around a simple operating path: connect the customer email ID over SMTP, prepare the audience, create content, and send only after readiness checks are clear.
Operations visibility
See the signals that matter before and after sending
Dashboard readiness, analytics, deliverability reports, and audit logs help teams understand what is ready, what was sent, and what needs attention.
Plans and pricing
Pricing aligned to contacts, customer email IDs, automations, and users
Plans define MailForge workspace capacity. Actual emails sent depend on the connected customer email provider limits, mailbox reputation, SMTP throttles, and any daily/hourly/minute caps configured by the user.
Starter
For small teams starting regular campaigns from their own customer email IDs.
- 50,000 MailForge email allowance
- Actual sends depend on provider limits
- 10,000 stored contacts
- 3 customer email IDs
- 5 active automations
- 3 workspace users
Growth
For brands and agencies managing larger audiences across customer-owned email connections.
- 250,000 MailForge email allowance
- Actual sends depend on provider limits
- 100,000 stored contacts
- 8 customer email IDs
- 50 active automations
- 10 workspace users
Scale
For high-volume teams that need more customer email IDs, users, and governance.
- 1,000,000 MailForge email allowance
- Actual sends depend on provider limits
- 500,000 stored contacts
- Multiple customer email IDs
- Unlimited automations
- 25 workspace users
Security and compliance
Workspace controls for teams handling real subscriber data
MailForge keeps role access, 2FA configuration, audit trails, suppression hygiene, unsubscribe handling, and billing limits visible inside the workspace.
RBAC and 2FA
Owners, admins, and marketers see role-aware menus and protected workflows.
Suppression hygiene
Contacts can be suppressed or resubscribed with consent-aware operating guidance.
Audit and limits
Workspace changes, billing limits, customer provider limits, SMTP capacity, and security settings remain visible to operators.
FAQ
Answers before teams start sending
Common questions about the current MailForge setup and what has intentionally been kept simple.
Which sending systems are supported?
The current setup is SMTP-focused: client SMTP, Gmail SMTP, Microsoft 365 SMTP, Outlook SMTP, Hostinger SMTP, and custom SMTP details.
Does MailForge send from its own mail servers?
No. MailForge is the operating layer. The connected customer email ID and its SMTP provider are the sending source.
How many emails can be sent?
MailForge plans set workspace allowance, but actual send volume depends on the customer email provider limits, mailbox reputation, and configured daily/hourly/minute caps.
What is the difference between campaigns and automation?
Campaigns are planned one-time or scheduled marketing sends. Automation handles timestamp-based follow-ups and recurring sends.
Can contacts be imported in bulk?
Yes. Contacts can be added manually or imported through CSV/XLSX files, with group assignment included in the import flow.
Can users preview email designs before sending?
Yes. Email Designs supports a direct HTML editor with live preview.
How is automation handled?
Automation is timestamp and recurrence based, with scheduled sends, follow-ups, recurring sends, contact groups, and specific recipient options.
Ready for a cleaner email marketing workspace?