Skip to content
Pilot · first 5 MSPs

Enforcement-ready client domains, on the Partner plan.

For MSPs with 50 or more client domains: the Partner plan at $299 a month with 100 domains included, plus a readiness workflow that takes each domain to enforcement on evidence the client signs off. Where the product does not do a step yet, we do it by hand and say so below.

01 — Who it is for

MSPs with a real portfolio and DNS access.

You manage at least 50 client domains.
You hold DNS access for them, or can get it from the client.
You want each client at enforcement with evidence the client can read and approve.
02 — The workflow

Four steps, and who does each one today.

  1. 01Sender inventory with owner approval

    Product plus a person

    Your client sees every service that sends as their domain, who owns it on their side, and whether they approved it.

    Today: The Senders view lists every source found in each domain's aggregate reports, with its provider, volume and SPF and DKIM results, and lets you categorize each one and add notes. It has no owner or approval field yet, so for pilot accounts we record each sender's owner and the client's approval by hand in the readiness pack.

  2. 02Readiness checklist with documented exceptions

    Done by hand for pilot accounts

    Each domain gets a written list of what has to be true before enforcement, with every exception and its reason on the record.

    Today: The product scores each domain from 0 to 100 and names its top issue. The checklist and the exceptions are not in the product yet: for pilot accounts we write them by hand in the readiness pack, from the domain's own report data.

  3. 03DNS change alerts

    Done by hand for pilot accounts

    When someone edits a client's SPF, DKIM or DMARC record, you hear about it before the client's mail does.

    Today: The product checks each domain's records once a day by default and keeps every change in the domain's DNS history. Change emails for client domains do not reach the partner account yet, so for pilot accounts we review that history and email you each change by hand.

  4. 04White-label client evidence export

    Product plus a person

    Your client gets a document under your name that shows where each domain stands and what was decided, as supporting evidence for their own review.

    Today: Your client's white-label portal already exports a posture summary PDF under your company name and brand color. The readiness pack that goes with it, with senders, checklist, exceptions and changes, is assembled by hand for pilot accounts.

03 — What we promise about enforcement

Readiness and documented exceptions. Nothing on a calendar.

Readiness, not a date.

A domain moves to enforcement when its checklist is complete and the client signs off. We set no calendar deadline, because a sender nobody has found yet does not keep to one.

No staged share of mail.

RFC 9989 retired the pct tag, so a policy is never applied to a fraction of messages. Each step covers the whole domain and follows the evidence for that domain.

No reject for domains whose users post to mailing lists.

RFC 9989 section 7.4 advises against it, because many lists change messages in ways that break DMARC. Those domains stay below reject, at the policy their evidence supports, recorded as an exception.

Going back is a reviewed change.

Every record change is written down, reviewed and approved before it is published, and the previous record is kept so it can be restored through the same review. Nothing changes a record automatically.

We hold no DNS write access.

You or your client publish every record. We prepare the change and check it once it is live.

04 — Not in the pilot

What this offer does not cover.

Forensic reports

The readiness work uses aggregate reports only. Forensic samples, if a domain publishes a ruf= tag, are outside the pilot workflow.

DNS changes made by us

You or your client publish every record. We hold no credentials for any zone.

A reject date

Enforcement follows readiness and the client's sign-off, domain by domain.

PSA or RMM modules

The REST API and outbound webhooks ship today. Native ConnectWise, Autotask, Kaseya, NinjaOne and HaloPSA modules are on the roadmap, not live.

Per-domain removal

Removing a client means deleting its whole organization, as the partner billing rules explain. Export its history first.

05 — Price and terms

$299 a month. 100 domains included.

$2.99 per client domain per month above 100, counted at the daily usage sync
No setup fee, no annual billing and no trial
Cancel any month from the Stripe customer portal
The by-hand parts of the pilot cost nothing extra

Below 76 domains, Partner Starter at $119 a month costs less and runs the same product, without the by-hand pilot work.

Every billing rule is on the partner program page, and client data is covered by the data processing agreement.

06 — Remediation, done for you

Want the remediation done for you?

PlatOps, the company behind DDMARC, sells the DMARC Enforcement Sprint: $2,500 per domain, one-time, about 30 days for most domains. It finds and fixes each sender and hands back a written account of what changed. It is optional, priced separately, and the pilot does not require it.

Before you subscribe

The questions MSPs ask.

MSPs that manage at least 50 client domains, hold DNS access for them or can get it, and want their clients at enforcement with evidence the client can read. The first 5 MSPs on the Partner plan get the by-hand parts of the workflow described on this page.

07 — How to start
  1. 1Create a free account from any subscribe button on this page
  2. 2Verify your email: Stripe Checkout opens for the Partner plan
  3. 3Send us your first client's domains and we start its readiness pack

Start with one client. 100 domains are already included.

Subscribe with a card, enroll your first client organization, and tell us which domains to start on. The first readiness pack is the proof that the workflow fits your service.

100 domains included · $2.99 per domain above that · cancel any month