Every point the sensor captured. Nothing cut, nothing tiled.

udStream does not make that trade. It renders the complete dataset at full resolution, on a standard laptop or desktop PC, with no dedicated graphics card required. What the sensor recorded is what appears on screen.

It runs where you put it. On a laptop, on your network, on-premise, or fully air-gapped with no connectivity at all.

No decimation. No thinned deliverable. No separate reduced copy. You are not looking at a representation of the survey. You are looking at the survey.

1,500 kilometres of the Bruce Highway is held and rendered as a single udStream dataset, from state scale down to a first-person view on the road surface, without changing files or waiting for anything to load.

That is not a benchmark run. It is a working dataset.

Move through the scene, find the defect, and mark it up where it is. Capture the view as a screenshot placed back into the scene, so the finding sits at the location it describes rather than in a folder somebody has to correlate later.

Then track those findings as work items against the project, with states, comments and a board, so a QA pass is a tracked piece of work rather than a pile of screenshots in an email.

Measurement in the full application covers the survey work: line, area, height, grading, profiles, volumes and export.

This is the part that changes how a survey firm communicates.

Set the scene up the way you would explain it standing on site: the cross section through the overpass, the classification filter that isolates what matters, the markup sitting where the issue is. Then publish it as a preview link and send it.

What you set up is what they get. Your client, the design engineer, the asset owner, the contractor, the person who has to sign it off. They open it from the link alone, with no account to create, no licence to buy and nothing to download.

They are inside your prepared view, at full resolution, in the browser. They can move through the site themselves and measure it: line, area, height, grading. What they cannot do is alter what you set up, which is the point of sending it.

Everyone ends up standing in the same curated reality instead of interpreting a PDF of it. A defect notice, a design query, a work order, a client update: one link, inside or outside your organisation.

That last part matters more than it sounds. They are not taking your word for a number in a report. They are checking it.

Publishing needs a Studio licence. Withdrawing needs only the permission. A licence that lapses cannot strand a link already out with a client.

udStream builds one scene from data held anywhere. A cloud scene, a file on a desktop, a network drive, your own cloud, a third party's. The sources stay where they are and compose into a single scene.

Which means two organisations can each keep their own data where it sits and work the same scene together. An asset owner holds the reality capture, an engineering firm holds the design, neither hands anything over, both work the same scene.

udStream is the client. It renders. It runs on the computers your team already has, on-premise or air-gapped, and a server is never required to run it.

udCloud is our platform: licensing and licence management, project management and access, project and usage reporting, sharing, dashboards, QA/QC documentation, and optional data hosting.

udServer is udCloud run by you, on your own infrastructure, for air-gapped operation, high security, or end-to-end control of your deployment.

Hosting with us is optional, always. Take udCloud if you want us to hold and run the data. Host it yourself, any way you like, if you do not. udStream renders at full resolution either way.

Studio administers and curates. It manages projects and access, builds the curated scenes, and publishes preview links to clients.

Analyst is the professional working seat. Full application, full resolution, the daily work.

Previewer is your clients. Free, no account, view and simple measurement.

No volume bands. No thresholds. No bundle you have to decode.

Buying for a large team? Talk to us.

Pooled or concurrent licensing is a deal-by-deal conversation. Every price published here is per named user.

Storage and egress, if you take udCloud.

Optional storage is charged at the public AWS S3 price for your region plus a 15% management fee, so you can check the base rate before you call us. Streaming egress (data transfer) is included up to 10% of what you store each month, and your storage and egress are visible in your udCloud management view, so a bill is never a surprise.

Why we are doing it: we want a small group of firms using udStream properly, on real corridors and real client work, early enough that what they tell us shapes where it goes next.

What founding customers get

• Your pricing is locked for the life of your contract.
• Up to 10 TB of your source data converted to UDS, done by us. You upload, we convert, we hand it back wherever you want it, and then you plan the rest of your archive with your team. The entitlement runs for thirty days from signing. Conversion is not hosting, and hosting stays a separate choice.
• Unlimited training for your first 90 days, as many sessions as it takes, remote or in person if you are in Brisbane, no cap on attendees. A named person here owns whether this works. After 90 days we keep helping your trained people with new features and anything that needs clarifying.
• Ongoing support for anyone who attends, informally, on new features and anything that needs clarifying. We do not put a clock on that.

What we ask

Work with us in the open. Let us name you as a customer, put a case study together once you have something worth showing, and give us a real workload to measure so our pricing stays grounded in what firms actually use.

The rates are the published rates. The cohort is about getting the right twenty firms in early, not about discounting to fill it.

Apply for the founding cohort

The Unlimited Detail engine powered Leica JetStream for more than 30,000 users. Our team built that engine, and the team that built it owns and operates it today.

Euclideon failed commercially. The technology never failed. The people who built the engine are the people who rebuilt the company: we acquired the assets and Nuclideon is what came out of it. The engine kept moving the whole time.

We build these tools with the firms doing the work, not at a distance from them. Orion Spatial Solutions, a survey firm, uses udStream in its own QA/QC workflow and has been instrumental in developing what that role actually needs. The corridor data we demonstrate on is theirs.

The Queensland Department of Transport and Main Roads is a customer. The US Navy is a customer. The technology is patented.