LabGL builds the engine
Splitting the material, finding the evidence, attaching the source. LabRAG and LabChure run on the same engine.
Technology
Runs in the browser, with nothing to install
Technology that answers from documents, shows 3D in AR, and turns catalogs into websites.
Stack
What the products are made of
The AI reads, the camera recognizes, and the website gets built.
AI RAG — reading
Documents are read as they are, and answers come back with the evidence and its source. The exam-question, tax and legal services run on the same foundation.
WebAR — recognizing
The camera recognizes floors, markers, print, faces and locations, and the 3D appears right there. Point your camera at a QR code and it opens.
Generative AI — building
From the material it read, it writes the text, decides what goes where and in what order, and finishes the website. Look at the result, describe it again, and it takes the shape you want.
The engine
Who builds what
The engine and the service are built by different people.
Experts build the service
On top of that engine, with their own material and their own words. The person who knows the policy, the tax code or the exam.
Why the web
How this differs from software you install
What changes is on the receiving end.
Nothing for the recipient to prepare
Anything that needs installing can be blocked by corporate security, and that is where it stops. A link opens right there, as long as a browser is available.
A fix ships immediately
The next person to open the link sees the fix. Nobody has to fetch and install a new build.
It does not care which device
One address opens the same way on any device. Nobody has to hunt down the right app for their operating system.
Operations
How we run it
Work is split so the screen never waits and no product's material mixes with another's.
Heavy work never holds up the screen
Long jobs such as reading documents or building 3D files run separately from the screen. The screen keeps responding while a job is still running.
Each product keeps its own data
Each product has its own database. One product's material never mixes with another's.
What was verified is what ships
What was verified in development is packaged whole and shipped as it is. Nothing unverified gets mixed in.
Requirements
A browser is enough
There is no separate device to buy.
Which devices are supported?
Any device running a recent web browser.
Which devices support AR?
Any current smartphone with a camera. On a desktop the 3D viewer opens, and you scan a QR code with a phone to continue into AR.
It runs in a browser. Is it slow?
The browser uses the device's own graphics acceleration. Running on the web is not what makes 3D slow.
Further reading
Guides
Written for the moment before you pick a product, when you want to know what actually runs and how.
What WebAR is
Augmented reality opened in a browser with no install. The kinds, and what happens after the QR code is scanned.
How GLB and USDZ differ
The format the web reads and the format the iPhone AR viewer reads, side by side.
AR support by browser
Which way opens in which browser. Checked October 2026.
What RAG is
How a model is made to answer from your own material, and where it falls down.
How 3D runs in a browser
WebGL and WebGPU, the order of work, and what makes it slow.