Turso Cloud

Open coreDatabase

Millions of Databases. One Architecture.

Homepage Docs Pricing Repository

Scanned 15 Oct 2026 · Schema v5 · features v21

From: $5.99/mo
freemium subscription tiers + row/storage/sync usage overages
Free tier: Yes
No card required.
Isolation: Not disclosed
the public docs do not say
Regions: 10
Virginia, United States · Ohio, United States · Oregon, United States · Central, Canada · São Paulo, Brazil · Dublin, Ireland +4
Capabilities: 16 / 61
4 partial · 21 fail · 0 not assessed
Agent readiness: 8.5/11 · 8/11
read · drive, pre-login surface

Advertised for

Per agent databases · Per tenant databases · Offline first apps · Embedded replica sync · Vector search rag · Multi tenant saas

Built for

Developers, then technical

· https://turso.tech/ — SQLite-compatible. SDKs in TypeScript, Python, Rust, and Go. Self-serve from signup to production.
· https://turso.tech/pricing.md — Rows read and rows written are a proxy for compute.

01 Pricing freemium subscription tiers + row/storage/sync usage overages

Tier	EntryFree	Developer	Scaler	Pro	TopEnterprise
Price	$0/month; $0/month billed yearly ($0/year)	$5.99/month; $4.99/month billed yearly ($59.88/year)	$29/month; $24.92/month billed yearly ($299/year)	$499/month; $416.58/month billed yearly ($4999/year)	Custom
Storage	5 GB	9 GB	24 GB	50 GB	—
Storage overage	—	$0.75/GB	$0.5/GB	$0.45/GB	—

rows read per billion, rows written per million, storage GB, sync GB·Card required: No·turso.tech

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

Dark, mint-accented developer presentation: oversized sans-serif marketing headings, fine grid rules and code-led landing imagery; pricing retains the same spacious visual system, while documentation uses a denser three-column reading layout.

Swiss-inspired
Corporate

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Not disclosedthe public docs do not say

Persistence

Durable managed databases backed by S3/S3-Express

Snapshots / forks

Resources & limits

Storage

Diskless multi-tenant architecture; local disks cache data backed by S3 and S3-Express

Limits & quotas

Free: 100 databases; 500 Million rows read/month; 10 Million rows written/month; 3 GB syncs/month; 1-day PITR; audit retention None days. | Developer: Unlimited databases; 2.5 Billion rows read/month; 25 Million rows written/month; 10 GB syncs/month; 10-day PITR; audit retention 3 days. | Scaler: Unlimited databases; 100 Billion rows read/month; 100 Million rows written/month; 24 GB syncs/month; 30-day PITR; audit retention 14 days. | Pro: Unlimited databases; 250 Billion rows read/month; 250 Million rows written/month; 100 GB syncs/month; 90-day PITR; audit retention 30 days. | Enterprise: Contact sales; dedicated infrastructure, unlimited usage, BYOC and 24x7 priority support. Table lists Pro baseline quotas; prose promises unlimited/custom usage, so do not treat 50GB as hard Enterprise capacity.

GPU

Access

Deploy interface

cliapisdkmcpdashboard

SDK languages

TypeScriptJavaScriptPythonGoRustPHPRubyKotlinSwiftCDart

Network & secrets

Egress controls

Secrets

Bring your own cloud

Enterprise AWS BYOC

Placement & use

Jurisdiction

aws-us-east-1 (Virginia, United States)aws-us-east-2 (Ohio, United States)aws-us-west-2 (Oregon, United States)aws-ca-central-1 (Central, Canada)aws-sa-east-1 (São Paulo, Brazil)aws-eu-west-1 (Dublin, Ireland)aws-eu-north-1 (Stockholm, Sweden)aws-ap-south-1 (Mumbai, India)aws-ap-northeast-1 (Tokyo, Japan)aws-ap-southeast-2 (Sydney, Australia)

Advertised workloads

Per agent databasesPer tenant databasesOffline first appsEmbedded replica syncVector search ragMulti tenant saas

04 Capabilities 16 pass · 4 partial · 21 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 2/4

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not applicable

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not applicable

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Not supported

GPU computeGPU-backed instances available.

Not applicable

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not applicable

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not applicable

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not applicable

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not applicable

Networking & delivery 2/4

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Not applicable

Custom domainsBring-your-own domain via CNAME/DNS.

Not applicable

Public preview URLsShareable per-deploy / per-branch URLs.

Not applicable

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not applicable

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Not supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Supported

Email send / receiveSend and/or receive email from the workload.

Not applicable

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 5/6

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not applicable

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not applicable

Git deployDeploy from a Git repo / push-to-deploy.

Not applicable

