A controlled private beta
Access is manually granted after reviewing the organization, use case and sender domains.
Access by request
For Forge Labs applications and organizations with an existing relationship with their recipients.
- Forge-managed plans and quotas
- Mandatory sender authentication
- Transactional API and campaigns
- Warm-up, bounce, complaint and reply tracking
- No purchased, rented or scraped lists
Frequently asked questions
The commitments governing Mailforge usage.
Which emails are allowed?
Expected transactional messages, newsletters to an authorized audience and targeted B2B outreach with a documented lawful basis.
Are marketing campaigns allowed?
Yes after Forge Labs review, with documented recipient origin, unsubscribe handling and progressive quotas. Spam and purchased, rented or scraped lists remain prohibited.
How are sender domains secured?
A domain must be authenticated and explicitly assigned to a traffic class. Mailforge separates transactional, newsletter and B2B traffic.
How are bounces and complaints handled?
Providers send events to Mailforge. Hard bounces and complaints enter suppression lists; any complaint or a 3% hard-bounce rate pauses warm-up.
A legitimate email use case?
Describe your transactional flow or campaign, recipient source and expected volume. Forge Labs reviews every activation.
Contact Forge Labs