Creators of8DB

Explore the models / 8DB

Point clouds

Find structure in a field of points.

Work with sampled geometry and supported attributes, then connect spatial neighborhoods to the broader observation.

Explore the capabilitiesSee a complete workload
Sample · search · inspect
Model / Point cloudsConceptual diagram
point clouds representation: conceptual diagramNEIGHBORSSAMPLES → NEIGHBORHOODS → STRUCTURE
A point sample outlines a surface. Highlighted neighbors identify a local region of interest.

Start with the operations
your question needs.

  • XYZ nearest-neighbour queries
  • Region queries and confidence-aware filtering
  • Rejection of nonfinite coordinates on recorded execution paths

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

Attribute coverage and retention depend on the representation. A downsampled view need not retain every source attribute. Registration, segmentation and defect classification are separate operations to qualify.
Connected native models

Keep the next question within reach.

A point set is more useful when the application can follow it back to the observation and forward to the asset’s inspection history. 8DB’s native shapes and relationships provide building blocks for that workflow.

meshes representation: conceptual diagramVERTICES + FACES → CONNECTED SURFACE
Meshes

Keep the surface, and what it describes.

Connect · surface · inspect

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

Follow the relationship to a better answer.

Connect · traverse · follow

Explore model ↗
documents representation: conceptual diagramSOURCECONTEXTDOCUMENT → PASSAGE → EVIDENCE
Documents

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

Inspect the measured surface around a component

point clouds representation: conceptual diagramNEIGHBORSSAMPLES → NEIGHBORHOODS → STRUCTURE
Step 1 / Point clouds

Receive an XYZ scan with capture metadata

A point sample outlines a surface. Highlighted neighbors identify a local region of interest.

Next: Validate coordinates

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. Receive an XYZ scan with capture metadata
  2. Validate coordinates and retain the source link
  3. Select a component region and nearby points
  4. Relate the selected points to geometry and earlier inspections
  5. Present the measured evidence for an inspection decision

Count decoding, registration if required, storage/indexing and evidence assembly. A neighbourhood-query benchmark alone is not a defect-detection result.

Compare a realistic alternative.

Spatial stacks are realistic alternatives. Use their supported dimensionality and functions as the baseline; include any separate scan-processing library actually required by the job.

PostGIS reference

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.

01Point density & answer quality
02Neighborhood query latency
03Load & index memory
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; PostGIS reference; 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