Embedded libSQL/SQLite databases with optional Turso Cloud edge replication
Turso documents libSQL—an open-source SQLite fork—and the Turso CLI (`tursodb`) at docs.turso.tech for embedded, local-first SQLite databases with optional Turso Cloud hosting for multi-region replication. Official guides cover installing the CLI (`curl -sSL tur.so/install | sh`), opening `.db` files or `:memory:` databases, schema migrations, and vector search extensions described in the Turso documentation index. Turso Cloud adds managed groups, database tokens, and HTTP/libSQL remote URLs provisioned through the Turso dashboard and `turso` CLI commands (`turso db create`, `turso db tokens create`) per quickstart pages.
Use cases
- Shipping offline-capable agents that persist state in embedded SQLite files
- Replicating lightweight app databases to Turso Cloud regions for low-latency reads
- Prototyping RAG or catalog features with local vector tables before scaling hosted replicas
- Teaching teams libSQL migrations without standing up full Postgres clusters
- Pairing Turso MCP with coding agents for schema-aware SQL iteration
Key features
- Local-first SQLite-compatible storage via `tursodb` and libSQL per Turso CLI documentation
- Optional Turso Cloud replication with database URLs and auth tokens managed in the dashboard/CLI
- Built-in MCP server mode (`tursodb path/to.db --mcp`) documented for agent database tooling
- Vector search and schema tooling described in Turso docs for AI-adjacent app stacks
- Git-friendly single-file databases suitable for edge and mobile deployments
Who Is It For?
- Developers building edge or mobile apps with SQLite ergonomics
- Platform engineers evaluating lightweight state stores for agent workflows
- Teams migrating from file-based SQLite to managed Turso Cloud groups
Frequently Asked Questions
- Is Turso only a hosted cloud database?
- No—Turso documents open-source embedded libSQL via the CLI plus optional Turso Cloud hosting; many workflows start with local `.db` files.
- How do agents connect to Turso databases?
- Turso documents a built-in MCP mode on `tursodb --mcp` and Turso Cloud URLs/tokens for remote libSQL clients—see docs.turso.tech agent/MCP sections.
- Where are pricing details?
- Turso publishes Turso Cloud plan tiers at turso.tech/pricing; embedded libSQL usage is open source without cloud fees.
Related
Related
3 Indexed items
Chroma
Chroma documents an open-source embedding database at docs.trychroma.com for storing and querying vectors, metadata, and full-text fields in Python and JavaScript clients. Official guides cover ephemeral in-memory collections, persistent local storage, self-hosted server deployments, and Chroma Cloud at trychroma.com with authentication tokens. The docs describe collection CRUD, `add`/`query`/`get`/`update`/`delete` APIs, embedding functions (default and third-party), hybrid search, and multitenancy patterns for RAG and agent memory workloads per the documentation index.
LanceDB
LanceDB documents a multimodal lakehouse for AI at docs.lancedb.com, built on the open-source Lance columnar format for storing vectors, metadata, raw bytes, and embeddings in unified tables. LanceDB OSS is an embedded library with Python, TypeScript, and Rust SDKs for local development; LanceDB Enterprise is a distributed managed lakehouse for search, curation, feature engineering, and training workflows per docs.lancedb.com. Features include vector/semantic search, BM25 full-text search, hybrid search with SQL filters, versioning, and cloud object-store integration (S3, GCS, Azure).
Voyage AI
Voyage AI documents state-of-the-art embedding models and rerankers at docs.voyageai.com for retrieval-augmented generation and semantic search. The embeddings API at POST https://api.voyageai.com/v1/embeddings converts text into dense vectors; the Python `voyageai` package exposes `voyageai.Client.embed()` with models such as voyage-4-large, voyage-4, voyage-4-lite, voyage-code-3, and domain-specific variants per docs.voyageai.com/docs/embeddings. Docs describe `input_type` query vs document prompts for retrieval tasks, optional `output_dimension` (256–2048), and `output_dtype` quantization (float, int8, binary). Rerankers score query–document relevance to refine initial retrieval results. Voyage AI is part of MongoDB's AI stack (MongoDB docs reference Voyage embeddings) and integrates with vector stores and LLMs as modular RAG components.