For creators · free
Build the next world.
One command puts your game or 3D experience in front of players. It works out the rest — build folder, engine, cover image, even signing you in.
Nothing to configure first. No manifest to hand-write.
Or don’t type anything.
Install the skill and ask your agent. It builds the project, writes the manifest, and runs the publish for you.
> list this on VYRLD
Building… 7 files, 2.2MB
Detected engine: three
Wrote platform.json
✓ scanned — no findings
✓ live at vyrld.com/g/drive-route-66What that command actually does.
- 01
Finds your build
Looks for an index.html in dist/, build/, out/, or public/.
- 02
Detects your engine
Reads package.json — Three.js, Babylon, PlayCanvas, R3F.
- 03
Writes platform.json
Slug, title, entry, cover image. Commit it; later publishes reuse it.
- 04
Signs you in
Opens a browser once. Nothing to copy or paste.
- 05
Scans and uploads
Then prints the URL of your live page.
One requirement: build your project first. The CLI uploads build output, not source.
Questions
- What can I publish?
- Anything that builds to static files. Three.js, Babylon, PlayCanvas, React Three Fiber, raw WebGPU, hand-written canvas, or Rust compiled to WASM. No SDK, no engine to switch to.
- Does it cost anything?
- No. Hosting and bandwidth are on us, and a world that goes viral costs you the same as one nobody plays. Creator payouts are the next thing we build.
- What gets rejected?
- Bundles that register a service worker, match a known cryptominer, or ship executables. Cookie access, frame-busting and password inputs get flagged for a human rather than blocked. Your first publish is reviewed; after that they go live instantly.
- My world is blank after publishing.
- Each world runs on its own isolated origin, so it has to be self-contained. External scripts, CDN fonts, and absolute paths like /assets/x.png will not resolve. Use relative paths and vendor your dependencies.
- Can I publish from CI?
- Yes. Set VYRLD_TOKEN from a dashboard key and pass --yes. It takes priority over the saved login.
Want the full manifest reference?
Every field, what it defaults to, and what the scanner checks.
Read the reference