Emaze Tours - Interactive Virtual Tour Builder
Her own 3D tour builder instead of a foreign service, launched in 2 weeks
An online service for teachers: a tour is built from slides and the viewer walks through it in the browser like a museum hall, by link or on the author's own site.
- Built in
- 2 weeks
- from the first commit on 6 July to handover on 18 July 2026
- Scale
- 333+ authors
- have made tours, as of 3 October 2026
- Volume
- 500+ tours
- 86+ published, as of 3 October 2026
Before
Maria showed a tour made on Emaze and asked for the same service of her own: on her domain, without a foreign subscription and with user data kept in Russia. There was no spec, only the example.
What I built
A web service on the client's domain: a slide editor, a 3D hall where the camera walks the viewer from slide to slide, publishing by link and embed, accounts, limits and an admin panel. Server and data in Russia, mail from her domain.
After
The service runs on prozumentova.ru. Teachers build and publish tours on their own, and the administrator invites people from an Excel list and sets limits. A guide for authors and the administrator was handed over.
What the client got
-
An editor like a slide deck
Text, images, YouTube, Rutube and VK video, shapes, drawing and background music.
-
A live 3D hall
A rotunda or a straight hall: the camera walks the viewer to each slide like a guide.
-
One-click publishing
A link to the tour and ready-made embed code for any site. Opens on a phone.
-
Accounts and limits
E-mail sign-up, a "My tours" section and a free-tour limit the admin sets.
-
Admin panel
Every tour and user, roles, blocking, invitations by e-mail and from an Excel list.
-
Its own server in Russia
HTTPS on the client's domain, mail from her address, data stored under Russian law 152-FZ.
How it looks
How it was built: details and stack
Tech Stack
The brief
Maria Prozumentova showed a tour built on Emaze, a foreign service, and asked for the same service of her own. This was not about one tour but about a builder: authors put tours together from slides and publish them, and viewers walk through the finished tour in the browser.
There was no spec, only that example and three conditions:
- the service runs on her own domain;
- no foreign subscription;
- user data is stored in Russia.
What was built
A fully working service: creating tours, viewing and publishing them, and managing users and content. Grouped the same way as in the report for the client.
Tours and viewing
- Two hall types to choose from: a round rotunda and a rectangular hall.
- The camera “walks” smoothly from one slide-painting to the next, like a real visitor.
- Realistic frames, visitor figures and lighting.
- A background image on the wall and background music.
Editor
- Slides: add, duplicate, reorder, delete. Up to 20 slides per tour.
- Objects: text, images, video, shapes, frames, brush drawing, arrows, stickers and emoji.
- Text formatting and alignment, layer order.
- Slide background: an image or a colour.
- Autosave: the draft saves itself on the server.
Publishing
- Publishing by link in one click.
- Unpublishing: the link stops opening.
- Ready-made code to embed the tour on another site.
- The viewer and the editor work on a phone.
Images, audio, video
- Upload your own images (PNG, JPG, WebP, GIF, up to 10 MB) and audio (MP3, OGG, WAV, M4A, up to 20 MB), with format and size checks.
- Images are scaled down and converted to WebP in the browser before upload, so the hall loads lighter.
- A personal file library that only its owner can see.
- Video is added by link from YouTube, Rutube and VK, with nothing uploaded to the server.
Accounts and access
- Sign-up and sign-in with e-mail and password, password recovery.
- A “My tours” section: edit, unpublish, delete. Deleting asks for the tour’s name, so nothing is removed by accident.
- A free-tour limit set by the administrator.
Admin panel
- Every tour: counters, search by title, a status filter, sorting, and viewing, editing or deleting any tour.
- Users: create an account that is active at once, invite by e-mail, grant or remove the admin role, block, delete an account and, optionally, its tours. Admins cannot change their own account, which guards against locking themselves out.
- Limits: a shared free-tour limit and a personal limit for any single user.
- Bulk invite: addresses are pasted as a column from Excel or loaded from an Excel, TXT or CSV file. A new address gets a “set a password and sign in” e-mail and a tour limit, while an existing user only has their limit updated; the service asks for confirmation before sending.
Reliability and privacy
- Its own server in Russia, data stored under Russian law 152-FZ.
- HTTPS on the prozumentova.ru domain.
- E-mails (invitation, sign-up confirmation, password reset, address change) come from the client’s domain, in Russian and in a branded template.
- Only the owner can change a tour and its files: the server checks it, and stored files are separated by owner.
How it works
The service is built on Next.js 16 (App Router) and TypeScript. The key decision: the hall is rendered in 3D but edited in 2D. The hall is a real Three.js scene in React Three Fiber, with walls, light, frames, visitor figures and a camera that walks the viewer to each slide. The objects on a slide are flat 2D layers with plain x, y, width, height, rotation coordinates. They are moved, resized and rotated with React Moveable handles, as in Canva, and the editor state lives in a Zustand store. Authors never have to think about 3D space: they build a slide as in a presentation, and in the hall the same slide hangs on the wall like a painting.
Accounts, data and files are on Supabase: Auth for sign-in, Postgres for tours and objects, Storage for images and audio. Supabase is self-hosted on the service’s own server in Russia rather than in the cloud. Stored files are separated by owner and served through signed links, and video links are accepted only from allowed hosts.
The code is split into layers: validation → repositories → services → actions → UI. Zod checks the input, database queries live in repositories, rules in services, and server actions connect them to the interface. That keeps business rules out of the components.
The app is built as a Docker image and runs behind Caddy, which obtains and renews the Let’s Encrypt HTTPS certificate for the domain on its own. Mail goes out from the client’s domain. The main flows are covered by end-to-end Playwright tests: slides, moving objects, drawing, backgrounds, publishing, audio, the admin panel and the mobile panels.
How the work went
- 6 July 2026 - first commit.
- 8 July - the first working version on the server, in Docker behind Caddy with HTTPS. The same day brought mobile viewing, video previews and autosave.
- 11 July - drawing, stickers, background music, a personal account with a limit, the first admin panel and legal pages with consent at sign-up.
- 15-17 July - editing restricted to the owner, slide backgrounds, user management, Playwright tests, a moulded frame and a camera that no longer passes through walls, sign-in by invitation.
- 18 July - handover. By that day Supabase had moved from the cloud to the service’s own server in Russia, and the service was live on prozumentova.ru. Maria received a project report and a guide for authors and the administrator, as PDF and HTML.
- Late July - bulk invites from Excel, TXT or CSV and a personal limit for each user. A video walkthrough of almost 12 minutes was recorded for the administrator.
- August - a configurable publication limit, clear errors when an invitation fails to send, with a fallback link, and the legal documents in the site footer.
What I took away
Render in 3D, edit in 2D. Real 3D editing is a wall for anyone who is not a designer. Here the hall has depth only when viewed, while a slide is put together like an ordinary presentation. The author gets the museum-hall effect without ever touching 3D.
A live draft on the server instead of a document. There was no spec, and a working version took its place: two days after the first commit the service already opened by link, and every change after that could be seen in it straight away instead of being discussed on paper.
The guide is part of the delivery. Along with the service, Maria got a report and a guide for authors and the administrator, and later a video walkthrough. A service with an admin panel is worth something when the administrator can invite people, set limits and sort out tours on her own.
The data in the admin and user-list screenshots is illustrative.
Services used in this project
Related case studies
- A BlaBlaCar-Style Rideshare ServiceA web app for finding travel companions in Russia, built for a client on the BlaBlaCar model. It opens from a link in the phone's browser, with no App Store, Google Play or install.
- Novoe Vremya - Medical & Education Corporate SiteA single corporate site that forks into a medical center and a training center, built to pass Russian licensing checks.