Roadmap

Where we are, what's next, what's later. We'd rather undersell than lie.

Now
  • seele.agency is live. This site, security disclosures, and the public docs mirror are kept current.
  • Mobile apps (iOS / Android) — closed beta. TestFlight and Play Console internal track. Built from an internal tree; source is not published. We'll tell you when this changes.
  • Internal tooling (cluster-hub) — private. Running on our side. Not a product yet; no signup, no public API. We're using it to ship everything above.
  • TabMind v0.7.0 shipped. 4-page capture, full DOM capture, performance budgets, GPG signing pipeline. Download.
  • Security disclosure program live. /.well-known/security.txt + security@seele.agency + critic-agent automatic review (daily 07:55 cron). Bug bounty pool: 3% of revenue, kicks in once revenue exists.
Next
  • v0.8.0 — Knowledge graph + multi-device sync. KG linker (TF-IDF cosine over titles + tags), 4-provider capture (Grok / Claude / ChatGPT / Gemini), AES-256-GCM sync, signed release. Backend endpoints live on cluster-hub: /api/kg/*, /api/sync/*.
  • Public docs at docs.seele.agency. Moving from "good enough for the team" to "good enough for anyone reading." Starting point: /docs.html with 3 priority pages (getting-started, providers, security). Will move to a proper doc framework when the docs outgrow flat HTML.
  • Mobile TestFlight expansion. Invites go out in waves. No public App Store timeline yet. Codemagic CI + signing setup guide published; first internal build pending Play Store + App Store Connect hookup.
  • CF cache bypass. Workers-based seele-fresh ready to deploy — bypasses stale Cloudflare cache by proxying GitHub Pages origin. Track issue.
Later
  • Open API access. Not in product yet. We'll publish a roadmap entry here with a real date before we open anything.
  • Mobile source policy under review. Today's call is proprietary; we may revisit once the shipped binary and the public repo stop drifting.
  • Self-host or partner deployments. A frequent ask. Nothing concrete. We'll announce here if it moves from "we've heard you" to "we're building it."