Docs
Reference material for the Parachute ecosystem
Parachute is open source. The most direct way to read about how it works is in the code itself — start with each repo's README.md. Below are the design notes that anchor architectural direction post-launch.
Architecture design notes
Written 2026-04-20 in the week before public launch, capturing the shape Parachute is evolving toward.
-
Module architecture
2026-04-20The canonical module protocol:
info,config,services.json,.well-known/parachute.json. How Vault, Lens, Scribe, and third-party modules plug into a single ecosystem under one HTTPS URL. -
Hub as portal — OAuth and the service catalog
2026-04-20OAuth architecture with the hub as issuer. One ecosystem sign-in, tokens carrying a service catalog, scopes that constrain what a client can reach.
-
Parachute Cloud — architecture sketch
2026-04-20Cloud deployment shape: tenant-per-subdomain, Postgres-backed, CDN-hosted Lens, pooled Scribe. A plausible north star we refine when a first cloud user materializes.
Per-repo READMEs
- parachute-hub — the coordinator:
install,start,stop,expose, and lifecycle for every module. - parachute-vault — the knowledge graph. REST + MCP, SQLite-backed.
- parachute-lens — browser-based companion for your vault. Installable PWA.
- parachute-scribe — Whisper-compatible transcription API.
- parachute-channel — messaging gateway for Claude Code agents.
- parachute-patterns — cross-repo conventions (naming, schemas, OAuth scopes, ports).
Want to follow along?
Read the blogOr see what's next.