Ask your cloud data anything.
OptiQL is a SQL workspace over everything CloudOptify knows about your clouds — cost, resources, tags, waste, recommendations and budgets, Azure and AWS together. Ask the question you actually have, see the answer as a chart, and share the query with your team.
1SELECT service_name, SUM(cost) AS cost2FROM service_daily_costs WHERE date >= date('now','-30 day')3GROUP BY service_name ORDER BY cost DESC LIMIT 10;
Write SQL → see the answer as a chart → save and share the query.
One query, both clouds
Cost, resources, tags, findings and budgets across Azure and AWS, reachable from a single editor.
Start from an example
Ready-made queries for common FinOps questions, and a schema browser that explains every field.
Answers as charts
Switch any result between a table, bar, line, share or headline number — then copy it or download CSV.
Save and share
Keep queries private, share them with named colleagues, or publish them to your whole organization.
The questions no dashboard quite answers.
Every FinOps team has a list of questions that never quite fit a dashboard. Answering them used to mean an export, a spreadsheet and an afternoon. With OptiQL, it’s a query.
Both clouds, one query.
OptiQL works over everything CloudOptify knows about your estate: daily cost by service and account, resources and their tags, waste findings, recommendations, budget alerts and cloud groups. Azure and AWS sit side by side, and every amount is already in one currency — so a single query compares both clouds without any stitching.
Not sure where to start? Ready-made examples cover common FinOps questions — top services, month-over-month spend per account, untagged resources, waste by category, tax and credits by month — and load with one click. A built-in schema browser explains every field, so you never have to guess what a column means.
See it, then share it.
A result is rarely the end of the conversation. Switch it between a table, a bar or line chart, a share breakdown or a single headline number — then copy it straight into a spreadsheet or download it as CSV.
The best queries get asked again. Save one and choose who can see it:
Only me
Keep it in your own library while you’re still working on it.
Specific people
Hand a colleague the exact analysis you ran — ready to open and run.
Everyone
Publish it to your whole organization and make it part of how the team works.
Shared queries run exactly as their author wrote them, chart included — so everyone looking at “untagged spend by account” sees the same numbers, calculated the same way.
Boring in all the right ways.
A SQL editor over live financial data should never surprise anyone. Every query runs read-only against an isolated copy of your organization’s data, built for that query and discarded afterwards. It never touches the live database, it can never see another organization’s data, and anything that would change data is refused with a clear explanation.