About QueryCanary

QueryCanary was built out of a very real problem: discovering your production data is broken… days too late. Whether it’s a metric that silently flatlines, signups that drop and go unnoticed, or a NULL where there shouldn’t be — the data broke, and no one knew.

I built QueryCanary to give developers and data teams an early warning system for their production databases. It's lightweight, SQL-powered, and designed to help you define integrity checks you care about — like low signups, broken joins, or invalid prices — and then get alerted when things drift off course.

It started as a personal tool to make sure I didn't get blindsided at work by broken analytics. Now it's a fully functional micro-SaaS, used in production to monitor real systems — quietly catching issues before they become problems.

QueryCanary supports scheduled SQL checks, anomaly detection, SSH-tunneled Postgres / MySQL / ClickHouse connections, email alerts, teams, and a simple dashboard. It’s still early, but I’m actively building, shipping, and listening.

The Team (of one)

Hi, I’m Luke Strickland — software developer, carpenter, and volunteer firefighter. I’m building QueryCanary from a small town in Western Pennsylvania focused on delivering a simple product for a simple price.

I’d love your feedback. If you have questions, ideas, or find bugs, email me at luke@querycanary.com.

🙇 Thanks for checking out QueryCanary.