Skip to content

Paridity Customer Deployment Guide

This documentation pack explains how Paridity is deployed after a customer buys the product and wants to run it in their own cloud account.

It is written for sales engineers, customer platform teams, security reviewers, DBAs, and implementation partners. It avoids assuming deep Kubernetes or Temporal expertise, while still naming the concrete responsibilities and technical requirements.

Document Map

Document Purpose
01_deployment_overview.md Plain-language explanation of what gets deployed and how it fits into the customer's environment
02_requirements.md Infrastructure, identity, network, database, and operational prerequisites
03_responsibility_matrix.md Who owns each part of the deployment and ongoing operation
04_deployment_process.md Step-by-step process from sale through production handoff
05_security_and_networking.md Security architecture, network flows, secrets, SSO, and evidence handling
06_cost_and_license_considerations.md Cloud cost drivers, sizing, open-source license posture, and customer-provided licenses
07_customer_intake_checklist.md Questions to collect before implementation begins
08_temporal_operations.md What the customer must operate for Temporal and what Paridity owns

These are internal engineering references, not part of the customer documentation set. They are named rather than linked, because they are not published to the customer documentation site - ask your Paridity contact if you need one of them during an implementation.

Reference Repository path
Deployment runbook docs/runbooks/deployment.md
Security checklist docs/runbooks/security_checklist.md
Reference deployments docs/architecture/reference_deployments.md
Disaster recovery docs/architecture/disaster_recovery.md
Deployment split-readiness docs/architecture/deployment_split_readiness.md
Helm chart README deploy/helm/paridity/README.md
Terraform README deploy/terraform/README.md