Ctruh Studio - Create interactive 3D and XR experiences without coding
by•
Ctruh Studio is an AI-powered no-code platform that lets anyone create, customise and publish interactive 3D experiences for websites. Generate 3D assets with AI, build immersive product showcases, virtual stores, configurators and AR experiences directly in your browser.
Replies
One thing kept coming up in almost every conversation: We love immersive experiences, but they're just too difficult to build.
That became our starting point.
So we built @Ctruh Studio: a platform that lets anyone create and publish interactive 3D experiences for the web without the usual complexity.
We're just getting started, and I'd genuinely love your feedback.
If you get a chance to try it, let us know what you'd build first. Every comment helps us make the product better. 🚀
It's amazing to see something we've spent years building finally out in the world.
From the very beginning, our goal was simple: make immersive commerce easy to create and even easier to experience without downloads, plugins, or unnecessary complexity.
If you're visiting us on Product Hunt today, spend a few minutes exploring the live demos. The best way to understand the product is to experience it yourself. We'd love your feedback and support!
Watching Ctruh Studio go from an idea to a product that's now live on Product Hunt has been an incredible journey.
It's amazing to see years of hard work finally out in the world. The goal has always been simple: make immersive 3D, XR and AI experiences easy to create and experience right in the browser, without downloads or unnecessary complexity.
Proud to be part of a team that's making immersive technology more accessible for creators, brands, and businesses.
If you're visiting us on Product Hunt today, take a few minutes to explore the live demos. We'd love your feedback and support! 🚀
This looks promising. How easy is it for someone with no technical background to start using this Ctruh Studio? Congrats @sharun_kanan and team!
@hamza_afzal_butt Thanks so much, Hamza, great to see you here!
Honestly, I'm probably the best test case for your question. I'm a GTM guy, close to zero coding or design skills, and I use Studio all the time. If it needed technical chops, I'd be the first one stuck.
There's no modelling, no code, nothing to install. You start from a product photo you already have, VersaAI turns it into a 3D asset in a couple of minutes, and you build from there right in the browser. The fact that I can do it is kind of the whole point, we built it so the non-technical people are exactly who it works for.
Would genuinely love your take if you give it a spin, free launch credits, no card. Your feedback would mean a lot given how well you know this space.
Smart bet going browser-native. The thing I'd want to know as someone who builds for the web: what does dropping a Studio experience onto a product page do to its Core Web Vitals? Product pages have to rank and convert, and heavy WebGL/JS can quietly wreck LCP/INP even after you've optimized the mesh. Do you lazy-load it below the fold, ship a 2D fallback for crawlers and no-WebGL devices, and keep it off the main thread on first paint? "Immersive without tanking your SEO" might matter to a serious brand as much as the try-on itself.
@greigsb This is honestly the best question in the thread. It's the exact problem that made us build Verse Engine from scratch instead of wrapping Three.js or Babylon, so happy to go deep here.
Our rule is simple: 3D never touches the critical rendering path. Ever. We treat the product page as sacred. It loads as a normal 2D page first, the LCP element is a plain img with fetchpriority=high, and our canvas isn't allowed to compete for it. The engine and assets sit in a lazy chunk behind IntersectionObserver and idle callbacks. Until the user scrolls to it or taps it, nothing 3D is even requested. So LCP is whatever the brand's page already scores. We didn't want to be in the business of explaining to a merchant why their ranking dropped after installing us.
INP is the harder one, you're right. Naive WebGL integrations die there. We keep the heavy stuff off the main thread entirely: worker-based rendering, WASM decode for Draco/Meshopt/KTX2, WebGPU compute where the browser supports it, WebGL2 where it doesn't. GPU uploads are chunked with frame yields so hydration doesn't create long tasks.
The piece I'm most proud of is our Sequential Virtual Texturing technique. Textures never load as one big file. They're tiled across mip levels and the engine figures out per frame which tiles the viewport actually needs, at what resolution. Close surfaces pull high-res tiles, far ones pull low. Indirection map, LRU tile cache, predictive prefetch when the camera moves. A product with hundreds of MB of texture data streams in kilobyte-sized chunks, so there's no giant decode for INP to choke on. This one took us way longer to get right than I'd like to admit.
Crawlers and no-WebGL devices get the page as static HTML product images, copy, JSON-LD schema, all of it with the 3D as an enhancement layer on top. The ladder runs WebGPU then WebGL2 -> static imagery with the same DOM semantics and alt text at every rung, so Googlebot indexes the same page a five-year-old Android sees. And the container reserves its aspect ratio before anything mounts, so CLS doesn't move.
One thing nobody asks about but everyone feels is the second visit. Our other patent covers versioned asset caching. A service worker checks whether each cached asset actually changed, per scene and per texture, before touching the network. An unchanged normal map doesn't get refetched because a material somewhere else was updated. Repeat views cost near zero bandwidth. And repeat visits are where conversion actually happens, so that's not a nice to have for us.
So yes "immersive without tanking your SEO" isn't a feature we added, it's basically the thesis. VersaAI turns the product photos brands already have into 3D, the engine renders it off the main thread, and the streaming + caching layer delivers it. A 3D storefront that costs a brand its ranking is a demo, not infrastructure.
We built for the second thing.
@vinay_agastya9 thanks for going deep on this. Most 3D vendors do it backwards, canvas first with SSR bolted on later, and that's why their Lighthouse scores fall apart. Keeping the img as the LCP element and not letting the canvas fight it for that spot is the part that actually matters for commerce.
The versioned per-texture caching is the bit I'd put front and center on your site. "Repeat visits cost near-zero bandwidth" is a conversion story a growth team gets right away, even if they never learn what a normal map is. That's second-visit revenue in language they already speak.
And sequential virtual texturing to hold INP together under hundreds of MB of streaming is the kind of thing you only build after it burns you once. Really solid work, this is a lot more serious than what the category usually ships.
The platform feels simple to use, even without much technical knowledge, and the 3D, AR, and AI features save a lot of time. There is still some room for improvement, but the overall experience has been smooth and genuinely useful for presenting products in a more engaging way.
Ctruh is genuinely solving a real e-commerce pain point by letting shoppers see products in 3D/AR before buying and doing it without forcing brands into clunky app downloads or dev-heavy integrations, team has built something people actually want, not just a flashy demo.
I personally like there Versa AI outputs
Just tried it out, and I was genuinely impressed! I converted almost every item I've bought online just by clicking a photo, and it turned them into 3D models so quickly. The experience was incredibly smooth. I could zoom in really close, rotate the models from every angle, and explore every little detail.
Whenever I wanted to make a change or try something different, the AI chatbot was there to help. The AR feature was just as impressive. I could place each item on my desk and instantly see how it would look in my space.
I honestly can't wait to see where this product goes from here. Huge credit to the CTRUH team for building something this exciting!
"I've had a great experience using CTRUH Studio. The platform makes it easy to create interactive 3D, AR, and WebXR experiences without requiring advanced development skills. The interface is intuitive, the performance is smooth, and deploying immersive content is quick. It's an excellent solution for businesses looking to showcase products through engaging 3D and AR experiences."
@santosh_reddy13 nice to hear that
Congrats on the launch! The e-commerce angle makes sense: I hesitate on furniture and shoes exactly because flat photos hide the scale. One question from someone who ships to shops with heavy pages already: what does a typical embedded 3D showcase add to page weight and load time on mobile?
@artem_t Artem, this is the question serious brands care about most, so let me answer it straight.
Yes, 3D carries more data than a flat image. But almost none of it is on the critical path. The page ships as a complete 2D product page first; the engine and 3D assets are a separate lazy chunk gated behind IntersectionObserver, so nothing 3D loads until the shopper scrolls to it or taps in. Your page's load time is whatever it already scores.
Then the delivery layer, where our patents sit: geometry and textures never load as monolithic files. Our Sequential Virtual Texturing tiles everything across mip levels and streams only the tiles the viewport actually needs, near surfaces high-res, distant ones low. A product with hundreds of MB of textures streams in kilobyte-scale chunks. Model size stops mattering.
On mobile: rendering runs off the main thread (WebGPU with WebGL2 fallback), so it never fights your page's scripts, and an on-device controller eases quality to hold smoothness on that exact phone, even predicting thermal throttling before it stutters. One engine serves a budget Android and a headset alike. Repeat visits cost near-zero bandwidth thanks to per-version scene caching.
So on heavy pages: the 3D doesn't compound your weight, it's lazy-loaded, streamed in tiles, and rendered off the main thread by design. A storefront that costs a brand its load time is a demo, not infrastructure.
@sharun_kanan that answers it, the page keeps its own score and 3d only loads when the shopper actually reaches it. the tile streaming part surprised me, always assumed textures ship as one big file. appreciate the detailed reply