The site
The environment, straight from architectural, site or floor plans — or from photos of the site, with the objects separated out first.
- From plans or site photos
- Photoreal walkable worlds from pictures or a video (early access)
Digital twins · Industrial sites
Every digital twin stands on a 3D model of the real site — scanned, cleaned and rebuilt by hand, and that is where twin budgets go. Zetta 3D generates it from your plans and photos instead: the site and every object in it, separately, composed into one scene anyone can open from a link.

Hexagon digital twin study (660 executives, 2024); scan-to-BIM cost guides, 2025–2026; industry delivery estimates. Figures are orders of magnitude, not quotes.
See it
The problem
Companies believe in twins; few of them scale. The reasons repeat across industries, and most of them are the 3D.
Scanning is the cheap part. Turning the scan into a usable model is people modelling, for weeks.
Generation replaces hand modelling. Photos and plans are enough — no crew on site.
A point cloud or a photo mesh has no pump, conveyor or crane in it — only a surface shaped like one.
Every object is generated on its own, so it is an object from the first minute: select it, move it, swap it.
Scans and CAD exports run to tens of millions of polygons and have to be cut by 95–99% before they run in real time.
Each object has its own polygon budget and clean topology, so the whole site runs on a phone.
Older equipment has no usable CAD. What is not built yet exists only on drawings few people can read.
Equipment comes from photos; the future state comes from the plans, with alternatives to compare.
A new machine or a moved rack means a re-scan at five or six figures, and more modelling.
Generate the one thing that changed and swap it in. No re-scan.
Twin platforms need licences, workstations and trained people — so the people who decide never see it.
One link that opens in a browser, plus Unity and open exports for the teams that need them.
Every platform assumes someone else built the model. Nobody makes it.
How it works
We do not capture a site and cut it apart. The environment and every object are generated separately, so each one is its own entity from the first minute — selectable, movable, swappable, ready for data.
The environment, straight from architectural, site or floor plans — or from photos of the site, with the objects separated out first.
Every crane, pump, rack, forklift and door, generated from its own photos as its own light object.
Site and objects composed into one scene, with behaviour included, and delivered as a link anyone can open.
Floor and site plans give the environment directly. Each object is generated from its own photos.
Segmentation first separates the environment from the objects in the pictures, then each is generated on its own.



How we compare
| Approach | The real site, as objects | Separate objects | Runs on a phone | No crew on site | Photoreal look | Change one thing, no re-scan | Survey-grade precision |
|---|---|---|---|---|---|---|---|
| Laser scanning & scan-to-BIMMeasured geometry, to millimetres | Partly | Partly | No | No | Partly | No | Yes |
| Photo capture & splatsA photoreal look, captured fast | Partly | No | Partly | No | Yes | No | No |
| CAD & BIM modellingExact objects with engineering data | Partly | Yes | No | Yes | No | Partly | Yes |
| AI 3D generatorsFast, cheap single assets | No | Yes | Yes | Yes | Partly | Partly | No |
| Zetta 3DA real site and its objects, from photos and plans, composed in one link | Yes | Yes | Yes | Yes | Yes | Yes | No |
YesYesPartlyPartly, or only in some casesNoNo Survey-grade is the one column we leave to scanning — see accuracy below.
| Task | Today | With Zetta 3D |
|---|---|---|
| One piece of equipment with no CAD | 4–10 hours of hand modelling | Minutes, from photos |
| A 50,000 sq ft building | 1–2 days scanning, then 1–3 weeks modelling | The composed site, objects included, in days |
| A warehouse of repeated equipment | Thousands of assets at hours each | Generated once, reused across sites |
| A change on site | A re-scan at $10,000–100,000+, then more modelling | Generate the new object and swap it in |
| A project not yet built | $600–2,500 a rendered still | A future-state twin from the plans, alternatives included |
A textured object with PBR materials costs 68 credits (€0.68) on our self-serve plans — against hours of modelling by hand. Site projects add service work, and still start an order of magnitude below scan-and-model.
Accuracy, plainly
Positions and footprints follow your plans when you give them. Every deliverable carries an accuracy label, and where millimetres matter our objects sit beside a survey scan of that zone instead of replacing it.
Here, a survey scan of that zone — with our objects beside it.
What we deliver
Six ways in. An asset library or the missing assets are the easiest place to start; twin updates keep a twin true as the site changes.
Your real equipment, generated from photos: light, reusable and exportable.
Plans and photos in; a composed twin, behaviour included, out as one link.
The equipment your scan or CAD twin is missing, generated and placed.
What is not built yet, from the plans, with alternatives to swap and compare.
Heavy meshes rebuilt to run in real time, with clean topology.
When the site changes, objects are added, moved or swapped — not rebuilt.
Where each part stands
We will sit on top of the data you already collect — not replace your meters or your building and energy management.
The plans or photos of one site, and photos of the equipment in it. One site, fixed scope, a first twin in weeks — in open formats you keep.
enterprise@zetta3d.ai