8DB / The omnimodal database

One database.
Many dimensions.

Search the text. Follow the relationships. Understand the signal. Bring more of your question into the same database.

Familiar modelsRicher structuresConnected workflows

Start with the useful result

What are you trying
to make possible?

A question rarely stops at one data model.
Explore how several models contribute to a useful result.

Illustrative workflows. Each guide includes alternatives, evaluation criteria and the scope still to qualify. Prefer to start with a representation? Browse all 17 models ↓

From a native operation to a useful decision

Choose what the data should help you do.

Storing a structure is the beginning. Its operations determine which questions your application can answer.

01 / Time series

Turn a missing reading into a useful next step.

Request missing evidence, wait for late data, or recognize an interval when no reading was expected.

Respond to missing readings →
02 / BioTwin / Lineage

When the evidence changes, know which answers to revisit.

An answer can keep the same number while its justification changes. Find the dependent work that needs review.

Trace changed evidence →
03 / BioTwin / Order lattices

Keep the strongest alternatives visible.

A candidate may offer more benefit at more cost. Preserve the alternatives instead of hiding that choice inside one score.

Compare meaningful alternatives →

Distinct implementation examples, with their scope explained at each destination. See the evidence and scope →

01 / Find your data model

See the breadth.
Choose your starting point.

Select a model for a visual introduction.
Open its guide for operations, comparisons and evidence.

17 model guides

01

Records & search

Store it. Find it. Retrieve it.

4
04

Spatial data

Work with location and geometry.

4
Explore by applicationMolecular & genomic workflows

Composite applications connect several representations. They are a separate route into the library.

02 / From input to useful answer

The interesting part
is where models meet.

A familiar question often needs several kinds of data. Follow the work from its source to the answer.

Personal media / Illustrative workflow

“Find the photo from that evening by the lake.”

Similarity finds candidates. Time and place narrow the answer.

01media representation: conceptual diagramCONTENT + REPRESENTATIONS + SOURCE

Import the image

Original + metadata

Media
02vectors representation: conceptual diagramQUERYCANDIDATES → CONTEXT → RETRIEVAL

Find similar content

Search representation

Vectors
03spatial representation: conceptual diagramREGIONLOCATION + DISTANCE + CONTEXT

Add the location

Place and proximity

Spatial data
04time series representation: conceptual diagramPOINTBOUNDGAPMEANING PRESERVED THROUGH TIME →

Match the moment

Time and event context

Time series
THE USEFUL FINISH LINEThe matching image, connected to its original and context.

Import-to-searchable time · relevance · memory · stored bytes

Design example, not an executed combined benchmark. Include metadata extraction, embedding generation and permissions in the complete job.

Multimodal performance / Evidence reviewed 18 September 2026

Ownership, time and location. One complete answer.

Multimodal workload: graphs + time series + spatialSeptember 18, 2026 article
milliseconds · complete shipping query Lower is better · linear scale from zero
8DB10.8
Native graph + typed time series + spatial composition
SurrealDB332.5
3.2.4 · tuned record-range layout

Same-host synthetic shipping fixture; same four logical CPUs per server; 20 timed requests each, including HTTP and decoded JSON. Exact ships and timestamps checked. Custom Rust composition versus SurrealQL. Preparation excluded; resident-memory paths without durable completion or authentication. This measures the combination, not an isolated graph, spatial or time-series operation.

Read the results, comparison and methods →
Observed process memory: 213 MiB vs. 831 MiB

8DB used about 74% less resident memory at the recorded post-query checkpoint. Client and OS cache excluded; this is not a minimum device requirement. Energy and SSD wear were not measured.

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.

03 / The buying decision

A model list
is the beginning.

Multi-model databases such as SurrealDB already combine familiar representations. Compare what you can actually do with them, what information survives and what your team still has to assemble.

See SurrealDB’s documented models

Bring the whole question

What should your data
help you understand?

Explore your workload