RakuAI turns anything your camera sees into a world your AI assistant can walk through, measure, and change.
Member ofCapture today is a phone scan in, a draggable splat out. The MCP runtime your AI drives is already live.
Capture is a phone experience. Point your camera at this QR code to open the Raku Capture web app, then scan a real space.
Or open it directly: rakuai.com/capture-app/
Raku Capture is built by an NVIDIA Inception member. We're bringing NVIDIA-accelerated 3D Gaussian splatting (the Brush trainer on A10G / L40S) to the reconstruction step so a phone scan of any room turns into an explorable splat in minutes, drawing on the program's NGC catalog and partner cloud credits. Read the announcement →
Three jobs, one pipeline. Reality goes in as video. A spatial world comes out. Then your AI assistant lives in it over MCP — it reads the scene, never silently rewrites your room.
Point a camera at a space and move around it. A phone is enough. No rig, no markers, no booth. This is where we lead, because this is the part that has to be honest before anything else is interesting.
The frames become a Gaussian splat with real geometry and scale — a scene you can orbit, measure, and anchor to. The runtime keeps authority over physics, collision, and transforms.
Your AI assistant connects over the same six-tool MCP contract the engine already exposes. It can see the scene, measure distances, simulate changes, and act — within permissions you set, every call audited.
Honest framing: the hero use case is shipping toward early access now. The others are where this goes — labeled so you know what is real today versus what is on the roadmap.
Scan a room. Then ask your assistant questions about the actual space in front of you — "will this couch fit along that wall," "how far is the window from the desk." It answers against the measured scene, not a guess.
A captured space can become a level, a backdrop, or a playable set piece inside the RakuAI runtime. We are not promising prompt-to-game. We are saying a real scan is a real, reusable part of one.
On glasses, the capture becomes a persistent spatial twin your assistant shares with you — anchored, sub-millimeter precise, built for the thermal envelope the runtime was designed around.
The longer arc is continuous capture: the world updates as you move, and the assistant reasons about it live through ingest_frame. Today that path is proven with stubs. We will say so until it ships end-to-end.
Concept media below. These are the demos on the queue, described plainly — placeholders, not staged footage dressed up as a product.
A single uncut clip: someone walks a phone around a room for about twenty seconds, and a draggable Gaussian splat of that room appears. No edit cuts hiding the work. Capture is the claim, so capture is what we show.
The same scan, now connected to an assistant over MCP. We ask it to measure a gap, check a fit, and describe what is on a shelf — and it answers from the captured scene. The point is the assistant reasoning over your space, not a stock one.
Capture is new. The runtime your AI drives is not. The six-tool MCP server is live, deny-by-default, every call audited — and any model that speaks Model Context Protocol can read a scene through it. Wire it into Claude Desktop and start asking questions about a real space.