Give Your AI the Evidence Behind the Answer
Explore the ideas and implementation context behind this capability.
Explore the models / 8DB
Media
Make content part of the answer.
Connect media representations to metadata, source material and supported search paths within a broader data workflow.
Represent · relate · retrieve
Model / MediaConceptual diagram
Start with the operations
your question needs.
- Typed media schemas
- Registered decomposers for supported formats
- Relationships to source events and derived representations
Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application.
Format support varies. Transcription, semantic interpretation and embedding generation require appropriate codecs or models. A database that stores media does not automatically perform those tasks.
Connected native models
Keep the next question within reach.
The broader value is to connect a photograph or recording to what it documents. Media, time, location, text and relationships can become parts of one question instead of unrelated retrieval results.
Keep the source behind the answer.
Structure · search · trace
Explore model ↗Give a similar result its context.
Compare · rank · retrieve
Explore model ↗Keep the meaning in every observation.
Observe · window · analyze
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
Assemble the evidence from a recorded inspection
Receive a recording with capture time and asset identity
Image, audio and frame sequences carry different representations that can connect to one source record.
Next: Derive representations
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
- Receive a recording with capture time and asset identity
- Decode or derive representations with the required tools
- Store supported content and source relationships
- Retrieve relevant segments, text and nearby observations
- Return an inspection view with linked evidence
Count model/codec work, index readiness, transfer and consumer rendering when they belong to the input-to-value contract. Fewer data handoffs may help, but end-to-end latency and energy need measurement.
Compare a realistic alternative.
Integrated data platforms and specialist media/model pipelines are both relevant. Select the smallest realistic stack for the required output rather than assuming each media type requires a separate database.
SurrealDB data modelsCompare 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.
01Original / metadata fidelity
02Import-to-usable time
03Decode & derived-data cost
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.
Related articles
Take the next step into the thinking.
One Sealed Store for Every Shape of Data, and It Works With the Network Gone
Explore the ideas and implementation context behind this capability.
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; SurrealDB data models; the related articles above. Internal source leads and outstanding release checks remain in the editorial record.
Download this referenceEvaluate 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