Pick a path,
not a page.
The docs are a reference. These are routes through them: an ordered list of pages for the job you are doing, with a note on why each one is there, ending in an exercise you run against real data.
Answer questions with SQL in Studio
You write queries and want answers. Someone else worries about tables, tokens and pipelines.
Build tables that maintain themselves
You own the tables other people query: loading them, shaping them, keeping them fresh and controlling who sees what.
Call Opteryx from your own code
You are wiring Opteryx into an application, a notebook or a service, and you need auth, a client and a result you can work with.
Nothing to sign up for
No accounts, no badges. Every step is a page that already exists. Ticking steps off is remembered by this browser only.
Read in order
Each step assumes the ones before it. Skip a step if you already know the material, but do not reorder them.
Finish with your hands
Every path ends in an exercise on the public sample datasets, with a few questions to check the ideas stuck.
Not sure which path?
If you mostly write queries, start with Analyst. If you create tables other people read, Data engineer. If you are calling Opteryx from code, Developer. The paths cross-reference each other, so nothing is lost by picking wrong.
Or read When to use Opteryx first →