Documentation for integrators.

Pryvate is a secure real-time communications engine designed to be embedded and governed by system integrators. It provides hardened server infrastructure and native mobile SDKs that integrators deploy inside their own solutions for government, defence, legal, healthcare, and other high-assurance environments.

Pryvate is not a messaging app, not a collaboration platform, not a SaaS tool for end-users, and not a replacement for Teams, Zoom, or WhatsApp. If it sounds like an app, it isn't Pryvate. It's infrastructure that integrators embed within their own platforms.

Pryvate supports multiple deployment models: on-premises within your own data centre, sovereign cloud deployment on UK or jurisdiction-specific infrastructure, or hybrid models combining both. The integrator controls the deployment environment entirely.

The integrator always controls the data. Pryvate operates as a subsystem within your architecture. You control deployment environment, branding, identity management, audit boundaries, retention policies, and the customer relationship. Pryvate has no access to your communications.

Pryvate is designed to support GDPR and HIPAA frameworks, and is architected to align with NCSC principles. It supports SOC 2 pathways and sovereign deployment models. These represent architectural alignment — not certifications. Specific compliance outcomes depend on your deployment context and integrator implementation.

No. Pre-development participation is structured as professional services, not investment. There is no equity involved, no IP transfer, and no roadmap control. All participation fees convert to licence credits or integration services credits.

Participation fees provide early access to SDK builds, feedback sessions, priority onboarding, and (for higher tiers) input into API shape and deployment support. All contributions convert to licence or engineering services credits upon general availability.

Yes. Integrators fully control branding and user experience. End-users interact with your platform, not Pryvate. We provide the secure communications engine; you provide the product experience.

Pryvate is policy-driven. You define retention rules, access controls, and audit boundaries through deployment configuration. The platform supports audit-ready logging without requiring default content storage — proportionate to your governance requirements.

Request an architecture discussion. Initial conversations are technical and architectural, not sales-led. We'll assess fit, discuss your deployment context, and determine whether Pryvate is appropriate for your use case.