Built to be trusted with your platform
The guardrails are the product
An assistant that can write to your platform has to be constrained by design, not by policy. These are the constraints, and none of them can be switched off from a prompt.
Six things that are always true
A human publishes
Every AI result is a draft. There is no tool in the system that lets a model make a page live.
Your tenant, only
The company the Studio edits is set by the platform, not by the model or the prompt. Data from other tenants is not reachable.
Sandboxed code
Anything that executes code runs in an isolated container with no network and no credentials, on its own machine, away from the platform's API.
EU by default
Models run on Vertex AI in the EU. Anything that would leave the EU sits behind a gate that is off unless you turn it on.
Kept twice
Every publish archives the previous version as a revision, and every change is a commit in your repository. Restore from either.
Typed tools, fixed fields
The assistant reaches only allow-listed tools, and every block has a fixed set of fields with length limits. A page that does not validate is never stored.
Who runs it
Holio Studio is part of the Holio platform, owned, developed and operated by Optiyo LTD. The platform runs on Google Cloud in European regions with its own compute in Germany, and Studio's sandbox is a machine of its own that holds no credentials.
The same team built Profrakt, the shipping platform used by more than 1,500 Norwegian online stores — which is why shipping in Holio is part of the platform rather than an integration to it.
Questions about trust
Can the assistant read another customer's data?
No. The tenant is a parameter the platform fills in on every call; the model cannot set it, and the tools it reaches are scoped to that tenant before the model sees them.
What happens if a published page is wrong?
Restore the previous revision with one click, or revert the commit in the repository. Both exist for every publish.
Is customer-written code isolated from the platform?
Yes. Functions and app components run on a separate machine under a container sandbox with no network and no credentials, and per-tenant rate limits and budgets are a precondition of the first production run.
Ask the hard questions on the walkthrough
Bring your security lead. We show the constraints, not slides.