Skip to content

Cost and License Considerations

Cost Buckets

Paridity cost has two categories:

  1. Cost to run the Paridity platform.
  2. Cost created in customer data platforms when reconciliation queries run.

The second category can be larger at scale and must be included in customer planning.

Paridity Platform Runtime Cost

Runtime cost includes:

  • Kubernetes nodes or serverless container runtime
  • API, UI, and worker pods
  • Managed PostgreSQL
  • Temporal compute and persistence
  • Load balancer or ingress
  • Logs, metrics, traces, and SIEM export
  • Evidence storage
  • Backups and point-in-time recovery
  • NAT gateways or private endpoint charges where applicable

Reference AWS estimates from the architecture docs:

Tier Typical scope Directional monthly cost
Small Pilot, up to 50 mappings About $110/month
Medium Enterprise starting point, up to 500 mappings About $865/month
Large Large estate, up to 5,000 mappings About $5,800/month
Multi-region V1 planning only, large per region About $17,400/month for three large regions

These are planning numbers, not quotes. Region, discounts, reserved capacity, evidence retention, log volume, and HA requirements can materially change cost.

Data Platform Cost

Reconciliation work can create cost in source and target platforms:

Platform area Cost driver
Snowflake Warehouse credits consumed by proof and extraction SQL
Databricks SQL warehouse/serverless/job compute
BigQuery Bytes scanned and slot usage
Redshift Cluster/serverless compute
Source databases CPU, I/O, read replicas, and possible license capacity
Object stores Read requests, scanned bytes, and transfer
Network Cross-AZ, cross-region, private endpoint, NAT, or egress charges
Logging/SIEM Ingested application and audit logs

For large datasets, customer warehouse/database resource monitors should be configured before production schedules are enabled.

Cost Controls

Recommended controls:

  • Start with a controlled pilot mapping.
  • Use auto incremental mode where appropriate.
  • Use full mode intentionally for baseline or periodic controls.
  • Use proof-first execution so field diff work runs only after proof failure.
  • Set worker concurrency limits per source/target system.
  • Schedule heavy jobs outside business-critical windows.
  • Use partitioned reconciliation for very large tables.
  • Configure evidence retention and purge policy.
  • Monitor PostgreSQL storage growth.
  • Monitor warehouse credits/bytes scanned for target systems.
  • Review cost estimates after the first production week and first month.

License Posture

Paridity is designed around commercially safe dependencies. Core components are generally permissive or commercially accepted:

Component License posture
FastAPI, Pydantic, SQLAlchemy Permissive ecosystem
React, Vite, TanStack, Zustand, shadcn/ui, lucide Permissive ecosystem
PostgreSQL PostgreSQL License
DuckDB MIT
Apache Arrow/PyArrow Apache 2.0
Trino Apache 2.0
OpenTelemetry Apache 2.0
Kubernetes, Helm CNCF/open-source ecosystem
Temporal self-hosted / Python SDK Commercially usable for this packaging model

The product should maintain a third-party notices file and SBOM as part of the release process.

License Cautions

Important cautions:

  • Customer database drivers may have separate licenses or download terms.
  • Oracle, DB2, SAP, Snowflake, Databricks, and similar systems may require customer-owned client libraries, accounts, or subscriptions.
  • Customer replication tools remain separately licensed by the customer.
  • Paridity integrates with replication tools; it does not grant licenses to Qlik, GoldenGate, SLT, Fivetran, Airbyte Cloud, or similar products.
  • HashiCorp Vault should be optional, not required. Many customers will prefer their cloud-native secret manager.
  • Avoid making Confluent Platform components required. Apache Kafka core is acceptable; Confluent Platform components may carry license constraints that need legal review.

Commercial Packaging Considerations

Before selling production deployments, define:

  • Paridity commercial license/EULA
  • Third-party notices and SBOM delivery
  • Support boundaries between Paridity and customer cloud operations
  • Supported connector tiers
  • Supported deployment targets
  • Upgrade policy and supported version window
  • Security patch SLA
  • Whether implementation services are included or separate