Self-Hosting Verge3D vs. Publishing on Verge3D Network

Updated

Verge3D supports both self-hosted publishing and one-click upload to the cloud-based Verge3D Network, so the right choice depends on how much control you need over hosting, how much setup work you want to avoid, and where your audience already lives. If you need full control over the domain, server, and files, self-host. If you want the fastest path from a finished scene to a shareable link, use Verge3D Network.

What each option actually means

Self-hosted publishing means you deploy the exported Verge3D app on your own website or server. You manage the files, the domain, and the delivery.

Verge3D Network is Soft8Soft's cloud option: you upload your experience with one click and it is hosted for you.

Both are described as supported paths in the same workflow, so this is not a case of one being a workaround for the other.

Compare the two on the dimensions that matter

Dimension Self-hosted Verge3D Network
Where the app lives Your own website/server Soft8Soft's cloud
Setup effort You handle deployment One-click upload
Control over domain and files Full Limited to what the cloud provides
Best fit Brand sites, client work, existing web stacks Quick sharing, demos, prototypes
Further distribution Convert to mobile/desktop app, publish on WordPress/WooCommerce Same downstream options apply

The source material does not list pricing, storage limits, or bandwidth terms for either option, so treat those as things to confirm on the official licensing and store pages before committing.

Choose self-hosting when…

  • The interactive needs to sit inside an existing site, brand domain, or CMS you already run.
  • You or your team are comfortable moving exported files onto a server.
  • You want the deployment to be part of a larger web property rather than a standalone link.

Choose Verge3D Network when…

  • You want to publish immediately after finishing the scene, without touching server configuration.
  • The goal is a shareable link for review, a demo, or a prototype.
  • You are still iterating and would rather not re-deploy manually each time.

What stays the same either way

The publishing step is the last of three: compose the scene in Blender, 3ds Max, or Maya; add interactivity with Puzzles, the visual scripting environment (300+ puzzles, no coding required); then deploy. Whichever hosting route you pick, you can still convert the result to a mobile or desktop app, or publish it on WordPress/WooCommerce.

A practical way to decide

Ask one question first: does this interactive need to live on a domain I control? If yes, plan for self-hosting. If no, start on Verge3D Network and move to self-hosting later if the project grows into a production site. Because the scene and Puzzles work are identical in both cases, switching the publishing target does not force you to rebuild the interactive.