SkyDrive.

The software skydiving runs on.

Dropzones, jumpers, tandem video and parachute rigging each have their own software. None of it talks to each other. SkyDrive is one suite built for all four.

In active development β€” first product in testing

The principle

Automate the paperwork. Never make the safety call.

Every decision that could hurt someone β€” pull altitude, breakoff, the spot, canopy choice, whether to jump at all, whether footage shows a malfunction β€” stays with qualified humans. SkyDrive surfaces data; it does not advise.

That isn't a disclaimer bolted onto the bottom of a page. It's an architectural rule: no screen in any of these products is allowed to read as a recommendation, and safety-adjacent behaviour is never gamified.

What's being built

Four products, one suite.

Each one stands on its own β€” no product requires another to do its job. They share a login and speak to each other when you want them to, and work fine when you don't.

Status labels are current and kept honest. β€œIn testing” means real code being exercised against real workflows, not a public release β€” nothing here is available to buy yet. Every card above opens the thing it names: a test build or a preview, running on sample data, with nothing you enter kept. None of them is a finished product and none pretends to be.

Why

Every slice of this sport has software. None of it fits together.

A jumper's logbook doesn't know what the manifest put them on. The video team re-types what the front desk already entered. A rigger's seal doesn't connect to the gear record anyone else can see. Everyone re-enters the same information, all weekend, every weekend.

The work is unglamorous and the details matter enormously β€” which is precisely why it's worth building properly, and building once.