Turso
Also known as: Turso Database, Turso Cloud, libSQL
Turso gives developers a way to provision separate SQLite compatible databases for the agents they run. Each database can keep state, application records and embeddings, so a buyer can retrieve relevant material with SQL. The open source engine runs inside applications, while Turso Cloud handles hosted databases and regional placement. Developers control how each agent reads and writes its own store.
Turso is a SQLite compatible database engine and managed database service. Developers can give each agent, user or project its own database, which isolates each workload at the database level. An agent can use that database to save facts and record the progress of a long job. The application can provision the database through the Platform API, then issue a token restricted to that database. The underlying engine is written in Rust and supports concurrent writes. Turso’s open source engine can run locally, on a device or in a WebAssembly application, and its hosted service supports embedded replication for applications that also need an on device copy.
Turso stores vector embeddings alongside the rest of a database’s data. An index updates when a developer inserts rows, and SQL can retrieve related entries while applying filters on their attributes. An agent can use a dedicated database as its memory between sessions.
Memelord, an open source memory system for coding agents written by Turso's founder, gives each project its own Turso file, recalls related memories at the start of a task, lets the agent rate them afterward and drops ones that stop being useful or turn out wrong. The application that owns the file controls how long it keeps that data. Turso can branch a database to give experimental work a separate copy of the state and offers restoration options through the cloud service.
Cloud Developer costs $5.99 monthly or $4.99 per month on an annual term. That plan includes unlimited databases, 9 GB of storage, 2.5 billion rows read, 25 million rows written and 10 GB of sync each month. Customers can enable usage charges at published rates. Scaler costs $29 monthly and Pro costs $499. The free plan is available without a credit card. Hosted groups can have a selected primary region. Turso Cloud has a SOC 2 Type II report, and users can create database tokens with expiration and read only access.
At Engine Labs, the CTO.new platform gives teams of coding agents a Turso database per project. It ran tens of thousands of databases, supported more than 50,000 users and used a $500 monthly plan in that deployment. An application can check a project’s stored work status without starting the agent’s sandbox. Developers can also use Turso’s MCP server to expose an embedded database to an assistant for SQL queries and schema changes. Supabase announced on October 2, 2026 that it is acquiring Turso, with Turso's founders joining Supabase to lead its agent infrastructure work. Turso Cloud keeps running under the Turso name, and the open source database remains in active development.
Vendor details
Canonical URL
https://turso.tech/
Category
Agent infrastructure
Subcategory
Isolated databases for agent state and retrieval
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
SQLite compatible libraries, Platform API, Turso CLI and MCP access for embedded databases. Libraries and connectors include JavaScript and Rust.
In practice
A coding agent retrieves relevant project memories from a dedicated local database at the start of a new session.
A platform creates a database for each agent team and lets the application check task status while the agent’s sandbox is stopped.
An application developer branches a project database to try a change to the agent’s working state before applying it to live data.
Sources & related URLs
Research sources
Agentic Index coverage score
6.0 / 14 capabilities · 43%
| Integrations & Tool Calling | Not documented |
|---|---|
|
Turso exposes database operations to applications that connect through a compatible library, HTTP or a WebSocket. A buyer can give its own agent permission to query or change a database as part of its work. The connection terminates at Turso. External system actions are carried out by the agent’s host, using the business tools configured in that application. Sourceturso.tech/productread 2026-11-20 |
|
| Workflow Orchestration | Not documented |
|
At CTO.new, an agent team uses a separate project database to track what work is running and inspect progress while its sandbox is inactive. The database stores the task state and makes it available to the application. The buyer’s agent platform creates and assigns the work, manages the project and decides when to start or stop its execution environment. Sourceturso.tech/blog/cto-new-coordinates-tens-of-thousands-of-ai-agentsread 2026-11-20 |
|
| Knowledge Grounding & RAG | Full |
|
The database can maintain a vector index alongside the customer’s documents or records. Inserts update the index and SQL can retrieve nearest matches together with their stored properties. A developer can query the index across runs and use ordinary filters on the associated records. The same database can hold the embeddings and the text or metadata needed to construct agent context. Sourceturso.tech/vectorread 2026-11-20 |
|
| Human Oversight & Guardrails | Not documented |
|
A buyer can restrict an agent to a specific database and issue a credential that permits reads only. It can also issue a time limited token for a temporary task on a particular database. These settings apply every time the credential is used. The buyer’s agent application owns decisions about reviewing a proposed change before it makes an authorized database request. Sourcedocs.turso.tech/cli/db/tokens/createread 2026-11-20 |
|
| Security, Identity & Governance | Full |
|
Turso Cloud has SOC 2 Type II assurance and supports separate credentials for individual databases. An owner can issue a read only token or set an expiration. Deployments can keep agent work in different databases and can apply per database encryption. Customers that use their own keys keep control of the key material for supported encrypted deployments. Sourceturso.tech/solutions/securityread 2026-11-20 |
|
| Observability & Auditability | Partial |
|
Cloud audit logs and change data capture help a team trace access and modifications within the database service. Developers can inspect which data was changed or retain their own records of an agent’s activity in a project database. Turso observes the storage service and its operations. An agent’s decision trace comes from the application that sends those operations. Sourceturso.tech/solutions/securityread 2026-11-20 |
|
| Memory & State Persistence | Partial |
|
A project can keep an agent's memory in its own Turso database, and later sessions can read what earlier ones wrote. The memory logic in the pattern Turso sets out lives in Memelord, an open source package by Turso's founder that writes facts at task end, recalls them at the start of the next session and retires stale ones. Turso itself supplies the store that the buyer's code or tool reads and writes. The buyer can delete one project's database without touching any other. Sourceturso.tech/blog/how-to-build-a-retrieval-system-for-agentsread 2026-11-20 |
|
| Deployment & Data Residency | Full |
|
Teams can select the primary location when they provision a group of hosted databases. The cloud service can keep a copy synchronized with an embedded database. The open source engine also runs on infrastructure the buyer controls, including a local service or device. An application can hold an entirely local working database when the work requires local storage. Sourcedocs.turso.tech/cli/group/createread 2026-11-20 |
|
| Prebuilt Agents / Templates / Packs | Partial |
|
Developers can provision agent databases using a shared schema template and give each agent an isolated working store. A team supplies the schema and specifies the information it needs each agent to keep. A newly provisioned database can then use that structure while holding records for one project. The installed agent logic belongs to the developer’s application. Sourceturso.tech/solutions/ai-agentsread 2026-11-20 |
|
| Triggers & Channel Coverage | Not documented |
|
Creating a database supplies a resource to an application using the Turso API. A developer can provision the database when their own application creates an agent or opens a new project. When the agent runs, its application can query the database and update its state. The application’s scheduler or event handling determines when the agent itself receives work. Sourcedocs.turso.tech/api-reference/databases/createread 2026-11-20 |
|
| Model Flexibility & Routing | Not documented |
|
Turso can store vector representations created by a buyer’s embedding model and search them in the same database as application records. The developer decides how to create the embeddings and which reasoning service their application uses. The database receives the vectors and queries used for retrieval. The reasoning model handles the agent’s assignment in the developer’s application. Sourceturso.tech/vectorread 2026-11-20 |
|
| APIs / SDKs / MCP Extensibility | Full |
|
The Platform API lets a developer create a database in an organization through an authenticated request. It also has endpoints for database credentials and locations. Developers can use Turso’s database interface from their own service. An embedded database can expose MCP tools to an outside assistant to read available tables, inspect their columns and change the schema. Sourcedocs.turso.tech/api-reference/databases/createread 2026-11-20 |
|
| Testing, Debugging & Optimization | Partial |
|
A developer can branch a database to try a change with a copy of an agent’s state and leave the live database available. A branch is separate from its origin. A team can discard it when the experiment ends or transfer an accepted schema change with its migration tools. Test prompts, scores and judgments are managed by the buyer’s agent application. Sourcedocs.turso.tech/features/branchingread 2026-11-20 |
|
| Browser / Computer-use | Not documented |
|
The database engine can run inside a web application through WebAssembly. That application can keep records or embeddings locally on the device and query them there. This places the database inside the web application. It leaves navigation of outside websites to whatever interface tools the developer equips their agent with in its separate execution environment. Sourceturso.tech/productread 2026-11-20 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
$5.99/month or $4.99/month billed annually
Monthly plan with storage, rows read, rows written and sync allowances
Included quota
Developer includes unlimited databases, 9 GB of storage, 2.5 billion rows read, 25 million rows written and 10 GB of sync per month.
What is public
Developer is $5.99 per month or $4.99 with annual billing. Scaler is $29 monthly or $24.92 with annual billing. Pro is $499 monthly or $416.58 with annual billing. The Free plan costs $0.
Billing mechanics
Developer includes 9 GB of storage, 2.5 billion rows read, 25 million rows written and 10 GB of sync per month. Extra usage can be billed at published rates when enabled.
Variable cost rationale
When overages are enabled, storing additional data and increasing query, write or synchronization activity can add charges above the subscription fee.
Overage / add-ons
Developer charges $0.75 per additional GB stored, $1 per billion rows read, $1 per million rows written and $0.35 per GB synced when overages are enabled.
Sales call required
Mixed (some tiers require a call)
Free / trial
Free cloud plan without a credit card
Lowest paid plan
Developer
Commercial notes
Hosted databases that are idle use storage. Database branching and point in time restores carry no separate usage charge.
Missing data
Enterprise terms are quoted.
Related vendors
- AgentOps — Agent observability and debugging platform: open source SDKs trace…
- AgentPhone — AgentPhone gives the AI agents a team builds their own US or…
- Agno — Python agent framework and AgentOS runtime (formerly Phidata) for…
- Airbyte — Airbyte moves data from operational systems into warehouses and…
- AIsa — Resource and payment gateway for AI agents, with one key to 110+…
- Albato — Albato is a no code integration platform that sells an embedded,…
Alternatives to Turso
Other products that do the work Turso does, and what each one is.
- Corellium
- HyperspellCompany brain for AI agents
- Airbyte
- Deeplake
- Rime
- SpeechmaticsSpeech to text and text to speech APIs for voice agents and transcription