DEPLOYMENT

Make the hosting boundary a reviewed decision.

The current PrivDesk application works in an isolated local stack. We are preparing a hosted pilot and will scope customer-specific environments against real requirements.

Discuss your environment
RELEASE SEQUENCE
  1. Local product verification
  2. Hosted pilot acceptance
  3. Provider and restore checks
  4. Production review
Each gate needs its own evidence.
CURRENT DELIVERY STATE

Where the product can run.

Deployment names describe options for review. They do not imply that a public SaaS, dedicated cloud or air-gapped service is already available.

01

Local product stack

Core API and worker, PostgreSQL, S3 compatible storage, staff web app and customer portal have an isolated local test path.

Implemented
02

Hosted pilot

A public pilot needs a selected region, same-origin HTTPS, always-on worker, provider setup, monitoring, backups and a verified restore.

Preparing
03

Dedicated or private deployment

Customer-specific infrastructure, private cloud and self-hosted requests need architecture, operations and security acceptance for each environment.

Technical review
SCOPING QUESTIONS

What must your environment prove?

  • Data location and ownership
  • Identity and customer access
  • Worker, storage and backup operations
  • AI and integration provider policy
Send a deployment brief
PILOT REVIEW

Start with the support workflow and trust requirements.

We will identify the next technical and operational checks for your environment.

Plan a review