iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Bytes #226, published September 28, 2023, made the case for giving projects, SaaS customers, or even individual users separate small databases instead of placing everyone’s data in one shared database. It introduced Turso as an edge-hosted, distributed database built on libSQL, then described as Turso’s open-source SQLite fork, and explained how Embedded Replicas could pair a local copy with a remote database. Those ideas still make a useful way to think about data isolation, but the newsletter’s plan limits are historical—not current pricing guidance.
What was Bytes #226 about?
The short issue centered on a simple question: why would an application need many databases? Its answer was that a database can be an isolation boundary. A developer might use one database for each project, one for each SaaS customer, or one for every user on a platform such as Val Town. That is different from putting all customers or users into one database and separating their records with tables or tenant IDs. Bytes #226
The issue connected this approach to SQLite’s file-based nature: small databases can be treated as individual files, which it presented as part of the low-friction appeal. That is an architectural explanation, not a guarantee that separate databases are always cheaper or simpler. Costs and operational work depend on the application and the service hosting those databases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What is Turso, in the issue’s original framing?
In 2023, the newsletter described Turso as an edge-hosted, distributed database based on libSQL, which it called Turso’s open-source SQLite fork. The interview also framed SQLite as a library rather than a conventional database server. Turso CEO Glauber Costa put it this way: “We built our product around SQLite, which is really just a library.” The sentence appeared in the interview published with Bytes #226 on September 28, 2023; it is the issue’s framing, not a complete definition of Turso’s current products. Bytes #226 Interview with Glauber Costa
#1 Best Overall
Turso’s current materials describe distinct ways to use its SQLite-compatible database: open-source software, Turso Cloud, and embedded replication and sync. These are operating models, not interchangeable names for one deployment. A hosted database and a database embedded in an application have different connectivity, data placement, synchronization, and operational considerations. Turso product overview
Why use one database per customer or user?
Separate databases can make sense when isolation is a core product requirement. Rather than placing every tenant’s records in shared tables, an application can assign a database to each tenant, project, or user. The benefit being proposed is a clearer boundary around each group’s data—not a measured performance improvement or automatic cost saving.
- Per-customer SaaS: each customer’s data can live in its own database, rather than relying solely on tenant identifiers in shared tables.
- Per-project tools: projects can have independent stores, which can make their data boundaries easier to reason about.
- Per-user platforms: an application can give users individual databases where that fits how the product stores and manages their data.
The trade-off is that the application and its hosting setup must manage many database instances or files. The architecture is useful only if the isolation model, operational workflow, compatibility needs, and usage limits fit the product. Bytes #226 presented the pattern as an opportunity made practical by SQLite-style databases; it did not establish that every application should adopt it. Bytes #226
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What were Embedded Replicas?
In the 2023 issue, Embedded Replicas were described as a local SQLite database copy associated with a remote Turso database. The idea was to combine local responsiveness with remote deployment: an application could work against a database close to where it runs while a remote database remained part of the setup. Bytes #226
Rank #3
Current Turso materials describe embedded replication and sync for local-first and offline-capable applications. That is the present product framing; it should not be assumed that every implementation detail or label from the 2023 issue remains unchanged. Turso embedded replication
For an application that needs to operate during network interruptions, the important design question is how local changes and remote state are synchronized. A local copy can change where reads and writes happen, but an architecture still needs an explicit plan for synchronization behavior and for the application’s connectivity and data requirements.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Are Bytes #226’s Turso plan limits still current?
No. The newsletter reported that Turso’s free tier included up to 500 databases and that a $29-per-month tier included 10,000. Those are figures reported in September 2023, not current plan advice or independently verified present-day limits. Bytes #226
Recommended Free Tools
Turso’s current official pricing page, accessed in 2026, lists 100 databases on Free and unlimited databases on paid self-serve tiers. The page also lists usage allowances and paid overages; prices and included usage vary by plan and billing selection, so consult the live page for the terms that apply when choosing a plan. Turso pricing
| Plan information | Bytes #226, September 2023 | Turso pricing page, accessed 2026 |
|---|---|---|
| Free database allowance | Up to 500 databases, as reported by the newsletter | 100 databases |
| Paid database allowance | 10,000 databases on a tier reported at $29/month | Unlimited databases on paid self-serve tiers; prices and included usage vary by plan and billing selection |
How should a developer decide whether this model fits?
Start with the application’s data boundaries and operating needs rather than the number of databases a plan permits. A hosted cloud database, a local embedded database, and an embedded database that synchronizes with a remote service answer different needs. Turso product overview Turso embedded replication
Quick Recap
- Isolation: Decide whether a customer, project, or user needs a separate database, or whether shared storage with tenant-level separation is sufficient.
- Connectivity: Determine whether the application must keep working locally or offline, or whether it can depend on a hosted database connection.
- Synchronization: If local and remote copies both matter, establish how changes should sync and whether that behavior matches the application’s write patterns.
- Compatibility and operations: Check the SQLite compatibility and migration requirements, and account for the work of creating, managing, and monitoring many databases.
- Plan fit: Verify current limits, included usage, and overage terms on Turso’s pricing page instead of relying on the 2023 figures.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
