The architectural difference
Neo4j and SolarflareDB overlap around helping applications recover useful context, but they place the product boundary in different locations. The right choice depends on whether the application needs a specialized retrieval or memory service, a general graph engine, or a unified authoritative temporal context layer.
Capability matrix
| Dimension | Neo4j | SolarflareDB private-beta direction |
|---|---|---|
| Primary abstraction | General-purpose property graph database | Opinionated temporal context database |
| Query language | Mature Cypher ecosystem | Typed APIs and thin declarative context query target |
| Temporal context | Model in application/schema | Recorded/valid time, supersession, contradiction, provenance defaults |
| Semantic retrieval | Product and integration dependent | Native hybrid context pipeline target |
| Operations | Capacity-oriented managed graph service or self-managed | Shard-oriented serverless managed target |
| Entry pricing | Capacity based; review current Aura pricing | $0 Spark and $5 Hobby proposal |
When to choose Neo4j
Choose Neo4j when mature graph query, broad tooling, graph analytics, Cypher expertise, and a general-purpose graph platform are the dominant requirements.
Retaining a focused system is usually better than introducing a new database merely because it has a broader feature list. Benchmark the actual workload and operational boundary.
When to choose SolarflareDB
Choose SolarflareDB when the main job is agent context with serverless entry economics, hybrid retrieval, source episodes, current/as-of truth, transparent operation meters, and replay defaults.
SolarflareDB should earn adoption by reducing custom context infrastructure and improving temporal correctness, retrieval explainability, and cost transparency—not by claiming every incumbent is obsolete.
How to run a fair evaluation
- Use the same source episodes, identity rules, embedding model, and extraction policy.
- Measure immediate and settled retrieval after writes.
- Include current truth, historical truth, entity aliases, contradictions, and multi-hop questions.
- Record context tokens, answer quality, latency, index freshness, and operations cost.
- Test deletion, export, duplicate delivery, and concurrent writers.