---
lang: en
type: Thing
title: Turso
canonical: "https://saasspecs.com/item/turso/"
hvce_version: 1
tenant: saasspecs
slug: turso
record_kind: entity-profile
content_sha256: 42fce3215ca81bbe56c3eb9317481697cbcc781c04629d4995e9e87beea48c32
indexed_at: "2026-06-12T19:03:40.170Z"
license: citation-free
entities:
  -
    role: subject
    slug: turso
    name: Turso
    type: Thing
    profile_url: "https://saasspecs.com/item/turso/?format=md"
---
# Turso

Distributed SQLite at the edge with libSQL extensions, embedded replicas, and serverless autoscaling.

## Record

- **Schema type**: Corporation
- **Website**: https://turso.tech
- **Email**: support@turso.tech
- **Address**: 535 Market Street, San Francisco, California, 94105, United States
- **Coordinates**: 37.7899, -122.4014
- **Deployment Link**: [Deploy Turso Stack Layer](https://turso.tech/pricing)

### Summary

Distributed SQLite at the edge with libSQL extensions, embedded replicas, and serverless autoscaling.

### Description

Turso hosts SQLite databases replicated globally for low-latency reads at the edge. libSQL adds vector search, branching, and HTTP API access for serverless and mobile-first applications.

### Expert insight

Enable embedded replicas in your application process to eliminate round-trip latency for read-heavy local queries.

### Attributes

- **Free Tier Allowance**: 5 GB
- **Rate Limit Cap**: 1,000 RPS
- **Session Lifetime**: 24 Hours
- **Overage Fee per 1k MAU**: 0.25 USD/GB
- **MFA Support**: Enforced via Turso console two-factor authentication and organization policies
- **Enterprise SSO SAML**: Available on Enterprise plans with SAML directory federation
- **Custom Domain Support**: Custom database hostnames and private networking on paid tiers
- **Supported SDKs**: JavaScript, TypeScript, Python, Go, Rust, libSQL, Drizzle, Prisma
- **Social Providers**: GitHub and Google OAuth for Turso account login
- **Compliance Standards**: SOC 2 Type II, GDPR on Enterprise agreements
- **Webhook Fallback Policy**: Database webhooks with retry via application-layer consumers
