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.
- Manual organization review
- Mandatory DKIM domain verification
- User-triggered transactional messages
- Delivery, bounce and complaint tracking
- No purchased, rented or non-consensual lists
Frequently asked questions
The commitments governing Mailforge usage.
Which emails are allowed?
Only expected transactional email such as account creation, password resets, confirmations, invoices and operational messages tied to an existing relationship.
Are marketing campaigns allowed?
Not during the beta. Unsolicited outreach, purchased lists and non-consensual sending are prohibited.
How are sender domains secured?
A domain can only send after Amazon SES DKIM verification. Mailforge stores its verification state and sending logs.
How are bounces and complaints handled?
Amazon SES forwards events to Mailforge. Hard bounces and complaints enter the account suppression list and can trigger organization suspension.
A legitimate transactional use case?
Describe your application, recipient source and expected volume. Forge Labs reviews every account before activation.
Contact Forge Labs