Start with one query
Add your SQL, database engine, version and goal. Keep the investigation focused on the problem you need to solve.
Private beta · MySQL & MariaDB
Understand your slow SQL before you change it.
Bring a SELECT query. TuningLens guides you through the schema, execution plan and index evidence needed to evaluate a change—and gives you a way to verify it.
No database connection. No automatic SQL execution.
One query. A clearer next step.
01 / YOUR QUERY
SELECT id, created_at
FROM orders
WHERE customer_id = 42
ORDER BY created_at DESC
LIMIT 20;Start with the evidence
What indexes exist, and which access path does the plan choose?
Schema & indexes
Execution plan
Next: test the change, compare the results.
Illustrative workflow · not a measured performance result
Built for developers investigating a slow queryMySQLMariaDBSELECT queries · guided evidence · human review
On our roadmap: PostgreSQL, Snowflake and Amazon Redshift. These engines are not available in the current beta.
A focused investigation
From “why is this slow?”
to a change you can evaluate.
Collect what matters next
Follow guided requests for schema, indexes and plan output. Understand why each piece of evidence matters.
Review, then verify
Review the reasoning and tradeoffs. Check result equivalence and measure the change in your own environment.
An example, not a promise
An index idea is the start of a test.
For the order-history query above, an index beginning with customer_id and created_at might help. That is a hypothesis until the schema, existing indexes and plan support it.
TuningLens keeps the query, submitted evidence and follow-up together in one case, so the next decision has context.
Before calling it an improvement
- Inspect the current schema and index definitions.
- Compare plans using representative inputs.
- Verify the returned results still meet the requirement.
- Measure timings and consider index storage and write cost.
No invented speedups. AI recommendations still need your review.
Share evidence, not database access
Your database stays under your control.
No database credentials required
You choose which SQL and diagnostic output to submit. TuningLens does not connect to your database or run the suggested changes.
Be deliberate about what you share
Submitted cases are stored, and SQL, messages and evidence are sent to our AI provider for analysis. Remove secrets, personal data and sensitive values first.
SQL tuning field guides
Build the evidence before choosing a fix.
Read a MySQL EXPLAIN plan
Learn what access types, keys, row estimates and Extra flags say—and what they do not prove.
Read the guideUse runtime plans safely
Understand when MySQL EXPLAIN ANALYZE and MariaDB ANALYZE execute a statement before you run them.
Review the safety guideFollow a complete workflow
Move from symptoms to schema, plans, hypotheses and representative verification.
See the workflowBefore you begin
A few useful answers.
Which databases and queries are supported?
The current beta supports MySQL and MariaDB SELECT queries. PostgreSQL, Snowflake and Amazon Redshift support is planned, but those engines are not available yet. Include your engine and version because plans and diagnostic commands differ.
Will TuningLens change my database?
No. You collect the evidence and decide what to run. Runtime diagnostic commands can execute a query, so review them and use a suitable test environment.
Can it guarantee a faster query?
No. Suggestions depend on the evidence you provide. Verify correctness and measure performance with representative data before adopting a change.
How does private beta access work?
Create an account and confirm your email. An administrator reviews access requests before you can create tuning cases.
What does it cost?
Pricing is being evaluated during the private beta. There is no self-service paid plan or checkout in the current product.
Have a query worth investigating?
Bring the question.
Build the evidence.
Request beta access For developers and small teams working with MySQL or MariaDB.