Try Opteryx

Your First Query

Pick whichever way in suits you. Each one ends with a real result on screen in a couple of minutes, and none of them needs a cluster, a credit card or any configuration.

  • Hosted: sign in to opteryx.app and run SQL in the browser.
  • No account: read a public dataset over HTTP with curl. Nothing to sign up for.
  • Python: pip install opteryx-core and query from your own process. Nothing leaves your machine.

1. Sign in

Go to opteryx.app and sign in with Google, Microsoft or GitHub. There's no card to enter, and the free quota covers everything on this page. See Logging In if you get stuck.

2. Run the example query

Opteryx Studio opens with this query already in the editor. It reads public.astronomy.moons, a sample table every signed-in user can read:

SELECT
    planet,
    COUNT(*) AS moons
FROM
    public.astronomy.moons
GROUP BY ALL
ORDER BY
    moons DESC

Press Run (⌘↵ / Ctrl+Enter). The results grid shows the first rows:

text
planet   moons
Saturn      16
Jupiter      9
Neptune      8
Uranus       5
...

3. See how much data it read

The status bar under the results shows the row count, how long the query took and the bytes scanned. Bytes scanned is the data processed that Opteryx meters, so you can see how much each query reads as you go. See Cost Model.

4. Share it

Press Share, beside Run, for a link to the query in your editor. Whoever opens it gets the same SQL in their own editor, not yet run, and runs it with their own access, signing in first if they need to. The link shares the query, not your results, and only a single SELECT can be shared. The chart goes with it if you've set one up.

The same dialog gives you an Open in Opteryx badge as Markdown or HTML, for a README or a blog post:

text
[![Open in Opteryx](https://opteryx.app/img/open-in-opteryx.svg)](https://opteryx.app/studio/?q=…)

The ?q= part is the SQL compressed, so chat apps and Markdown editors leave the link intact. It isn't hidden: anyone can decode it, so keep secrets out of a query you share.

SQL examples in these docs that you can run as written have an Open in Studio button for the same reason: it opens that example in your editor, ready to run. Examples that use placeholder names like my_workspace don't, since they need your own names first.

Next Steps

Need Help?

If a step here didn't do what you expected, raise a bug or ask a question. Getting help covers what to include.