I just launched ParityCheck — a tool to detect environment drift before it breaks production. One of the most frustrating issues in software engineering is when something works perfectly in development but fails in staging or production. Differences in dependencies, environment variables, system packages, or database schemas can cause subtle bugs that are difficult to track down. ParityCheck helps teams detect those differences early. What it does: • Collects environment data (OS, runtime, dependencies, env vars, DB schema) • Compares environments to detect configuration drift • Calculates a health score for environment parity • Highlights direct vs transitive dependency mismatches • Integrates with CI/CD pipelines to prevent risky deployments • Provides a dashboard with drift insights and history Built with: Python, FastAPI, React, Docker, Kubernetes, PostgreSQL, Redis, and GitHub Actions. It also includes a CLI tool (envguard) for collecting and comparing environment reports locally or in CI. The goal is simple: make environment parity visible so teams can catch issues before production.

ParityCheck

Detect environment drift before it breaks production

Detect environment drift before it breaks production