kynetradb
One Rust binary: BM25 search + vector + KV + document + auth + files + realtime + agentic admin.
vs
Turso
libSQL distributed SQLite — per-tenant databases, edge replicas, embedded replicas.
Feature comparison
| Dimension | kynetradb | Turso |
|---|---|---|
| Full-text search | BM25 — reference catalogue | trigram |
| Vector search | Brute-force cosine evaluation | None |
| Auth | Preview scope | External |
| Row-Level Security | Preview scope | No |
| File storage | Preview scope | None |
| Realtime | Preview scope | None |
| Edge Functions | Preview scope | No |
| TypeScript SDK | Preview scope | No official client SDK |
| KV lookups | Preview scope | No |
| Document filter | Preview scope | Yes |
| LLM runtime | Preview scope | No |
| Outbound DB sync | Preview scope | No |
| Self-host | Preview scope | Limited |
| Single binary | Preview scope | No |
| License | Preview terms — request a scoped evaluation | MIT |
| Deploy targets | 19 target profiles | 1 listed target profiles |
| Free tier | Preview access by request | yes — 500 databases, 9 GB storage |
When to pick Turso
Best answer to per-tenant SQLite at scale; embedded replicas mean near-zero read latency. No search, vector, or auth built-in.
- You need globally distributed SQLite reads with per-tenant database isolation.
- Your team is already invested in Turso's SDK and ecosystem.
When to pick kynetradb
- You want a comparison-led conversation about BM25 full-text, vector evaluation, and data-plane trade-offs.
- You need a product-specific implementation scope rather than a generic migration claim.
- You want to assess 19 hosting target profiles, including 5 Indian providers.
- You want a scoped preview conversation about the data, deployment, and operating boundary.
- You want a single binary with no runtime dependencies — no container fleet to operate.
Create a record — both APIs side by side
Insert a product record. These are documentation-accurate shapes, not runnable end-to-end examples.
kynetradb
// kynetradb — @kynetra/client TypeScript SDK
import { createClient } from '@kynetra/client'
const kdb = createClient('https://your.host', PUBLISHABLE_KEY)
const { data, error } = await kdb
.from('products')
.insert({ title: 'Aurora Espresso', vendor: 'Aurora', price: 2200 })
.select()Turso
// Turso — libSQL client
const result = await client.execute({
sql: 'INSERT INTO products (title, vendor, price) VALUES (?, ?, ?)',
args: ['Aurora Espresso', 'Aurora', 2200],
});