Groundrush

Groundrush

Logbook. Progression. Readiness.

Every skydiving logbook records what you did. Groundrush answers the question that actually matters at the dropzone: can I do this jump, and what am I missing?

In development

The logbook is an input, not an archive

There are good logbook apps already, and they all do the same thing well: they store jumps. Groundrush stores them so a competency engine can read them.

Enter a jump and the engine re-reads your whole record against the requirements for whatever you are working toward — a licence, a rating, a jump someone offered you on tomorrow's load. It tells you what you have, what you are short of, and by how much.

“You have 43 of 50 jumps, 8 of 10 formation jumps, and no night jump yet.”
Not “you have 43 jumps.”

Sourced, or marked as unverified

Every requirement in the catalogue carries a link to the document it came from and a flag for whether a human has checked it. Where a source publishes two values — 33 feet (10 metres) — both are stored as published, because 33 ft is not 10 m and converting one into the other moves the threshold.

Statistics that cannot be derived honestly are not produced. There is no world ranking and no percentile, because we cannot see everyone's logbook and will not pretend otherwise.

Private by default

Having an account does not mean your jumps are shared. Every record is born private. A jump's exact coordinates say where you live and how you spend your weekends, so they stay on the device — what gets shared is rounded to the dropzone. Photo metadata is stripped on the server, because a client can be modified and a promise you cannot verify is not a promise.

Tagging someone needs their approval. A tag nobody approved records where a person was without asking them, so it stays a private note on the tagger's side until they say yes.

BASE is a personal record

BASE is not the skydiving model with a different label. No reserve, no licence ladder, altitude measured to the ground. It gets its own data model and its own idea of progress.

The app never asks whether a jump was permitted, and there is no field to record it — that answer is useless to you and useful to someone else. Objects are your own private cards, not a shared catalogue; nothing is suggested, listed, or mapped. BASE data syncs end-to-end encrypted under a password that never reaches the server, so no readable exit-point database exists for anyone to ask for.

Built for where it is used

Three taps

Friction is what kills logbook apps. Logging a jump is three taps, and the rest is optional.

Works offline

Dropzones have no signal. Everything works without a connection and syncs when there is one.

Correct units

Feet or metres follows the dropzone and your preference. A wrong altitude unit is a safety problem, not a formatting one.

Yours to take

Full export in the first release. A logbook you cannot get out of an app is not your logbook.

Six languages

English, Turkish, Spanish, German, French and Russian. Sport terminology stays in the sport's own words.

No feed

No posts, likes, comments or follows. The activity that shows up is jumps, milestones and licences — the engine's output.