For developers
It is also a git repository. Yours.
Every Studio project is a private repository your team can clone, edit and push. A draft is a branch, a publish is a pull request, a revert is a git operation. The Studio and your editor work on the same files.
- Repository
- One private repo per project, in an organisation with no default access
- Draft
- A branch
- Publish
- A pull request, merged by a person
- Verdict
- holio validate — the same answer in the Studio, in CI and in the sandbox
What is in the workspace
Plain files in a plain layout. Nothing you need a tool to read.
screens/
App screens as files, one per URL, built from the layout node registry.
sites/
Each website with its pages, its theme tokens and its routes, per language.
schema/
Your data objects and their fields, the source of the tables in your tenant.
functions/
Server-side code, once functions ship. The directory is already in the template.
menu.json
Where each screen sits in the navigation, and for whom.
holio.lock
Pins the registry version the workspace was validated against, so a new block type never surprises an old page.
One verdict, three places
holio validate reads the workspace and answers valid, ignored or a field-path error. The Studio runs it before it shows you a change, the pull request check runs it on every push, and the sandbox runs it before anything executes.
Three callers, one implementation. A page that validates on your laptop validates everywhere, and an unknown block type is refused against the pinned registry rather than silently skipped.
Bring your own agent — on the roadmap
Holio Code opens a real coding session on your workspace: one container per session, no network except the model gateway and the platform, no credentials inside. It reads the same files your team does and opens the same pull requests.
The desk side exists and answers today; the sessions switch on when the last two credentials are in place. We will not sell it as live until it is.
Questions from developers
Which languages?
Pages, screens, themes and schema are JSON, validated against a registry you can read. Functions, when they ship, are Python. App components are HTML that talks to the platform through a small typed bridge.
Can we work locally?
Clone, edit, run holio validate, push. The preview is the platform itself, so there is no local runtime to install: a page is a row, and the row is the preview.
Can we use our own CI?
The validate check already runs on every pull request in the workspace repository. Add whatever else your team runs; the verdict that gates publishing is the same one.
Who owns the code?
You do. The repository is private, in an organisation where the base permission is none and access is one team per customer. The platform's own code is never in it.
Ask for the workspace on the walkthrough
We open a project for you and you push the first change yourself.