A-Frame editor
The visual editor
for A-Frame.
Build A-Frame scenes visually in your browser — place entities, add components, write scripts — and keep readable A-Frame HTML you can export, edit and host anywhere. With AI built in.
Why AllegoryXR
Real A-Frame, edited visually.
Not a lookalike format that exports to A-Frame at the end. Your scene is A-Frame the whole way through.
Entities and components
What you place in the editor is an A-Frame entity with A-Frame components — the same model you already know.
Your own components
Register components with AFRAME.registerComponent and attach them to any entity, alongside HTML, JavaScript and CSS scripts.
Custom components →Export and host anywhere
Every scene is readable A-Frame HTML. Export it, put it in a repo, host it yourself — no lock-in.
Export guide →AI that speaks A-Frame
The built-in assistant, and agents like Claude Code through the CLI and MCP, write A-Frame fluently.
AI Agents & CLI →Under the hood
Plain A-Frame you can read.
This is the kind of markup behind a scene: entities, primitives and components — nothing proprietary in between.
- Open it in any editor, diff it in git, review it in a pull request
- Pull scene scripts with the Allegory CLI and push back only what changed
- Publish from AllegoryXR, or host the exported HTML yourself
<a-scene>
<a-entity id="lighthouse" position="-1.9 0 -1.5">
<a-cylinder radius="0.3" height="1.8"
color="#F4F1EA"></a-cylinder>
<a-entity light="type: point; color: #FFCF5A"
position="0 2.4 0" flicker></a-entity>
</a-entity>
<a-box color="#F98A1F" position="0.4 0.5 0.4"></a-box>
<a-sphere color="#2E63E7" radius="0.56"></a-sphere>
</a-scene>
Compare
Hand-coding, the Inspector, or AllegoryXR?
| Hand-coding A-Frame | A-Frame Inspector | AllegoryXR | |
|---|---|---|---|
| Place and move things visually | — | ✓ | ✓ |
| Readable A-Frame HTML | ✓ | ✓ | ✓ |
| Your scene is saved for you | Files you manage | Copy changes back by hand | ✓ |
| Publish one link for headsets, phones and laptops | You host it | — | ✓ |
| Built-in AI assistant | — | — | ✓ |
| CLI and MCP for AI agents | — | — | ✓ |
| Team accounts, roles and activity log | — | — | ✓ |
| Price | Free | Free | Free in beta |
Describe the component. AI writes it.
Ask the assistant in your dashboard, or your own agent through the CLI or MCP. You review and publish.
Add an A-Frame component that makes the lighthouse lamp flicker like a candle, and attach it to the lamp.
entities.showRead the lighthouse and its lamp lightscripts.pushWrote flicker.js — AFRAME.registerComponent('flicker')entities.updateUpdated: flicker attached to the lamp lightactivity.listChecked the activity log: one new script and one update, both recorded
Done — the lamp flickers. Open the scene in the editor, then publish.
Questions
A-Frame, answered.
Is AllegoryXR built on A-Frame?
Yes. Scenes in AllegoryXR are A-Frame scenes: entities with components, plus HTML, JavaScript and CSS scripts. A-Frame is the open-source web framework for WebXR, originally created at Mozilla.
Can I export my scene as A-Frame HTML?
Yes. Every scene is readable A-Frame markup you can export and host anywhere. See Export to A-Frame HTML.
Can I use my own A-Frame components?
Yes. Register them with AFRAME.registerComponent and attach them to any entity. You can write them yourself, ask the built-in AI assistant, or push them from the Allegory CLI.
How is this different from the A-Frame Inspector?
The Inspector (Ctrl + Alt + I in any A-Frame scene) is a free debugging tool for a scene that is already running; its changes are not saved unless you copy them back. AllegoryXR is where you build, save and publish scenes — with a team, AI and a link that opens on every device.
Do I need to know A-Frame to use AllegoryXR?
No. The editor is visual and the AI assistant can build for you. Knowing A-Frame simply means you can read and extend everything it makes.
Build your next A-Frame scene visually.
Free while in beta — no card required.