Private container registryHosted private image registry.

Not applicable

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Supported

AI & agents 2/10

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not applicable

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not applicable

Data 3/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 1/4

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not applicable

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not applicable

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 1/9

Built-in authPlatform-provided authentication / IAM for workloads.

Partially supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Not supported

TeamsMulti-user team accounts.

Partially supported

SharingShare a running workload/resource via link (optionally gated).

Not supported

BYOCRuns inside the customer's own cloud account.

Partially supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

database per agent/user/tenantper-tenant-isolation
“Spin a database for every user, agent, and tenant.” turso.tech
embedded replication and offline-first syncembedded-replica-sync
“Read and write locally with zero latency. Sync changes when the device comes online.” turso.tech
customer-managed database encryption keyscustomer-managed-encryption-keys
“Keep sensitive data private with keys only you control. Keys are per-database for full isolation.” docs.turso.tech
Vegas Blackout accident protectionusage-accident-protection
“Once per month, before your invoice closes, you can pick any single day and remove its charges from your bill.” turso.tech

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

8.5/11

6 full · 5 partial · 77% of applicable checks

llms.txt
Supported
“https://turso.tech/llms.txt — # Turso Substantive overview links docs, pricing and API/MCP.”
llms-full.txt
Supported
“https://docs.turso.tech/llms-full.txt — # Turso 998326-byte comprehensive docs snapshot retained as bounded POINTER; apex 18087-byte overview additionally retained.”
robots.txt AI policy
Partially supported
“https://turso.tech/robots.txt — User-agent: * Disallow: /api.turso.tech/ Disallow: /app/ Disallow: /turso-soc2.pdf Allow: / No named major AI user agents: wildcard/default allow earns HALF, not full under rubric.”
JSON-LD
Partially supported
“https://turso.tech/ — "@type":"Organization" Organization legalName Turso, Inc; no rich Product/SoftwareApplication offers.”
Sitemap
Supported
“https://turso.tech/sitemap.xml — <urlset Non-trivial 90379-byte XML sitemap.”
Meta tags
Supported
“https://turso.tech/ — Turso - Millions of Databases. One Architecture. Descriptive title/description and OG title/description present.”
Markdown negotiation
Supported
“https://docs.turso.tech/turso-cloud — # Turso Cloud Documentation Accept: text/markdown returns text/markdown on landing (1677 bytes) and docs (11262 bytes).”
Content efficiency
Partially supported
“https://turso.tech/ — HTML: 152745 bytes; visible-text UTF-8 bytes excluding script/style: 7618; ratio 0.04987397. Measured 4.9874%, within rubric 1–5% band; near threshold but do not claim >5% from mere SSR presence.”
Docs discoverable
Partially supported
“https://turso.tech/ — Resources Initial header has Resources dropdown, not directly exposed docs link. First docs links are body/footer; peer bounded design capture did not open submenu. Do not claim full without stronger evidence.”
Machine-readable pricing
Supported
“https://turso.tech/pricing.md — | Monthly Price | $0 | $5.99 | $29 | $499 | Custom | Structured markdown tiers, annual/monthly billing, usage and overage tables.”
No anti-bot wall
Partially supported
“https://trust.turso.tech/ — Initial direct GET trust.turso.tech returned 403; foxcrawl render returned full trust-center content with exit 0. Main public pages/docs all 200 and unchallenged; trust access needed rendered retry. No unresolved scan issue.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

8/11

7 full · 2 partial · 73% of applicable checks

Public API
Supported
“https://docs.turso.tech/api-reference/introduction.md — Programmatically manage databases, groups, organizations, and tokens with the Turso Platform API.”
OpenAPI spec
Supported
“https://docs.turso.tech/api-reference/openapi.json — "openapi": "3.0.1" Parsed JSON; 128033 bytes; docs and apex copies.”
MCP server
Supported
“https://docs.turso.tech/integrations/mcp.md — server at **`https://mcp.turso.ai/mcp`**. Hosted Cloud control+SQL MCP with OAuth; machine-discovery manifest also retained.”
SDK packages
Supported
“https://docs.turso.tech/llms.txt — [Turso Quickstart (TypeScript)](https://docs.turso.tech/sdk/ts/quickstart.md) Multiple official SDK languages documented.”
Auth documented
Supported
“https://docs.turso.tech/api-reference/authentication.md — The Turso API uses API tokens to authenticate requests. Organization/group scoped tokens, explicit scope list and lifecycle, bearer auth; SQL-token permissions separate.”
Self-serve credentials
Supported
“https://docs.turso.tech/api-reference/tokens/create.md — # Create API Token Programmatic issuance via API and CLI; AgentID account self-signup publicly documented without human-in-loop, not behaviorally tested.”
Webhooks
Not supported
“https://docs.turso.tech/llms.txt — # Turso No hosted webhook docs found in complete docs index/full text or Platform API; AgentMail external webhooks do not count.”
CLI tool
Supported
“https://docs.turso.tech/cli/headless-mode.md — turso auth login --headless”
Error model
Partially supported
“https://docs.turso.tech/api-reference/response-codes.md — The Turso API will respond with an HTTP status code, and in the event of an error, return an error message in the response body. HTTP 401/402/403/409 documented; no substantive uniform JSON error schema on this page. Anonymous /locations returned {"error":"token contains an invalid number of segments"}, a single observation not a complete contract.”
Rate limits documented
Not supported
“https://docs.turso.tech/llms.txt — # Turso No rate-limit or Retry-After documentation found in full docs. Billing quotas are not API request rates.”
Agent config files
Partially supported
“https://raw.githubusercontent.com/tursodatabase/turso-mcp/main/codex/README.md — `skills/turso/SKILL.md` — guidance for the agent on the Turso ecosystem One installable skill/config surface. /agents.md and /.well-known/agent 404; MCP manifest is MCP discovery, not a second generic agent-configuration surface.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 3

