Questions, answered.
Everything about bringing your team into HOLOH Workspaces. If something is missing, write to us and we will answer it here.
Confidential AI and agents
What the agents do, and what keeps their work private.
What does "confidential by design" mean?
Your team's data stays where it belongs. The workspace is the boundary for every agent, and any agent can switch to a confidential model that keeps prompts and outputs unreadable outside it. Both are enforced by the platform, so you never have to rely on a model choosing to behave.
Who can read what we send to an agent?
Only the people who can already see it. In confidential mode, agents run on hardware-enforced trusted execution with remote attestation, so prompts and outputs are unreadable to the model provider and to the infrastructure running the model. You turn confidential mode on for your own agent; workspace admins turn it on for coworker agents.
Can an agent see another workspace, or other people's messages?
No. An agent in one workspace knows nothing about any other. Your personal agent sees only what you see and answers only to you. Coworker agents are shared, but they stay confined to the workspace they work in.
Who decides what an agent can access?
You set up your own agent: its model, tools, skills and instructions, chosen from the models HOLOH makes available. Coworker agents are set up by your workspace admins, and your organisation's admins decide whether agents can use connectors such as GitHub. Whatever is chosen, the platform checks it on the server. Your agent can only see what you can see, and a coworker agent never leaves its workspace.
What can the agents do today?
You address an agent by name in the channel where the work already is. It reads and searches the channels you can already see and answers in the thread you asked in. It can find where a decision landed, recap a thread, write a report or do research for you. It is early, and we're building it in the open.
The basics
What HOLOH is and what you need to use it.
What is HOLOH Workspaces?
HOLOH Workspaces brings your team's chat, calendar and spatial calls together, with AI agents that work alongside you. It is confidential by design: each workspace is a boundary no agent can cross, and any agent can be switched to a confidential model that keeps prompts and outputs unreadable to the model provider and the infrastructure running it. One workspace instead of separate apps.
How does HOLOH compare to Microsoft Teams, Slack and Zoom?
Teams, Slack and Zoom each cover part of a team's day, with AI added on top. HOLOH puts chat, calendar and spatial calls in one workspace, with agents that are confidential by design. See how it compares side by side: HOLOH vs Microsoft Teams, HOLOH vs Slack and HOLOH vs Zoom.
Do we have to leave Microsoft Teams?
No. HOLOH calls run on Microsoft's own media plane, so a HOLOH participant can join a Teams meeting as an external participant once your Teams administrator has enabled it.
What do I need to join a call?
A webcam, a mic and a browser; Chrome works best. Join straight from the link, with no install or plugin. There is also a desktop app, on Windows today, with macOS and Linux to follow. You can switch between the 3D room and a flat 2D grid at any time.
Plans and billing
What early access covers, and what is not decided yet.
Can I try it for free?
Yes. HOLOH Workspaces is in early access and free while we build it. There is no card to enter and no trial that runs out.
What happens when paid plans arrive?
Nothing changes on its own. Billing is not built yet, so there is nothing to switch over, and no team is moved onto a paid plan without hearing it from a person first.
How will you count a user?
That is not decided yet. There is no seat count today, which is why the pricing page does not list one.
Is anything charged today?
No. Nothing is charged during early access, and the plans on the pricing page show the direction they are heading rather than a price list.
Security and administration
For the people who have to sign this off.
How is the rest of our data protected?
Everyone signs in through Keycloak, and what you can read is scoped to the workspaces you belong to.
Do you support single sign-on?
Everyone signs in through HOLOH's own Keycloak today. Signing in through your own identity provider (SAML) is planned for the Enterprise plan. Ask us where it stands and you get the current state, not a roadmap slide.
Can we set our own retention?
Not yet. Retention settings and an audit log you can export are planned for the Enterprise plan, and we are scoping them with the teams that need them.