Edge / per-tenant SQLite for agents
Need many lightweight per-user or per-agent SQL databases at the edge (libSQL/SQLite), not a single Postgres or Redis cache.
At a glance — Oct 2026
Updated 2026-10-27 · forward this page: /jtbds/edge-sqlite-agent-db#briefScores as of 2026-09-14 (43 days old; Depot marks scores stale after 30 days). The pick is still Depot's current editorial pick; it has not been re-reviewed since. Prices below carry their own dates.
- Depot Pick
- Turso · 8.22/10 for this job (curated estimate, high confidence)
pricePerf + dx for numerous small DBs. Distinct from serverless-db (Postgres) and agent-memory-kv (Redis).
- Runner-up
- Cloudflare Workers · 8.53/10
Scores higher than the pick on: Capability fit, Price / performance, Latency / reliability, Maturity / track record.
- When not to use the pick
- Want shared serverless Postgres branching — Neon; Auth+Storage suite — Supabase; sub-ms shared KV — Redis.
- Lock-in / migration
- The pick has lower stored lock-in risk than runner-up Cloudflare Workers (3.6 vs 5.5). Self-host fallback listed for this job: SQLite, sqlite-vec.
- Sourced price (no comparable unit)
Pick: no sourced price in this job's unit (no_sourced_price).
No cheapest SKU (no_comparable_unit_for_job). No price was invented.
- Free option
- Failure modes to watch
- Schema drift: Validate every tool call and every loaded table against the current schema. Quarantine mismatches instead of coercing them.
- Identity confusion: Bind every tool call to a user or tenant id. Refuse the call if that id changed mid-task. For a public bot, the operator owns the words the bot shows.
- Context overflow: If the input exceeds the window, say so and retrieve a narrower slice. Do not answer from a truncated head as if it were the whole source.
- Lost in the middle: Ask the agent to name the passage it used. Spot-check questions whose only support sits in the middle of the context, not only at the edges.
- Non-determinism: Run the task more than once and compare the end state, not a single transcript. Record the trial count next to any success rate you cite.
- Silent truncation: Tools must return whether the payload was truncated and how long the original was. Fail the task if the answer depends on the missing span.
Cite: Agent Provider Depot, Depot Pick for edge-sqlite-agent-db: turso, scores as of 2026-09-14. Agents: GET /api/decide?jtbd=edge-sqlite-agent-db
Free Edge / per-tenant SQLite for agents options · for local-offline agents
Turso
pricePerf + dx for numerous small DBs. Distinct from serverless-db (Postgres) and agent-memory-kv (Redis).
Pricing (directional): As of 2026-09-14 (turso.tech/pricing): Free $0 — 100 DBs, 5GB storage, 500M rows read, 10M written, 3GB embedded sync, 1-day PITR. Developer $4.99/mo; Scaler $24.92/mo; Pro $416.58/mo (annual-save prices shown). Unlimited DBs on paid. Overa…
Lock-in risk: higher = more lock-in (worse). Overall already inverts this dimension.
Depot pick for edge/per-tenant SQLite agent state. Serverless Postgres pick stays Neon; hot KV stays Redis; pgvector RAG stays Supabase.
Quote for Edge / per-tenant SQLite for agents
Depot Pick stays Turso. Prices below are sourced SKU rows only (as of 2026-10-27). Input and output are not blended. GET /api/quote?jtbd=edge-sqlite-agent-db
Nothing was compared. no comparable sourced unit for this job; chat input $/1M and other units were not borrowed pickIsPriceWinner is null.
Sourced price unavailable for the Depot Pick. No row in the pricing index.
2 of 4 candidates have no sourced price row. 4 are excluded from the Matching price comparison (none). no comparable sourced unit for this job; chat input $/1M and other units were not borrowed
Runners-up
Cloudflare Workers
Best edge runtime for lightweight agent gateways and tools. Heavy LLM loops still belong on Modal/Fly/GPU…
Neon
Excellent serverless Postgres for agent apps that want branching + pgvector without Supabase's full BaaS.
Supabase (pgvector)
Depot default for most agent apps under ~25–50M vectors. Don't add Pinecone until Postgres actually hurts.
When NOT to use the top pick
Want shared serverless Postgres branching — Neon; Auth+Storage suite — Supabase; sub-ms shared KV — Redis.
Full ranking (score table)
Ranked with this JTBD's weights. Scores are curated estimates unless marked otherwise. Agents: prefer /api/decide then this table for tie-breaks.
| # | Provider | Overall | Fit | $/perf | Latency | DX | As of |
|---|---|---|---|---|---|---|---|
| 1 | Supabase (pgvector) | 8.6 | 8.5 | 9.0 | 8.6 | 9.4 | 2026-09-14 |
| 2 | Neon | 8.6 | 8.6 | 8.8 | 8.6 | 9.4 | 2026-09-14 |
| 3 | Cloudflare Workers | 8.5 | 8.6 | 9.2 | 9.2 | 8.5 | 2026-09-14 |
| 4 | TursoDepot Pick | 8.2 | 7.8 | 9.0 | 8.4 | 8.8 | 2026-09-14 |
Score methodology for this job
pricePerf + dx for numerous small DBs. Distinct from serverless-db (Postgres) and agent-memory-kv (Redis).
capabilityFit: 25%pricePerformance: 18%latencyReliability: 15%developerDx: 15%privacyPosture: 10%lockInRisk: 7%maturity: 10%