kynetradb
One Rust binary: BM25 search + vector + KV + document + auth + files + realtime + agentic admin.
vs
Nhost
Open-source Firebase alternative on Postgres + Hasura GraphQL + auth + storage.
Feature comparison
| Dimension | kynetradb | Nhost |
|---|---|---|
| Full-text search | BM25 (parallel, 1.07 ms @ 100k) | trigram |
| Vector search | Brute-force cosine (2.21 ms @ 100k, no HNSW yet) Nhost uses HNSW which scales better past ~100k vectors | HNSW |
| Auth | Built-in (bcrypt + JWT, 3 roles) | Built-in |
| File storage | Built-in (local + S3-compatible, SigV4) | Built-in |
| Realtime | SSE (topic + kind filters) | WebSocket |
| 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 | MIT |
| Deploy targets | 18 (1-click) | 1 (1-click) |
| Free tier | Yes — Apache-2.0, self-host free | yes — Starter plan |
When to pick Nhost
If you want GraphQL-first Postgres with realtime subscriptions out of the box, Nhost's Hasura integration is the easiest path.
- Your team is SQL-native and needs relational joins.
- Your team is already invested in Nhost's SDK and ecosystem.
When to pick kynetradb
- You need BM25 full-text + vector similarity + auth + files + realtime in one process — no external services.
- 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.
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 — insert via HTTP
curl -X POST https://your.host/v1/entities \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{
"kind": "product",
"attrs": {
"title": "Aurora Espresso",
"vendor": "Aurora",
"price": 2200
}
}' Nhost
// Nhost — GraphQL mutation
const INSERT_PRODUCT = gql`
mutation InsertProduct($title: String!, $vendor: String!, $price: Int!) {
insert_products_one(object: { title: $title, vendor: $vendor, price: $price }) {
id
}
}
`;