Building the Best Monitoring and Tuning Tools for PostgreSQL

An independent company trusted by the world's largest Postgres operators

All-in on Postgres for Over a Decade

pganalyze began in 2012 when Lukas Fittl set out to build the best Postgres monitoring tool for production workloads. Today it is the trusted provider of deep Postgres observability and performance tuning for top companies around the world, including some of the Fortune 500.

Atlassian
Autotrader
Moody's
Salsify
Fivetran
fuboTv
pganalyze Team at a Postgres conference

From Flagging Issues to Providing Solutions

Rooted in our team's shared passion to optimize database performance based on years of scaling systems for Citus Data, Microsoft & Heroku, the company has grown while maintaining its independence. Today, we are focused on providing the best tooling to fix slow queries, missing indexes, and more, using deterministic, rule-based logic via pganalyze Advisors.

Built with and for the Postgres Community

Postgres continues to be the backbone of the world's data infrastructure, and we're proud to be a part of the community that is driving its evolution. In addition to being active Postgres contributors, we also share practical insights through conference talks, our YouTube channel & other resources. We also maintain the libpg_query open source project, a Postgres SQL parsing library used by many other projects.

Lukas Fittl speaking at a Postgres conference
pganalyze Team Offsite 2025

Thoughtful Growth, Not Growth at All Costs

pganalyze is a sustainable, remote-first company. That means async-first communication, real vacation time, and a culture built on trust. We think long-term, plan 6-week cycles, and prioritize deep technical work over shiny distractions. We're proud to build software that reflects the same values we bring to our team: precision, respect, and focus.

Get in touch

pganalyze Customer Quote by Ferenc E.: 'I had a great experience with pganalyze (both the product and the people making it) for up to terabyte-scale PostgerSQL instances.'