Current scope
Free public demo, no account system, no cloud sync, local browser persistence only, and a WebGL compatibility mode when WebGPU is unavailable.
Inspect, run, and self-host
Open Source 3D Building Editor With Live Demo and Local Setup
Start with the live demo, then inspect the repo and boot the Next.js app locally with Bun if you want an open source 3D building editor you can self-host.
Try The Open Source 3D Building Editor Before You Touch Infrastructure
Open the live editor first to confirm that this open source 3D building editor fits your workflow, then move into repo inspection only if you want to customize or self-host it.
That sequence lets you judge the editing experience before you spend more time on local setup or deployment.
Start Locally With the Bun Setup Path Already Documented
The repository already documents a Bun-based local setup, so engineers can install dependencies, start the Next.js app, and open the live editor without reverse-engineering the project structure first.
That gives you a direct path from trying the live demo to running it yourself, without forcing you to guess how deployment is wired together.
- install dependencies with bun
- start the local Next.js app and visit http://localhost:3000/editor
- deploy the public demo through a standard Vercel flow
Know the Scope and Limits Before You Commit
Today the editor covers practical early-stage building and interior editing tasks such as walls, roofs, slabs, ceilings, doors, windows, levels, zones, item placement, local autosave, undo and redo, and JSON import or export.
It is equally important to say what is not there yet: no account system, no cloud sync, and local browser persistence only. The best experience comes from WebGPU-capable browsers, but the current editor also falls back to a WebGL compatibility mode with reduced effects when needed.
Know What To Configure Before You Deploy
The README keeps deployment concrete. Set NEXT_PUBLIC_SITE_URL so canonical metadata, robots, and sitemap entries point at the right production domain, then deploy the Next.js app through a standard Vercel flow.
If you want heavy public item assets off the app host, use the optional NEXT_PUBLIC_ASSETS_CDN_URL for an R2-backed asset domain. That makes the self-hosting story more actionable than a vague promise to clone the repo someday.
Use This Project When You Need a Browser-Based Editor You Can Inspect and Self-Host
This fits teams that want a browser-based 3D building editor they can try in the public demo and later run in their own environment.
It is not built for downstream BIM delivery or feature-heavy cloud collaboration. Making that boundary explicit helps you decide quickly whether this workflow matches your needs.
Run the project locally before you self-host
Use the setup notes below to see how the repo behaves on your machine before you spend more time on self-hosting or customization.
Quickstart
bun install
bun run dev
# then visit http://localhost:3000/editor and check whether the browser uses WebGPU or WebGL compatibility modeBest for
People who want to try a browser-based 3D building editor now and keep the option to run it themselves later.
Not for
Production BIM delivery, cloud collaboration, or teams that need every legacy browser to match the full WebGPU experience.
Frequently asked questions
Can I run this open source 3D building editor locally?
Yes. The public demo repository documents a Bun-based local setup, so you can install dependencies, start the Next.js app, and open the live editor locally without reverse-engineering the workspace first.
What deployment path does the public demo use?
The public demo uses a standard Vercel-hosted Next.js deployment. The repo also documents environment variables such as NEXT_PUBLIC_SITE_URL and an optional R2-backed asset CDN path when you want heavy public items off the app host.
What should I configure before a production deployment?
Set NEXT_PUBLIC_SITE_URL so canonical metadata, robots, and sitemap output point at the correct deployed domain. If you want heavy public item assets off the app host, use the optional NEXT_PUBLIC_ASSETS_CDN_URL for an R2-backed asset domain.
Does this project include accounts, cloud sync, or collaboration today?
No. The scope is intentionally lighter weight: no account system, no cloud sync, and local browser persistence only. Teams that need multi-user collaboration will need to add those capabilities separately.
What browsers work best for the live editor?
The live editor works best in browsers and devices with WebGPU support. When WebGPU is unavailable, the editor falls back to a WebGL compatibility mode with reduced visual effects, so you can still inspect the workflow in more environments.
Is this a full CAD or BIM replacement?
No. The current project is best used for early layout work and browser-based building editing. It is not a full downstream BIM platform, documentation system, or cloud collaboration suite.
Inspect, run, and self-host
Try the live editor, then inspect the repo
Open the public demo to verify the workflow, then review the local setup and deployment path if you need an open source 3D building editor as a browser-based starting point for self-hosted work.