8000 Epic: consolidate vector store and local SQLite onto Turso (retire Qdrant Docker) · Issue #49 · simon-inkie/inkie-the-brain · GitHub
[go: up one dir, main page]

Skip to content

Epic: consolidate vector store and local SQLite onto Turso (retire Qdrant Docker) #49

Open

Description

@simon-inkie

Original Linear description

Idea (the maintainer, 8 Nov 2026)

Move everything into Turso so we no longer need a separate vector store (Qdrant, which runs in Docker) and so the SQLite stores used by Mission Control / Inkie Deck run through it too.

Why

  • Qdrant in Docker is a poor fit for an installable product, and hard to back up.
  • A SQLite-style database is a single file/blob that is easy to back up and move.
  • One store for brain memory (recall), Deck state and queues.

Questions to answer first

  1. How good is Turso's native vector search (index types, dimensions, recall, speed, filtering, scale)? Reference: https://turso.tech/blog/turso-brings-native-vector-search-to-sqlite
  2. What does migration from Qdrant look like (collections, payload indexes, embeddings re-use, dual-write/cutover, rollback)?
  3. Backup/restore story, Windows installer fit (no Docker), embedded vs server mode, maturity/licence.
  4. Can the existing recall CLI (the-brain search) and Deck SQLite usage move behind one interface?

Status

Research brief only. Tooling freeze applies: spec and hand over, do not build. A Sol research worker has been asked for a findings note.

Origin

Migrated from Linear: INK-985. The original wording is retained except the disclosed privacy and rendering edits below.

Current scope and qualifications

The description above is the original Linear account, including its historical findings and scope. It is not a fresh claim that every described defect still exists.
Current Linear state is Backlog. Prior source review recorded uncertain, with this remaining scope:

  • Review complete research findings and settle store decision; keep Deck dependency explicit.

Publication transfers the task; it does not authorise live recovery, deployment, spending or configuration changes.

  • Additional transfer edits: omit added excluded programme references.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestmajor-featureA substantial feature or new capability

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0