Customer Deployment Intake Checklist
Use this checklist before implementation begins. It is intended for a sales
engineer, solution architect, or implementation lead to complete with the
customer.
1. Customer and Project
| Question |
Answer |
| Customer name |
|
| Project sponsor |
|
| Business owner |
|
| Technical owner |
|
| Security owner |
|
| Operations owner |
|
| Target go-live date |
|
| Pilot or production? |
|
| Regulated/SOX/ICFR scope? |
|
2. Cloud and Runtime
| Question |
Answer |
| Cloud provider |
AWS / Azure / GCP / private / other |
| Region(s) |
|
| Kubernetes platform |
EKS / AKS / GKE / OpenShift / private / other |
| Existing cluster or new cluster? |
|
| Temporal deployment preference |
Embedded / dedicated / existing customer-managed |
| Temporal operations owner |
|
| Container registry restrictions |
|
| Helm allowed? |
|
| Terraform allowed? |
|
| Required tagging/labeling standards |
|
| Private endpoint requirements |
|
3. Sizing
| Question |
Answer |
| Expected number of mappings at go-live |
|
| Expected number of mappings after 12 months |
|
| Largest source table row count |
|
| Largest target table row count |
|
| Expected run frequency |
|
| Required concurrent runs |
|
| Required RPO/RTO for Paridity |
|
| Evidence retention duration |
|
| Preferred sizing tier |
Small / Medium / Large |
4. Identity and Access
| Question |
Answer |
| Identity provider |
Okta / Entra ID / Keycloak / Cognito / other |
| Protocol |
OIDC / SAML |
| Issuer URL or entity ID |
|
| API audience/client ID |
|
| UI client ID |
|
| Group claim name |
|
| Email/user claim name |
|
| Role mapping approved? |
|
| Break-glass process |
|
5. Secret Backend
| Question |
Answer |
| Secret manager |
AWS SM / Azure KV / GCP SM / Vault / Infisical |
| Workload identity mechanism |
IRSA / Azure WI / GKE WI / other |
| Secret naming convention |
|
| Secret rotation policy |
|
Canary connection_ref available? |
|
| Static keys prohibited? |
Yes / No |
6. Network
| Question |
Answer |
| Paridity hostname |
|
| TLS certificate source |
|
| Ingress controller |
|
| Source system CIDRs/endpoints |
|
| Target system CIDRs/endpoints |
|
| Replication tool endpoints |
|
| Secret backend endpoints |
|
| IdP/JWKS endpoints |
|
| SIEM/OTel endpoints |
|
| NetworkPolicy enforced by CNI? |
Yes / No |
| NAT/private endpoint constraints |
|
7. Source Systems
| System |
Type |
Environment |
Owner |
Endpoint |
Access approved? |
|
|
Dev/Test/Prod |
|
|
|
|
|
Dev/Test/Prod |
|
|
|
|
|
Dev/Test/Prod |
|
|
|
For each source system, collect:
- Database/platform type and version
- Network endpoint
- Required TLS settings
- Service account name
- Secret reference
- Schemas/tables in scope
- Expected load constraints
- Preferred read replica, if applicable
8. Target Systems
| System |
Type |
Environment |
Owner |
Endpoint |
Access approved? |
|
|
Dev/Test/Prod |
|
|
|
|
|
Dev/Test/Prod |
|
|
|
|
|
Dev/Test/Prod |
|
|
|
For each target system, collect:
- Warehouse/database type and version
- Compute warehouse or cluster to use
- Resource monitor or budget control
- Service account name
- Secret reference
- Schemas/tables in scope
- Query timeout or concurrency limits
| Tool |
Source |
Target |
Owner |
Metadata access method |
Approved? |
|
|
|
|
API / DB / files / none |
|
|
|
|
|
API / DB / files / none |
|
For each replication tool, collect:
- Tool name and version
- Task/job names
- How lag/watermark state is exposed
- Service account or API token secret reference
- Whether Paridity should treat replication state as advisory or strict
10. First Mapping Candidates
Choose a simple first mapping before a large or sensitive one.
| Question |
Answer |
| Source table |
|
| Target table |
|
| Primary/business key |
|
| Approximate row count |
|
| Watermark column or strategy |
|
| Replication tool/task |
|
| Full mode required? |
Yes / No |
| Auto/incremental mode required? |
Yes / No |
| Field-level diff required? |
Yes / No |
| Raw value storage allowed? |
Yes / No |
11. Operations
| Question |
Answer |
| Monitoring system |
|
| Log retention |
|
| SIEM integration required? |
|
| Alert channels |
|
| Backup owner |
|
| Temporal restart owner |
|
| Temporal patch/upgrade owner |
|
| Temporal persistence backup owner |
|
| Restore test date |
|
| Upgrade window |
|
| Incident bridge process |
|
| Support contact list |
|
12. Go-Live Approval
| Approval |
Owner |
Date |
| Architecture approved |
|
|
| Security approved |
|
|
| Network approved |
|
|
| Identity approved |
|
|
| Source/target access approved |
|
|
| Backup/restore approved |
|
|
| First run validated |
|
|
| Production handoff complete |
|
|