Open
What’s open, and what the tools add.
OpenXP is an open standard with an open core. You can author, run, and own a complete experience at a single venue with nothing but the open runtime. One experience never requires the cloud.
From the OpenXP manifesto: Warmth is the texture of welcome. Tension is the held breath before resolution. Wonder is the moment everything shifts. This is the language Shakespeare wrote into his stage directions — the through-line every memorable experience is built on. His plays endure because they admit the audience as the final author of meaning. The OpenXP experience format makes that language declarative, structured, and portable.
The foundation
Everything you need is open.
Everything required to author, run, and own an OpenXP experience is open source.
The open standard your experience file is written in, published under Creative Commons. No one owns it.
View on GitHub →Parse, validate, and generate OpenXP experience files.
View on GitHub →Additional tools and building blocks for authoring on the open format.
View on GitHub →Standalone engine that runs your experience in any venue — no cloud, no special tool required.
View on GitHub →MCP connectors that speak to the hardware: lights, sound, motion, sensors, screens…
View on GitHub →Your experience runs on the open runtime, on your own hardware, for good. No special tool is required to author it, run it, or own it.
Your data
Your ideas stay yours.
You trust XP Studio with the thing that matters most — your unreleased ideas. So we treat them the way the spec treats sensitive guest data: processed in the moment, never retained, never used to train anything.
When you use the AI, your inputs are sent to OpenXP, which prepares the request and calls the model provider. They are used to fulfil that request and nothing else. We do not store them, and we use providers under terms that exclude training on your data. Everything is encrypted in transit.
And if that is still not enough, you never have to use it. Write the experience file by hand, or generate it programmatically, and no part of your work touches the AI or our servers. The runtime and the format are open, so the most private path is always there.
Storage follows the same principle. Your work is saved to a personal data pod — an open, portable store that answers to you, built on the W3C Solid protocol.
By default your pod runs on your own machine. You can point it at any Solid-compliant provider instead, or use a managed pod when you work as a team. Wherever it lives, your work sits in an open, human-readable structure in a store you control — not in our database.
The bottom line
Your work is yours. Forever.
Whatever you make in XP Studio is output as an open-standard .xp file. It runs on the open runtime, with or without the tool, forever. The foundation is open, the output is open, and the file you create is human-readable and fully owned by you.