Parachute Daily: Future Roadmap (API access, migration, billing)

[unforced]

Parachute Daily — Future Roadmap

Post-v1 features and infrastructure for Parachute Daily. Parent brainstorm: #344.

API Token Access

Give users an API token to access their Daily graph directly. This enables "bring your own AI" — use your Daily data from Claude, ChatGPT, or any MCP-compatible client.

• Expose read/write tools as MCP-compatible endpoints on the user's DO
• Tools: search_notes, read_note, list_days, read_reflection, write_note
• Same tool interface that Daily's internal agents use, just exposed externally
• API key management in settings

Migration Tooling (Daily → Computer)

Easy path from hosted Daily to Parachute Computer (self-hosted or hosted VM):

• Export from DO SQLite (notes, cards, agent configs, runs, tags) as portable format
• Import into Kuzu on Computer instance
• Audio migration from R2 to local vault
• Guided flow in both apps

Hosted Parachute Computer

Full Computer experience without self-hosting, likely Fly.io:

• Full Python/FastAPI server with Kuzu, Claude SDK, module system
• Persistent volume per user, scale-to-zero VMs
• Different infrastructure from Daily (that's intentional)
• For users who outgrow Daily's agent capabilities

Billing / Stripe Integration

• Free tier with limits (TBD: storage? entries? agent runs?)
• Paid tier via Stripe
• Subscription management in settings

Offline Mode

• Pending queue for entries created without connectivity
• Cached recent entries for offline reading
• Sync on reconnect

Additional Entry Types

• Photo entries
• Handwriting entries (Apple Pencil, stylus)

Brain Integration

• Entity extraction from journal entries
• Graph traversal across entries (themes, people, places over time)
• Requires either Kuzu on a sidecar service or graph-on-SQLite extensions