status
beta
beta lane
IMAP mail-stream guard — hot-reloadable rule pipeline, quarantine buckets, audited rule edits (propose / apply / revert), webhook relays, SMTP intercept.
04 / mailroute prospect
MailRoute
A mail stream guard that treats inbox delivery as an auditable rules engine, not a black box: quarantine, review, and signed events live in the same path.
mail securityquarantineaudit trail
completion
74%
finished scope progress
Completion estimate across public surface, working system parts, and remaining implementation depth.
current value
$118k
derived from current completion
Estimated present studio asset value at the current scope and maturity level.
finished estimate
$160k
pricing signal €49–199/mo per domain
Target studio asset value at the planned finished scope. Revenue status: pre-revenue.
Internal studio value estimates in USD. Current value is derived from completion percentage and is not booked revenue.
What is done
Mailroute is already framed as a concrete operator tool, not a vague filtering promise.
- The rule-driven inspection model is defined across IMAP/SMTP handling, quarantine buckets, and signed downstream event flow.
- Audited propose/apply/revert rule editing is part of the product shape, which is a real differentiator versus opaque hosted filtering.
- The public product line, docs entry points, and surrounding mail-stack work establish a credible operational direction.
What is left
What remains is deeper execution hardening around review workflow and message-path reliability.
- Complete the stronger SMTP intercept and delivery-control path so policy can sit earlier in the mail flow.
- Improve the operator review surface around quarantine decisions, exceptions, and false-positive handling.
- Tie message handling more directly into the broader governance and audit infrastructure so rule changes and outcomes share one evidence model.
Commercial frame
Mailroute sells on visibility and operator control: the ability to explain what happened to a message and why.
- Pricing signal: €49–199/mo per domain, with room for managed review and compliance-sensitive tiers.
- Best fit: smaller teams and controlled environments where generic hosted filtering is either too opaque or too blunt.
- Finished-value estimate assumes hardened policy lanes, clear review UX, and credible downstream event integrations.
The strongest version of Mailroute is not just stricter filtering. It is a mail control surface where review, evidence, and policy change history are all inspectable.