Release qualification
A visible idea is not the same as a live promise.
The next releases depend on real provider connections, privacy and legal approval, and repeatable deployment evidence. We will keep planned areas visibly separate from available ones.
This is a directional roadmap, not a delivery date, service commitment, or public signup announcement.
What a release has to prove.
Working code is one part of the evidence. A public feature also needs operating, recovery, and support boundaries.
Real sending
Qualify the sender and rehearse the full delivery, bounce, complaint, and suppression path.Understand deliveryCertified connections
Verify provider scopes, webhooks, retries, revocation, and reconciliation before calling a connector live.Explore integrationsPrivacy and trust
Publish approved terms and verify data rights across the stores a feature touches.Review security
The next step
The latest approved news will be explicit.
Join the optional updates list for product and pricing announcements. A preview here does not reserve access.