kynetradb
One Rust binary: BM25 search + vector + KV + document + auth + files + realtime + agentic admin.
vs
Elasticsearch
Distributed Lucene-based search + analytics engine with kNN vector search and the ELK stack.
Feature comparison
| Dimension | kynetradb | Elasticsearch |
|---|---|---|
| Full-text search | BM25 (parallel, 1.07 ms @ 100k) Elasticsearch's Lucene is more mature with fuzzy/synonym support | lucene |
| Vector search | Brute-force cosine (2.21 ms @ 100k, no HNSW yet) Elasticsearch uses HNSW which scales better past ~100k vectors | HNSW |
| Auth | Built-in — email+password, refresh tokens, OTP/magic-link, OAuth (Google/GitHub), anonymous, /auth/v1 | Built-in |
| Row-Level Security | Built-in — auth.uid() DSL, per-row enforcement, SELECT/INSERT/UPDATE/DELETE | No |
| File storage | Built-in — buckets, public/private, signed URLs, object RLS, local + S3-compatible | None |
| Realtime | WebSocket — postgres_changes (INSERT/UPDATE/DELETE), presence, broadcast; RLS-filtered | None |
| Edge Functions | Built-in — WASM /functions/v1, sandboxed, 10s timeout, SDK .invoke() | No |
| TypeScript SDK | @kynetra/client — supabase-js-compatible, from().select().eq() | No official client SDK |
| KV lookups | Yes (point lookup by ID) | No |
| Document filter | Yes (JSON predicates) | Yes |
| LLM runtime | Yes (Anthropic + OpenAI + Ollama) | No |
| Outbound DB sync | Yes (12 sinks: Postgres, DynamoDB, BQ, Firestore, CF, Mongo, Redis, Pinecone) | No |
| Self-host | Yes (single binary) | Yes |
| Single binary | Yes | No |
| License | Apache-2.0 | SSPL |
| Deploy targets | 18 (1-click) | 0 (1-click) |
| Free tier | Yes — Apache-2.0, self-host free | yes — Elastic Cloud 14-day trial; self-host free (SSPL) |
When to pick Elasticsearch
A decade of search tuning, mature observability stack (Kibana, Logstash), and the best fuzzy/synonym/multi-language support in the market.
- You need fuzzy matching, synonyms, multi-language analyzers, or the Kibana observability stack.
- Your team is already invested in Elasticsearch's SDK and ecosystem.
When to pick kynetradb
- You want Supabase's developer experience — the
@kynetra/clientTypeScript SDK, PostgREST REST API, GoTrue-shaped auth, RLS, realtime channels — running as a single binary on infra you own. - You need BM25 full-text + vector similarity search built in with no separate service and no CDC pipeline.
- You want to deploy to 18 targets (including 5 Indian providers) from one Dockerfile.
- You need outbound sync to 12 databases (Postgres, DynamoDB, BigQuery, Firestore, Cloudflare, MongoDB, Redis, Pinecone) with zero extra code.
- You want an agentic admin with 10 typed LLM-driven actions and a persisted audit trail.
- You want Apache-2.0 with a self-host path that doesn't require an ops team.
- You want a single binary with no runtime dependencies — no container fleet to operate.
Search query — both APIs side by side
Full-text search call. These are documentation-accurate shapes, not runnable end-to-end examples.
kynetradb
# kynetradb — BM25 search
curl -X POST https://your.host/v1/search \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"q": "aurora espresso",
"top_k": 10,
"kind": "product"
}' Elasticsearch
# Elasticsearch — REST API
curl -X POST http://localhost:9200/products/_search \
-H "Content-Type: application/json" \
-d '{
"query": {
"match": { "title": "aurora espresso" }
},
"size": 10
}'