Graphics systems index

The stack behind
every frame.

A researched directory of dependable APIs, engines, spatial platforms, visualisation systems and open standards for building serious real-time graphics.

Precision graphics pipeline transforming a wireframe scene through three rendering stages into solid geometry
GEOMETRY / MATERIAL / LIGHT / OUTPUTGFX-01
36CURATED SYSTEMS
7TECHNOLOGY LAYERS
Web, desktop, mobile and XR Official project and standards sources Last researched 27 Jul 2026

Graphics architecture

A frame is a
whole system.

Rendering quality depends on more than an engine. Device access, scene structure, geometry, materials, spatial data and delivery constraints must work as one deliberate pipeline.

Exploded graphics system with hardware, rendering, scene graph and presentation layers
One system, five connected layers

SYSTEM MAP / 05 LAYERS

From device capability
to useful experience.

  1. 05
    Product experienceInteraction, accessibility, fidelity and response
  2. 04
    Engine and sceneCameras, lighting, simulation and application logic
  3. 03
    Assets and spatial dataGeometry, materials, metadata, tiles and interchange
  4. 02
    Rendering APICommand submission, shaders, memory and synchronization
  5. 01
    Runtime and deviceBrowser, operating system, GPU and display hardware

Local capability check

What can this
browser reach?

The check runs only in the current browser. It does not collect, transmit or store device information.

01WebGPUChecking
02WebGL 2Checking
03WebXRChecking
04WebAssemblyChecking
05OffscreenCanvasChecking

Systems directory

Choose the layer.
Understand the fit.

The order balances production maturity, ecosystem adoption, interoperability and technical relevance. It is a practical research index, not a universal performance leaderboard.

Technology layer
36 systems shown Research snapshot: 27 Jul 2026

Interoperability matters

The model must survive
beyond one renderer.

Strong graphics systems separate durable scene and asset information from a single presentation technology. Open formats and deliberate conversion pipelines protect years of product, industrial and spatial data.

01Scene structure

Preserve hierarchy, metadata and relationships, not only visible triangles.

02Runtime delivery

Stream the right geometry, textures and tiles for the current device.

03Operational context

Connect graphics to live state, permissions, workflows and business rules.

Industrial system shown as a solid model, transparent scene graph and point cloud
SOLIDSCENE GRAPHSPATIAL DATA

Selection method

Dependable graphics
earn their place.

Every inclusion needs a credible production path, active stewardship, useful documentation and a clear role within a modern graphics system.

01

Production maturity

Shipping history, stable releases and real deployment evidence carry more weight than novelty alone.

02

Ecosystem adoption

Tooling, integrations, contributors and supported workflows indicate practical staying power.

03

Interoperability

Standards alignment and reliable data exchange reduce lock-in and protect technical choices.

04

Governance

Clear licences, active maintainers and accessible specifications make long-term adoption safer.

Before choosing a stack

Start with constraints,
not a favourite engine.

01

Experience target

Define the interaction, visual fidelity and response the user genuinely needs.

02

Device budget

Set limits for GPU memory, frame time, power, bandwidth and thermal conditions.

03

Data scale

Measure scene size, geometry density, texture weight and update frequency.

04

Interchange path

Decide how assets move between authoring, storage, review and delivery systems.

05

Fallback strategy

Plan useful reduced modes for unsupported devices, accessibility and constrained networks.

Putting graphics to work

From graphics stack
to working experience.

ADOR.IS builds real-time product experiences, digital twins, spatial interfaces, technical visualisations and dependable software around complex graphics.

[email protected]