Claude Code Anthropic
Supported
“<Tab title="Claude Code">”
Source docs.turso.tech
Codex CLI OpenAI
Supported
“<Tab title="Codex">”
Source docs.turso.tech
Cursor Anysphere
Supported
“<Tab title="Cursor">”
Source docs.turso.tech

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 3

SOC 2 Type II
certifiedhostedCurrent homepage explicit Type II, trust-center rendered Compliance confirms SOC 2; report gated/no report independently audited. Pricing gates access at Pro+.
“SOC 2 Type II”
Source turso.tech
HIPAA
enterprise-onlyhostedTrust Compliance lists HIPAA, homepage says HIPAA-ready, Pro+ pricing; terms document BAA signing path. Do not call HIPAA certified.
“HIPAA”
Source trust.turso.tech
GDPR
self-attestedhostedMarketing GDPR/readiness statement, DPA Developer+; not an independent certification.
“SOC 2 Type II, GDPR, HIPAA-ready”
Source turso.tech

Regions 10

Virginia, United Statesaws-us-east-1
Ohio, United Statesaws-us-east-2
Oregon, United Statesaws-us-west-2
Central, Canadaaws-ca-central-1
São Paulo, Brazilaws-sa-east-1
Dublin, Irelandaws-eu-west-1
Stockholm, Swedenaws-eu-north-1
Mumbai, Indiaaws-ap-south-1
Tokyo, Japanaws-ap-northeast-1
Sydney, Australiaaws-ap-southeast-2

Turso Cloud now runs in ten AWS regions across four continents. OpenAPI /locations example stale at six regions. Actual anonymous /v1/locations returns 401; use explicit Oct 1 first-party ten-region announcement, no authenticated call.

Legal

Privacy notice Terms of service

08 Open source MIT · fetched by machine, not quoted from marketing

Licence & repository

Licence: MITOSI
Primary language: C
Stars: 17,272
Forks: 544
Created: 29 Sep 2022
Archived: No

Activity

Last commit: 13 Oct 2026
Latest release: libsql-server-v0.24.32 · 14 Feb 2025
Issues open / closed: 410 / 230 · 36% closed

Latest eight repository releases remain libsql-server tags, latest February 2025; fresh pushes October 13, 2026. Do not equate old release tag with repo archived.

Fetched via gh on 15 Oct 2026.

Self-hosting

Methods: dockerbinarysource-buildpackage-manager
You operate: —

S3-compatible storage optional for bottomless durability; no external dependency for basic sqld. Free under MIT plus own infra. Hosted API/dashboard/compliance and managed orchestration not supplied by self-hosted core.

Documentation signals 8/8

SupportedQuickstart
SupportedAPI reference
SupportedSelf-host guide
SupportedChangelog
SupportedOpenAPI
Supportedllms.txt
SupportedExamples
SupportedArchitecture doc

09 Company & presence Facts only, not scored

Company

Headquarters: San Francisco-based, globally distributed remote company
Founded: —
Team size: Not disclosed
Hiring: unknown

Activity

Last release: libsql-server-v0.24.32 (2025-02-14T12:10:54Z); new engine v0.8.3 (2026-10-12T14:39:37Z) github.com
Last blog post: 2026-10-14 — The Many-Database Architecture: Should You Give Every Tenant Their Own Database? turso.tech

Presence 6

Links found on the public surface scanned; not an exhaustive search.

10 Sources & method How this entry was produced

Public surface only

Everything here was read from turso.tech's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Database products →