Creators of8DB

Explore the models / 8DB

Topological braids

Keep the order of an interaction.

Represent crossing order in interacting histories so a relationship pattern can retain how it unfolded.

Explore the capabilitiesSee a complete workload
Order · encode · compare
Model / BraidsConceptual diagram
braids representation: conceptual diagramSTRANDS + CROSSINGS + SEQUENCE
Strands change relative order over time. Crossings retain sequence as well as connection.

Start with the operations
your question needs.

  • Braid encoding and strand operations
  • Topology matching on supported paths
  • Declared graph, hypergraph, vector and timeline projections

Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application.

Not every BraidQL operator is released. Durable semantic-identity ingestion remains gated while its encoding profile is corrected. Fingerprints summarize a representation; projections need not reconstruct the original braid.
Connected native models

Keep the next question within reach.

For a group of time series, rank crossings describe the pattern of co-movement. Braid representations can support topology-based comparison and declared projections into other structures.

time series representation: conceptual diagramPOINTBOUNDGAPMEANING PRESERVED THROUGH TIME →
Time series

Keep the meaning in every observation.

Observe · window · analyze

Explore model ↗
graphs representation: conceptual diagramENTITY → RELATIONSHIP → PATH
Graphs

Follow the relationship to a better answer.

Connect · traverse · follow

Explore model ↗
vectors representation: conceptual diagramQUERYCANDIDATES → CONTEXT → RETRIEVAL
Vectors

Give a similar result its context.

Compare · rank · retrieve

Explore model ↗

These connections show the models involved in the application design. Compare the supported combination and full workflow with a realistic alternative.

Input → usable value / interactive design example

Compare the interaction pattern of related signals

time series representation: conceptual diagramPOINTBOUNDGAPMEANING PRESERVED THROUGH TIME →
Step 1 / Time series

Read a bundle of source-backed time series

Measured points, an interval bound and a visible gap retain different meanings along the same timeline.

Next: Define crossings

Conceptual application workflow. Qualify the supported operations, external tools, protection and persistence for the complete path. These diagrams are explanatory, not measured results.

Read the complete workflow and comparison scope
  1. Read a bundle of source-backed time series
  2. Declare how series become strands and crossings
  3. Encode the rank-crossing pattern
  4. Compare topology and inspect the source intervals
  5. Return a pattern match with its interpretation and limits

A static graph and an ordered interaction history preserve different information. Temporal graphs or application-side encodings are legitimate alternatives; compare the exact invariant, query semantics and data preparation.

Compare a realistic alternative.

A property graph can store events and ordering relationships. 8DB’s case is the implemented braid algebra and its composition paths, not an assertion that another database cannot store ordered data.

Neo4j graph concepts

Compare equivalent outputs and required guarantees, including the simplest single-product alternative where one exists. A specialist may remain the better fit when its operators, ecosystem or operational maturity are decisive. Combining native models becomes valuable when your actual question crosses them.

Modality performance / Evidence reviewed 18 September 2026

Define the useful result. Measure the complete job.

A modality-specific timing is not yet linked to this guide.

There may be supporting engineering measurements in the internal archive. We are reconciling their workload, result quality and comparison conditions before presenting a public chart. A benchmark for an adjacent model does not establish this model’s performance.

01Crossing-order fidelity
02Encode & comparison latency
03Retained history bytes
Include memory, storage, energy and hardware writes

Record build-time and serving memory separately, original and derived stored bytes, measured joules per completed job, and physical writes including indexing, compaction and recovery. A smaller representation does not by itself prove lower energy or longer device life.

Match correctness, freshness, durability and protection across alternatives. Encryption, authorization, adapters, network setup and output delivery belong in the complete-job comparison wherever required. No universal zero-overhead claim follows from these results.

Choose the path that fits your deployment.

Verify the supported API/SDK, data format, persistence and indexing behaviour for the release you plan to use. Match the operation-by-modality protection profile and device qualification to the workload.

Post-quantum protection · Plan a workload evaluation

Related articles

Take the next step into the thinking.

Reference / Reviewed 17 September 2026

Readable, shareable and traceable.

This reference explains 8DB’s public modality description with an explicit workload and selection criteria. It is a documentary review, not fresh execution of every operator or platform.

Public sources: 8DB modality scope; Neo4j graph concepts; the related articles above. Internal source leads and outstanding release checks remain in the editorial record.

Download this reference

Evaluate the question
your application needs to answer.

Bring the data shapes, input state, expected output and the systems you use today. Define a comparison around that complete job.

Discuss your workload