Documentation

Docs

Everything needed to run Praxion: connecting a database, understanding where optimization suggestions come from, blocking a destructive migration before it merges, and operating the control plane.

Praxion Engineering · updated September 2026

Getting started

Start here if you have not connected anything yet.

Getting started Quickstart: connect your first Postgres database Run the Praxion agent inside your own network with Docker or the native binary, point it at a read-only Postgres replica, and register the database in the dashboard. No inbound ports, no VPN. 5 min read · Sep 19, 2026

Using the product

What the suggestions mean and how to keep them safe in a pipeline.

Optimizer Optimizations: where the suggestions come from Where Praxion's Postgres optimization suggestions come from, what each one carries — table, type, predicted saving, confidence, DDL — and how to verify one before and after you apply it. → Optimizations CI/CD CI Gate: stop a destructive migration before it merges Add the Praxion CI gate to your GitHub Actions or GitLab CI pipeline so a pull request that drops a table, a column or an index is blocked before it merges. → CI gate

Operating the control plane

Runbooks for the hosted side — the part you never install.

Runbook Supabase Runbook: control-plane Postgres & RLS Operate the Praxion control-plane database on Supabase: forced Row Level Security across 9 tables, the agent-fed pattern, migrations, and troubleshooting. → Supabase runbook Runbook Clerk Runbook: Organizations, SSO & RBAC Operate Praxion workspaces with Clerk Organizations: SSO setup, role_mappings, RBAC, member lifecycle, and troubleshooting for the Clerk↔Praxion mapping. → Clerk runbook

Field notes

Written by the engineers who build Praxion.

How to Find Slow Postgres Queries with pg_stat_statementsQuery optimization · 9 min Postgres Index Optimization: A Practical GuideQuery optimization · 8 min How to Read EXPLAIN ANALYZE: A Postgres Query Plan PrimerQuery optimization · 9 min Text-to-SQL with Guardrails: Let Your Team Query Postgres SafelyText-to-SQL · 8 min Monitoring On-Prem Postgres Without a SaaS AgentArchitecture · 7 min
Security and compliance documentation lives with the legal pages: the Security & Trust overview, the Data Processing Agreement and the Privacy Policy.

Stuck? Real humans reply.

Questions about your setup? Write to us and we will get back within one business day.

Contact support → All contact options →