English
Deployment

Deployment models

One system, three shapes. Choose by your venue's network and how much you want to run yourself — and switch later without changing how the meet works.

Cloud + deck agent Diagram: poolside timing console connects to a small deck agent, which bridges over the network to the Piranha cloud; browsers on phones, tablets, and laptops connect to the cloud. results ▸ REST status ▸ WS LAN Timing console Deck agent ~9 MB Piranha cloud Browsers on deck
Good-network venues

Cloud + deck agent

Everything runs in the cloud. On deck, a ~9 MB agent does only the irreducibly-local jobs — hold the timing-console link and push results up.

  • Open the meet in any browser, on any device on site.
  • A tiny cross-platform agent bridges the poolside console to the cloud.
  • Results upload over HTTP; timer status streams live over WebSocket.
  • Nothing to install for staff — just sign in and run.

Reliable venue wifi or a hotspot that holds.

Desktop, fully offline Diagram: timing console, the Piranha engine, and a browser UI all run on one laptop over local loopback, with an optional later sync to the cloud. Deck laptop ● runs fully offline Timing console Piranha engine Browsers on deck loopback — no wifi on the critical path optional sync Piranha cloud
Flaky-wifi venues

Desktop, fully offline

The entire backend, frozen into a native app, runs on one laptop on the deck. Zero network on the critical path — the timing console, discovery, and .gen ingestion are all loopback-local.

  • One installer per OS (Windows, macOS, Linux) — double-click to run.
  • Timing console, results, seeding, scoring, exports — all on the box.
  • Wifi can drop entirely and the meet never notices.
  • All your data in one local SQLite file — copy it to back up or move it anywhere.

Venue wifi you can't trust — or none at all.

Local-cloud hybrid Diagram: a meet is checked out from the cloud to a deck laptop, run fully offline on deck, then checked back in to sync results to the cloud. Checkout Sync back Piranha cloud plan · seed · history ● runs fully offline Deck laptop
Best of both On the roadmap

Local-cloud hybrid

The planned best-of-both: plan and seed in the cloud, check the meet out to the deck laptop for race day, run it fully local, then sync the results back. Today the pieces already exist separately — cloud planning plus the offline desktop app; one-click checkout and sync is on the roadmap.

  • Check a meet out: the cloud hands deck-day ownership to the laptop.
  • Run entirely offline on deck with the full desktop engine.
  • Check it back in: results, times, and DQs sync to the cloud.
  • Athlete history and records update centrally the moment you sync.

Office planning + an unpredictable pool deck.

Which one fits your venue?

A rough guide — none of these lock you in. The meet model, data, and reports are identical across all three.

Model Best when… What runs locally Where data lives
Cloud + deck agent Reliable venue wifi or a hotspot that holds. Deck agent Piranha cloud
Desktop, fully offline Venue wifi you can't trust — or none at all. Piranha engine Deck laptop
Local-cloud hybrid Office planning + an unpredictable pool deck. Piranha engine Deck laptop → Piranha cloud