Built to be resold

Per-customer statements you can rebill from. A billing page that explains variances before you ask. Your own MSP as a first-class organization in the console.

Backup is supposed to be your best line

Recurring, sticky, high margin. Then storage grows and the renewal moves, and the best line on the statement becomes the one you argue about. We have been on your side of that call.

  • Margin that leaks quietly

    Per-gigabyte pricing turns a growing client into a shrinking margin, one invoice at a time.

  • Rebilling you cannot show

    If the statement does not map to what you charge, every variance becomes an hour of somebody’s month.

  • Hardware that owns you

    A per-appliance licence makes the renewal conversation about the box.

How it fits your business

  • Rebilling

    Statements built to forward

    Per-customer statements map to what you charge, with the posted list as your defensible ceiling and your internal organization excluded automatically.

  • Operations

    Triage by exception

    Hundreds of customers triage from one queue. The console names what needs you and the safest next action.

  • Ticketing

    Your PSA, first-class

    ConnectWise and CommandIT today, routed by alert type to the right board. Tickets sync status both ways; more PSAs follow.

  • Conviction

    Run on yourself first

    Internal-use licensing lets you protect your own infrastructure with the product you sell, and demo from your own console.

Every customer, one list

Your own organization sits among them, marked internal and excluded from what you rebill.

The customers screen listing every protected organization with status, products, resources, storage location and appliance

Three steps to your first protected client

  1. Protect yourself

    Run your own organization on internal-use licensing. Sell what you already trust.

  2. Take one client

    Onboard a real customer on the standard trial and rehearse the restore in front of them.

  3. Price the book

    Quote from the rate card and the volume band you land in, with the renewal already stated.

Questions partners ask

What does it take to become a partner?

A conversation and an internal-use deployment. We would rather you protect your own infrastructure first than sign a partner agreement you have not tested.

Is there a minimum commitment?

Volume bands reward growth rather than punishing a small start, and the terms are stated in your quote. Nothing about the pricing depends on how hard you negotiate.

Can I white-label it?

Branding controls are in the console for what your clients see. Full white-labelling and custom domains are still an open decision, and we will not promise them before that decision lands.

How do I bill my clients?

Per-customer statements map to what you rebill, with your own internal organization excluded automatically. The billing page explains every variance before you have to ask about it.

What about the customers I already protect with something else?

Migrate them when their renewal comes rather than paying twice. We would rather earn the second renewal than force the first.

Start with your own infrastructure

Protect your own organization first, on internal-use licensing. Sell it once you have recovered something of your own, and the demo stops being a pitch and becomes a description of your own Tuesday.

What we commit to

  • The same rate for the same volume, for every partner.
  • Renewal pricing stated at signing, and a locked rate that holds for its term.
  • No per-appliance licence, so the hardware conversation stays yours.