For aerospace & space
From hangarto deep-space relay.
Mission, Propulsion, Life Support, Comms, and Aviation share one telemetry intake, one anomaly substrate, and one set of books. Pathfinder I seed data ships with every module — open the page and the math is already running.
- Tsiolkovsky-on-trigger Δv accounting
- Friis link-budget calculator (live)
- ECLSS severity → auto-anomaly fan-out
- Vehicle transfer between programs by reference
Replace Your Stack
One platform. Built for flight.
Mission ops, comms, ECLSS, propulsion, and atmospheric MX — replaced by modules in Turtini.
Turtini charges $79 a month for your first 5 people, falling to about $3 per person as an organization grows. Every module is included at every tier, and we take no share of what you collect — your customers pay a merchant account in your name.
How it fits
Built for how flight programs actually run.
Mission Coordination
Flight history, anomalies, comms passes, and abort feasibility — one view.
Mission is the coordination OS — a vehicle (Pathfinder I in the seed) carries flight history, anomalies, planned events, and partner-view exports. onMissionEventWritten auto-stamps MET (mission elapsed time) and writes flightHistory atomically. missionListPartnerView / transferMissionVehicle callables manage cross-org sharing without copying records.
Propulsion
Δv budget that recomputes on every burn.
Propulsion ships a live Δv tracker (budget vs expended vs reserved-for-aborts vs available). On a mission event, Tsiolkovsky-on-trigger computes actual Δv from mass-ratio + Isp, decrements propellant tanks by mixture ratio, and bumps engine cycle counts. Abort feasibility recomputes live as the margin moves — when an abort window closes, you see it.
Life Support / ECLSS
Severity escalation that creates anomalies before the crew sees red.
Life Support sits on every Mission vehicle (every record references missionVehicleId). Snapshot ingest reuses bridgeApiKeys for spacecraft telemetry. Severity-escalation triggers fan out to missionAnomalies; critical alarms auto-spawn anomalies. Weekly auto-burn-rate calculations project consumable depletion — O2, water, food — well before the projection becomes a problem.
Comms (Space Link)
Friis link budget + pass scheduling + outage anomalies.
Comms sits beneath Mission's pass scheduling. Interactive Friis link-budget calculator returns live verdict, margin, and achievable rate. Critical outages auto-spawn missionAnomalies. commsPredictPass derives next-pass timing from orbital elements. Pathfinder × Goldstone S-band seeder ships sample data so the module opens populated.
Aviation (Atmosphere)
FBO, flight school, charter — same platform, different mission profile.
Aviation is the atmospheric-flight tier — Part 91 GA owners, Part 135 charter, flight schools, FBO operators. Aircraft rosters, flight logs, MX with cycle/hour intervals, fuel tickets, dispatch, weight & balance. Maps primitive shared with Voyages, Field Service, and Sports.
Bridge API → Spacecraft Telemetry
The same primitive that streams from a wheelhouse streams from a spacecraft.
Bridge's telemetry intake pattern (bridgeApiKeys → snapshot writes) was generalized for Life Support and Comms. Whether the feed is engine vitals from a vessel, ECLSS sensors from a habitat, or downlink quality from a deep-space relay, it lands in the same hash-chained audit log with the same anomaly-fan-out semantics.
Shared substrate
The same primitives across every flight tier.
A vehicle, a telemetry snapshot, an anomaly, an audit log — the same shape whether the vehicle is a Cessna 172 on a flight-school dispatch or a deep-space probe on a Mars-orbit transfer.
Property-records-follow-property
Same pattern that runs Closings and Sports also runs Mission — the vehicle is canonical. Vehicle transfer between programs carries flight history, propellant accounting, and anomaly ledger by reference, never by copy.
Permissions over copies
Partner-view exports route through permissioned reads — never duplicated docs. Revoke a partner org, and they lose the view; the underlying record never moved.
Verified-by-Turtini reports
Every Mission Readiness Review, Anomaly Report, and Telemetry Summary PDF carries a Verified-by-Turtini QR + SHA-256, independently verifiable at /verify/:id — sufficient for FAR Part 450 / CSLA filings.
Common audit substrate
Aviation, Mission, Comms, Life Support, and Propulsion all write to the same hash-chained per-org audit log. The same query that surfaces an anomaly on Day 12 of a Pathfinder mission surfaces a discrepancy in a Part 135 maintenance entry.
Pathfinder seeders
Activating Mission, Comms, Life Support, or Propulsion seeds a Pathfinder I dataset on first run — vehicles, ground stations, sensors, flight events — so the module opens populated and you can see what fits before designing your own.
Open primitives
No proprietary message bus. Telemetry intake is Bridge API; downlink format is the same JSON other modules use. If you need to migrate off the platform tomorrow, every record exports through the same Bearer-authenticated REST API.
Ready to light the candle?
Create your org in minutes. Pathfinder seed data on first activation.