When the job crosses models.
Consider 8DB when connected geometry belongs inside a larger information workflow. Domain modeling and rendering tools remain complementary; verify supported topology and interchange.
Explore the connected workflow ↗Explore the models / 8DB
Meshes
Keep the surface, and what it describes.
Represent connected geometry for applications that need more than disconnected spatial samples.
Connect · surface · inspect
Model / MeshesConceptual diagram
The decision / Specialist context
Connect the surface to the asset it represents.
A face or vertex becomes more useful when an application can connect it to an inspection, a material record or an earlier version.
Bentley iTwin
Converts reality-capture inputs into meshes and related outputs.
Read the source ↗OpenUSD ecosystem
Scene composition and interchange across assets and tools.
Read the source ↗WHAT THE WORK REQUIRES
Khronos glTF focuses on efficient runtime delivery. Pixar describes scene composition as an interoperability problem across production tools. Neither requirement is satisfied by merely storing triangles.
Start with the operations
your question needs.
- Typed triangular mesh values
- Spatial vertices with triangle connectivity
- Related geometry records and source relationships
Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application.
A mesh type is not a complete CAD, rendering or simulation package. Verify each required geometry operation and format importer. This page does not assert automatic remeshing or physical simulation.
Connected native models
Keep the next question within reach.
Typed connectivity retains a distinction that an unstructured bag of coordinates would lose. Keeping that representation beside source records opens a path from a selected surface region to its measurement context.
Find structure in a field of points.
Sample · search · inspect
Explore model ↗Follow the relationship to a better answer.
Connect · traverse · follow
Explore model ↗Keep the source behind the answer.
Structure · search · trace
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
Review a component surface and the evidence behind it
Import supported geometry and source metadata
Vertices and faces form a surface. A selected face remains connected to its neighbors.
Next: Keep connectivity
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
- Import supported geometry and source metadata
- Preserve vertices and triangle connectivity
- Select a surface region in the application
- Resolve associated point observations and inspection records
- Present a reviewable surface with its measurement context
The full job may include a renderer or geometry library. Show these dependencies explicitly; native storage does not remove every specialist tool.
Compare a realistic alternative.
Geometry functions and specialist mesh tools remain relevant alternatives. Compare the exact operators and fidelity, then the effort to keep the surface linked to application evidence.
PostGIS referenceCompare 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.
The comparison to make: Locate a surface region and attach its inspection to the correct asset revision.
A reviewed timing for this specific job is not yet published here. The evaluation below defines the useful result and the measures that matter. Supporting measurements must match this model, its quality target and the required operating conditions.
01Topology & attribute fidelity
02Local adjacency / region latency
03Load & update 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.
Evaluate the result you need
Locate a surface region and attach its inspection to the correct asset revision.
Illustrative evaluation workflow · qualify the required operations and deployment
- 01Surface model
- 02Selected faces
- 03Asset revision
- 04Inspection record
Topology fidelity
Preserve connectivity, orientation and required attributes.
Local query latency
Time adjacency or region work with useful output.
Change cost
Measure edits, versions, import/export and retained bytes.
Bring the workload that matters to you.
Discuss an evaluation ↗We’ll use its output, quality and operating requirements to define a useful comparison.
Comparison scope, sources and next evidence
Document supported topology and formats; test round-trip geometry and local updates against a suitable mesh library plus persistent records.
Match the required correctness, freshness, durability and protection. Include ingestion, transformation, indexing and delivery in a complete-job result. Measure memory, stored bytes, energy and physical writes separately. Vendor descriptions establish offers, not independent rankings or 8DB compatibility.
- Bentley iTwin reality modeling Vendor documentation
- Pixar OpenUSD User/developer production context
- Khronos glTF Industry standard overview
Market review: 20 September 2026 · Reference revision 3.0. Linked benchmark results retain their own dates and scope. Standards are evaluation context, not an 8DB certification.
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.
8DB | Native Multimodal Data: Connect the Dots Across Graphs, Maps and Time Series
Explore the ideas and implementation context behind this capability.
8DB | What Can Geometry Reveal That Data Points Alone Cannot?
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; PostGIS reference; 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