Source Protection/One switch per customer

End one customer. Nobody else notices.

Every customer has their own key. Give a pilot an end date, pause a late payer, or cut off a contract that ended.

Keys · Acme platform

Acme BankRunning
Ends 30 Nov · 2 of 5 copies
GlobexRunning
Ends 31 Mar · 1 of 3 copies
Initech pilotSwitched off
Pilot ended on day 31
ResumeEnd for good

How the switch works.

Each customer runs your software with their own key. You can give the key an end date, pause it, end it for good or swap it for a new one, and only that customer is affected. Their locked parts stop opening the next time the software starts or checks in.

One key for each customer

Give each customer, team or developer a key, and choose the repositories it covers. Set it once and new builds of those repositories work with it.

Give it an end date

A pilot can end on day 31 with nobody chasing. A contract can end on the day it ends.

It takes effect the next time their software starts or checks in.

Pause, end or swap

Pause a key and bring it back later with nothing to redeploy. End it for good. Or swap it for a new one if you think it leaked.

A swapped key means the customer pastes in the new one.

Limit the copies

Choose how many copies of the software a customer can run at once.

Who uses it.

Sales teams running pilots and trials
Give the pilot an end date and it ends when you said it would.
Finance teams with a customer behind on payment
Pause the key and bring it back when they have paid.
Vendors whose contract has ended
End their key and the locked parts stop opening.