Choose your deployment

Piranha runs three ways. Pick based on where your meets happen and your network.

Hosted (server)

A FastAPI backend serving the built web app, on SQLite or Postgres, reachable over the network. Best for a league that wants one always-on instance multiple clubs share. Deploys to any host that can run the app and serve static files (e.g. Render).

Desktop (offline-first)

A native app (Tauri) that bundles the backend as a local “engine” and serves everything over loopback. Built for deck day: the timing-console connection, zeroconf discovery, and .gen ingestion are all local, so flaky venue wifi is never on the critical path. This is the right choice for the box on the pool deck.

Local

Run the backend and web app directly on one machine for development or a single-operator setup. Zero-config on SQLite.

Which should I use?

• One club, on the deck, unreliable wifi → Desktop.
• A league sharing one instance → Hosted (Postgres recommended under load).
• Trying it out / developing → Local.

Next: Install & first run.