FAQ
Is my data sent anywhere?
By default, no. The configurator and plan analyzer run as WebAssembly inside your browser tab. Pasted plans, hardware specs, and generated configs never leave your device. See the privacy policy for the full story.
Can I use this offline?
Yes — once you've loaded the page once, the WASM is cached. You can disconnect and everything keeps working until you reload.
How accurate are the recommendations?
Each parameter value is derived from public PostgreSQL practice and our 25+ years of running PostgreSQL in production. They are defensible defaults, not custom advice — for that, you need to know the workload, the data distribution, the application access patterns, and the failure modes that matter to you. Always test in non-production before applying anything to production.
Why does the configurator say to enable pg_stat_statements?
Because once you have it, you can answer almost every “what's slow?” question with a single query. It has negligible overhead and is universally recommended for production PostgreSQL.
How do I apply a change that requires a restart?
The configurator marks each value with one of: live (reload via SELECT pg_reload_conf();), restart (full PostgreSQL restart needed), or careful (live-reloadable but watch resource cost). The download includes a README explaining the workflow.
What PostgreSQL versions are supported?
13 through 18. Some parameters were renamed or got new defaults across versions — the tool handles those automatically.
Is there an API?
Yes — POST /api/v1/generate, POST /api/v1/render, POST /api/v1/analyze. See the repo for the endpoint contract. Rate-limited to 60 requests/minute/IP. If you need higher limits, get in touch.
Is the code open source?
Yes — the Go engine and the Next.js app are both in the same public repository. Audit the rules, the parser, the WASM build — everything.
Can I self-host this?
Yes — there's a docker-compose.yml at the repo root. See the README for instructions. The application is stateless so deploying it is trivial.
I found a bug / want a new detector
File an issue on the GitHub repo, or use the contact form. We read everything.