Nothing to provision
No cluster to size and no idle spend between queries. Sign in with Google or GitHub and run your first query in the browser.
Opteryx queries files in S3 and GCS, Iceberg tables and PostgreSQL databases in place — no loading, no cluster to run. Your data lake is already there. Start querying it.
Three commitments you can check for yourself on the free plan.
No cluster to size and no idle spend between queries. Sign in with Google or GitHub and run your first query in the browser.
Grant access per identity with glob patterns over schema.table, scoped to a workspace. Issue and revoke tokens for machine access.
The free allowance is a quota, not a credit. Without a billing account, usage past the limit is blocked, never billed.
Editor, results, charts and history in one place. Nothing to install.
This query is real. Sign in, paste it, and it runs on the free plan.
-- Exoplanet discoveries per year SELECT disc_year, COUNT(*) AS planets FROM public.astronomy.exoplanets WHERE disc_year >= 2017 GROUP BY disc_year ORDER BY disc_year; -- 10 rows · 6,324 scanned
Query a bucket, a catalog or a database in place, or upload files. Everything Studio does is also an API you can call.
No seats, no reserved capacity, no minimum. Add a billing account when you outgrow the free allowance.
Resets daily. Unused allowance doesn’t carry over.
Shared across all your workspaces. Without a billing account, usage past it is blocked, never charged.
Start freeBeyond the free allowance, per unit, in GBP excluding VAT.
About £4 per terabyte scanned and £0.02 per GB stored per month, with every charge attributed to the query that made it.
Read the cost model# pip install opteryx-core import opteryx # the same engine, over a file on your disk result = opteryx.query( "SELECT * FROM 'space_missions.parquet' LIMIT 5;" ) result.head()
Run the same engine yourself over local files, dataframes or object storage, with no cluster and no schema to declare. It’s Apache-2.0 and stays that way.
The hosted service adds storage, sign-in, access policies, metering and Studio. The SQL is the same in both.
Sign in with Google or GitHub, then point at your data or start with the sample datasets.