Field-level retrieval
Request the minimum approved fields without a separate feature charge.
Simple USD pricing
Pay for the customers you protect.
Every published plan includes approved stores, updates, searches, retrievals and deletions under fair use. No per-field or per-request meter discourages safer data handling.
Published subscriptions
Choose the smallest plan that covers every customer.
Plan capacity follows the number of unique customer identities under protection. Prices and allowances below come directly from the published Piipe configuration.
Loading Piipe plansFinding the options available for your organisation.
Plan finder
One choice. One clear recommendation.
How many customer identities should Piipe protect? We recommend the smallest published plan that covers them.
Customers protectedSelect the range that covers your customer base.
A visible growth policy
Warning first. Grace next. Upgrade only when required.
Piipe does not stop protecting identities the moment normal growth crosses a plan boundary.
- 100%NotificationWe tell you when usage reaches the published allowance.
- 105%Grace periodProtection continues while you review the next plan.
- 110%Plan adjustmentThe next suitable plan covers continued growth.
Included by design
Security controls are not add-ons.
The product should not become less secure because a customer chooses a smaller plan.
Policy and audit
Purpose checks and accountable operations apply across published plans.
Developer access
Use the HTTPS API and integration guidance included with the service.