Auto Indexing
Stop Guessing Which
Postgres Index to Create
Slow queries, production regressions, and manual index tuning still eat engineering time because most teams do not know which index will actually help, when it is safe to apply, or how to validate the outcome. SelfHost is planning to analyze your live workload, recommend the right indexes with expected impact, and let your team approve safe changes before performance issues turn into incidents.
30s
GitLab reported query plans taking up to 30 seconds because a functional index was missing; with the index, execution dropped to a few milliseconds
Top 25
AWS native database insights default to top-25 SQL visibility, which is useful for diagnostics but incomplete for full workload tuning
Recommend only
Most PostgreSQL and MySQL advisor products still stop at surfacing DDL recommendations instead of owning safe execution
What a missing index actually costs
The same query. The same data. The only difference is a correctly-placed index.
Full sequential scan across every row - grows worse as your table grows
Direct index lookup - query time stays flat regardless of table size
What teams are actually fighting against
Most tools help you inspect. Very few help you decide and act safely.
Existing Tools
- Manual DBA tuning: Slow, fragmented, and hard to trust without deep provider knowledge
- ORM and schema defaults: Cover the obvious indexes but miss the workload-specific ones that actually slow production
- Cloud advisors and monitoring tools: surface missing-index recommendations, but usually leave validation, rollout, and rollback to your team
- Result: Teams keep shipping slow queries because acting on index advice feels riskier than leaving it alone
After SelfHost
- Continuous workload analysis across live query patterns
- Clear recommendation of which index to create and why it matters
- Approval-first rollout with safety checks before apply
- Before-and-after measurement so teams can verify impact with confidence
- Result: A safer, faster loop from slow query to measurable fix
How SelfHost is planning to solve this
Three layers. Every recommendation must be safe, measurable, and explainable.
Layer 1 of 3
Workload-Aware Detection
Always on. No configuration needed.
- Observe real slow queries and repeated access patterns across the workload, not just schema definitions
- Detect where missing or duplicate index candidates are affecting production performance
- Prioritize recommendations by likely impact, not just theoretical usefulness
What all is included
The full capability set, end to end.
Additional capabilities:
Help this reach further.
The more input we get, the better we build. Share this idea and bring in more voices.
25 votes so far
Vote if this is something you'd genuinely use and wouldn't mind paying a small fee for.
Browse
Other ideas to
explore.
Database Storage Downsizing
AWS locks storage at its peak - once autoscaling bumps up your volume, you pay for that size forever. SelfHost can shrink it back transparently, something RDS structurally cannot do.
Cost Monitoring
AWS Cost Anomaly Detection waits up to 24 hours. SelfHost flags active cost anomalies in 5-15 minutes, maps the likely culprit even with incomplete tags, and gives your team context to act before the bill compounds.
Database Cost Comparison
No tool combines performance benchmarks, instance pricing, and feature gaps in one place. Define your workload and see exactly what you would pay and get across every major provider.