Security
Security, sovereignty and compliance, by design
The assistant reads and proposes, a separate executor applies what you approve, and every action is recorded. Pandore is installed where your sovereignty requires.
Who holds the keys
AI never holds the keys to your production
Every change goes through the same chain. AI proposes, your rules and a person decide, and only a separate executor holds write access, just long enough to apply.
Propose and decide · read-only
AI assistant
Reads your estate and drafts the plan.
Read-onlyYour policies
Allow, bound or block every step.
Before executionYour approval
An authorized person approves. The plan is then frozen.
Plan lockedApply · the only write access
Executor
The only one with the key: ephemeral access, scoped to the approved target.
Holds the keyYour infrastructure
The approved change is applied, exactly once.
AppliedSecurity and governance
Autonomy you can put in front of an auditor
Policy runs before execution
Out-of-policy changes are blocked, not flagged after. Irreversible production changes can require two approvals.
Every action is evidence
Requests, checks, approvals and changes are written to an immutable audit log you can export.
Sovereign where you need it
Pandore is European, and it is installed where your sovereignty requires: in the EU, in your own cloud or data center, in your jurisdiction. Your estate data stays there, and with models hosted in that jurisdiction or self-hosted, nothing has to leave your boundary.
- EU residency: pass
- blocked: region outside EU residency scope
SOC 2 Type 1 and air-gapped deployment are on our 2027 roadmap. We will show you the current status on a call rather than claim a certification we do not hold yet.
Deployment
Where Pandore runs
Pandore is European, and it goes where your sovereignty requires. Your estate data stays in the place you choose.
In the EU
Hosted in the European Union, with your estate data kept in Europe.
AvailableIn your cloud
Installed in your own cloud account, or with a provider in your jurisdiction.
AvailableIn your data center
Installed on your own on-premises infrastructure.
AvailableAir-gapped
Fully isolated deployment, with no connection out of your perimeter.
2027 roadmapFAQ
Security questions
Does the AI change my infrastructure on its own?
No. The assistant is read-only. It proposes a change, a human approves it, and a separate executor applies it. The AI never holds a write credential.
Am I tied to a single AI model provider?
No. Pandore works with the AI model of your choice: your own API key, a model hosted in Europe or directly on your own servers. You can switch models, or combine several, whenever you want.
Where does Pandore run, and how does it stay compliant?
Pandore is European, and it is installed where your sovereignty requires: in the EU, in your own cloud or data center, or with a provider in your jurisdiction. It is built to support the obligations that bind regulated sectors, including GDPR, DORA and NIS2 in Europe: data kept in the jurisdiction you choose, an immutable audit trail, and a policy engine that enforces residency and approval rules before any change runs. Air-gapped deployment and formal certifications such as SOC 2 Type 1 are on our 2027 roadmap, and we will not claim one we do not hold yet.
See Pandore at work, on your own use cases
In a demo, you make a request, Pandore plans it, checks your rules and waits for your go-ahead. On your clouds, your GPUs and your compliance constraints.