SQLite

Turso — built on libSQL, the open-source fork of SQLite — packages edge distribution, embedded replicas, and native vector search into one product. This 2026 guide explains how Turso differs from other serverless databases, the May 2026 pricing, real production patterns (multi-tenant SaaS, RAG, mobile AI), strengths and trade-offs, competitive positioning, and sustainability — all from publicly available information and a practitioner's perspective.

How to build CRUD and forms — the heart of internal-tool work — in Hono + Inertia + React. Covers Drizzle ORM for DB access, Zod for end-to-end typed validation, and Inertia's useForm for error display, redirects, and flash messages, all from a practitioner's perspective.

From Firebase, Supabase, and AWS Amplify comparison to REST/GraphQL design, authentication, push notifications, and real-time sync. Our Shinagawa-based development team provides a thorough backend selection guide including cost estimates by MAU scale.

**Cloudflare Durable Objects** ([official docs](https://developers.cloudflare.com/durable-objects/) / [product page](https://www.cloudflare.com/products/durable-objects/) / [SQLite in Durable Objects blog](https://blog.cloudflare.com/sqlite-in-durable-objects/)) is Cloudflare's **stateful serverless primitive that pairs compute with persistent storage inside a globally-unique instance running on Workers**. Announced in 2020, it reached **GA on SQLite storage with Workers Free-tier availability in April 2025**, then **entered its paid-billing phase on January 7, 2026** — this is now the commercial-adoption era. **Architectural core**: a **`DurableObjectStub`** derived from a name (`DurableObjectNamespace::getByName`) always routes to the single, globally-unique instance for that name → **zero-latency SQLite access** because compute and storage co-reside in the same process on the same machine. This delivers **strong-consistency single-master semantics at edge latency** — a class of distributed system that is famously hard to DIY, replaced with a single platform primitive. **Pricing** (Paid tier): - **Requests**: 1M/month included, then **$0.15 / 1M** (WebSocket inbound counts at 20:1) - **Duration**: 400,000 GB-seconds/month included, then **$12.50 / 1M GB-seconds** - **SQLite row reads**: 25B/month included, then **$0.001 / 1M** - **SQLite row writes**: 50M/month included, then **$1.00 / 1M** - **Stored data**: 5 GB-month included, then **$0.20 / GB-month** - **`setAlarm()` counts as one row write** **Free tier** (launched April 2025): 100,000 requests/day, 13,000 GB-seconds/day, 5M SQLite row reads/day, 100K writes/day, and 5 GB stored data — plenty for personal PoC and startup validation. **WebSocket Hibernation**: idle-but-eligible instances **do not accrue duration charges**. Long-lived sparse-messaging sessions (chat, notifications, LLM conversation state) become dramatically cheaper to run. **Key 2025–2026 updates**: April 7, 2025 SQLite GA + Workers Free; August 21, 2025 direct `getByName` construction; October 16, 2025 Data Studio UI editor; **October 25, 2025 WebSocket message size lifted from 1 MiB to 32 MiB**; January 7, 2026 SQLite storage billing goes live. **Representative use cases**: collaborative editing (Google-Docs-class), real-time chat, multiplayer game room-matching, live notifications, **LLM agent conversation and session state** (backend for Claude Code / Cursor-style tools), financial and IoT event buffering, distributed rate limits and locks. **Positioning**: where [Local LLM landscape (June 2026)](../columns/local-llm-landscape-2026-june-update), [agmsg](../columns/agmsg-cross-agent-messaging-cli-ai-2026-06), and [Sakana Fugu orchestration](../columns/sakana-fugu-orchestration-model-2026-06) distribute AI **inference**, Durable Objects distribute **stateful session, history, and coordination** at the edge — a natural complement rather than a competitor.

**[agmsg](https://github.com/fujibee/agmsg)** is an open-source (MIT) **cross-vendor messaging tool for CLI AI coding agents** by **fujibee** ([official site agmsg.cc](https://agmsg.cc/)). It lets **Claude Code, Codex, Gemini CLI, GitHub Copilot CLI, Antigravity, and OpenCode** talk to each other through a shared local SQLite file — so **humans stop being the copy-paste courier between tools**. Tagline: "You stop being the copy-paste courier between your agents." **Highlights**: - **Only dependencies are bash and sqlite3** — no daemon, no network, no Python - **Three delivery modes** — `monitor` (~5s real-time push), `turn` (between-turn polling), or `both` - **N-agent teams**, role switching (`actas`), spawning new agents (`spawn`), and clean teardown (`despawn`) - **Not MCP, not subagents, not a message queue** — a peer-to-peer messaging layer between sessions - **One-line install**: `npx agmsg` - **Claude Code Plugin Marketplace**: `/plugin install agmsg@fujibee-agmsg` **Product Hunt #5 Product of the Day on June 9, 2026** (219 upvotes, 39 comments). GitHub stars 859, v1.1.1 (June 25, 2026). Community-built derivatives include agmsg-shogi, agmsg-go, and agmsg-mcp. **Oflight's take**: unlike [Loop Engineering](../columns/loop-engineering-ai-agent-paradigm-2026-06) or [Sakana Fugu's orchestration model](../columns/sakana-fugu-orchestration-model-2026-06), agmsg occupies a different niche — **peer-to-peer messaging at the same layer, across tools**. It's an especially natural fit for the [Claude Code Agent View parallel-orchestration](../columns/claude-code-agent-view-parallel-orchestration-2026) workflows, and the most pragmatic way to stitch multi-vendor LLMs into one dev workflow. The article closes with **three direct inquiry funnels** for AI agent environment setup and custom integration.