Roadmap

Here now

The self-hostable base shipped 2026-04-23 and has grown in steadily since. The four committed-core modules — Vault, Surface, Scribe, Hub — install with parachute install <service> (or all at once through the setup wizard).

• Parachute Vault — the knowledge graph. SQLite-backed, REST + MCP, wikilinks, full-text and semantic search, lossless portable-markdown export + import for git projection / disaster recovery / Obsidian round-trip, upsert-by-id on update-note, JSON int coercion in schema validation. A pure hub OAuth resource-server — the hub issues per-vault scoped tokens. Source →
• Parachute Surface — the UI host module; Notes ships bundled as its first canonical surface. Installable PWA, works offline, voice capture with auto-transcription, multi-vault (one install, every vault on your hub), hierarchical capture tags, schema-audit UI, global text-size scaling. Drop additional custom SPAs under the same supervisor. Source →
• Parachute Scribe — Whisper-compatible transcription API. Runs locally by default; BYO cloud provider if you want one. Source →
• Parachute Hub — the coordinator. install, start, stop, expose, lifecycle for every service. OAuth issuer with per-vault scopes and cross-origin approve flow that works across loopback, tailnet, and public layers. Multi-user hosting shipped (Phase 2, 2026-05-27): one admin, N users, each with their own vault(s). Source →
• Parachute Runner — vault-as-job-substrate. A lightweight runner that spawns claude -p against tag:job notes — owner-operated automation without standing up containers. Shipped; not yet promoted to committed-core. Source →
• Parachute Channel — messaging gateway that lets Claude Code agents reach you through Telegram, Discord, and other channels. Exploration; may retire if not pulled by real use. Source →
• v0.6 hosted self-host (just shipped) — two peer paths to an always-on hub on your own subdomain. Deploy to Render (GUI-first, ~$7/month) or Deploy to Fly (CLI-first, ~$3.34/month). Single container, hub-as-supervisor, persistent disk; modules install at runtime via the admin UI. Architecture note →

Next few weeks

Driven by what's blocking real users plus what we've named in since-launch's "still on the bench" section.

• Multi-user UX polish — multi-user hosting shipped (one admin, N users, each with their own vault(s); Phase 2 added multi-vault membership and admin-initiated password reset). Still ahead: self-service signup, invite links, and role granularity below admin/user — landing as people ask for them.
• Public HTTPS exposure + web-AI connectors — polishing the Tailscale Funnel and Cloudflare Tunnel paths, and the OAuth handshake for custom connectors in claude.ai, ChatGPT, and Gemini. parachute expose works today; we're smoothing the on-ramp before announcing broadly.
• Dashboard SDK — the "build a custom dashboard against the export format" pattern wants a small typed helper library. Today it's a recipe in the cookbook; tomorrow it's a package.
• Notes header polish — the popover landed; the chrome around it could be tighter. Pinned and archived views, the today view, path tree.
• Vault atomic tag operations — rename and merge tags cleanly across a whole vault in one request, so clients don't have to orchestrate it.

A little further out

• Parachute Cloud — the done-for-you hosted path: managed vault, multi-device sync, cloud transcription, no server to run. Same shape as self-hosted, same portability. Deployment sketch →
• Native mobile wrapper — a Capacitor- or Tauri-wrapped build of Notes that unlocks background recording, on-device offline transcription, and pendant integration on phones. The PWA handles most of what most people need; the native wrapper handles the things a browser can't.
• Configuration portal — the hub page renders per-module settings forms automatically from each module's JSON Schema. You won't need the CLI for most config changes.
• Fine-grained scopes — clients ask for exactly what they need (read-only, read-write, per-vault, eventually per-folder). Foundation for third-party modules that users can trust partially.
• Pendant — always-on voice capture hardware, writing directly to your vault. Prototype PCB and enclosure exist; a shippable v1 comes through the native-wrapper path.

Longer arc

Parachute is open-source and modular on purpose. The longer arc is less a timeline and more a shape: an ecosystem of small, composable modules that all speak a common contract, so you can mix the official ones with community ones with your own. The canonical architecture lives in the design notes.

• Third-party modules — anyone can build a service that plugs into a Parachute hub. Calendar, email, chat, custom agents. The hub renders them like they were native.
• AI reflections — longer-horizon synthesis over your vault (weekly digests, patterns across time), as a module you choose to install rather than a built-in.