Start here
Query the supplied samples, connect your own data, then build your hackathon project. Use the event page for registration, rules and submission details.
1. Check your prerequisites
You need the Zetaris website URL, your account and query permission.
| Access route | Start here |
|---|---|
| Supplied instance | Sign in using the details you've been given. |
| Your computer | Download from Zetaris Cloud's Run locally page, then follow Install locally. |
| Managed AWS cluster | Use Managed AWS cluster to connect your AWS account and create a Zetaris compute cluster from Zetaris Cloud. |
2. Run some SQL
Open the SQL Editor. Use connection choices if you prefer an assistant or script.
Follow your first SQL commands. Check execution, inspect tables and read the supplied NY Taxi and TPCDS samples. This step only needs query permission and creates nothing.
3. Try your first dataset
Optionally follow your first dataset to connect PokéAPI and query Pikachu's abilities. This step needs creation permission and your assigned team names. Zetaris must be able to reach the API.
Check the expected rows if you use this recipe. You can also build a project using only the supplied samples.
4. Choose what to build
Analyse data, combine sources, or build an app. Find additional sources in Cookbooks.
5. Prepare your demo
Use the demo template to save your SQL, results and steps someone else can reproduce. Check the event page for submission requirements.
Stuck? See troubleshooting. Change only your team's approved objects; leave shared sources and the platform running.
Start with your coding assistant
Open this repository in your assistant, choose a connection and review the prompt before sending it.
Use the getting-started repository at https://github.com/zetaris/getting-started as the workspace. If it is not checked out, help me clone and open it first. Read docs/connections/client-setup.md for setup. Keep credentials in .env.local, never in this prompt or a report.
Read AGENTS.md and follow it. Run python3 scripts/preflight.py --jdbc and show
me the result. Report JDBC and REST checks separately. Stop on JDBC failures and report
what is missing. REST failures alone do not block JDBC. If the driver JAR path is not set, ask me
for it. Once readiness checks pass, connect over JDBC to the instance
configured in .env.local and confirm with SELECT 1 and SHOW LIGHTNING DATABASES.
If a local port check returns `Operation not permitted`, retry the same
read-only check with approved network access before reporting the endpoint as
closed. Distinguish missing Python runner dependencies (`.venv` or
`jaydebeapi`) from direct Java JDBC readiness; do not install dependencies
without asking.
Goal: verify SQL execution, inspect the supplied NY_TAXI and TPCDS_DB tables, then run a sample SELECT with LIMIT 5. Do not create objects.
Dry-run before creating anything and wait for my go-ahead.Requires the desktop app. If it doesn't open, copy the prompt into your assistant. Configure .env.local first; JDBC also needs the matching driver JAR.