Your AI, where you decide
Choose where Reelease runs, which AI model your agents use and where your data stays: from our service in Madrid to your own network with no internet access. Rules, approvals and run records are the same whatever you choose.
Where Reelease runs
You choose what your security team asks for, from starting today to no outbound connection at all.
Pilots start here
Reelease service, in Madrid
No servers to install or maintain.
- Google Cloud in Madrid (europe-southwest1)
- Kept up to date and monitored by Reelease
- Your systems’ information, in the EU
In your account
Your cloud
Reelease in your own cloud account, in the region you choose.
- Installs on your Kubernetes
- Your database and your storage
- Your networks, your keys and your access rules
In your network
Your premises
Everything on-premises, inside your network: platform, agents and AI model, on your servers.
- On your servers, next to your systems
- Sign-in with your corporate directory
- Your data stays in your network
No internet access
Isolated mode
For defense, critical infrastructure or any closed network: Reelease runs air-gapped, with no outside connection at all.
- No outbound connection, verified
- AI model on your own hardware
- Signed updates
The AI model, your choice
From the default model to an open-weight one on your hardware. You choose it per system and, if you like, per agent.
By default
They run inside the European Union.
- Per system and per agent
- Also when the agent works on your systems
- No training on your data
Your contract
Your account with your model provider, or any compatible service.
- Your terms and your billing
- The region in your contract
- Switch models without touching agents
On your hardware
An open-weight model on your own servers: you pick which one, and nothing goes to an outside provider.
- Works in isolated mode too
- Same agent, different model
- Your data stays in your network
If the chosen model isn’t available, the task stops: it never switches to another provider.
Where the agent works
It depends on the capabilities you give it: in the cloud when that is enough, and on the operator’s computer or desktop when the task needs it. In all three, the agent only runs plans signed by the platform.
Nothing to install on computers: each run works in its own disposable space, with no internet access and no access to other runs.
With the Reelease Agent, in an isolated folder for each run, without storing credentials or AI model keys.
For desktop applications: always with the operator’s consent, and every action goes into the run record.
The same everywhere
- Agents that start with no permissions
- A checked, signed plan
- Approvals your way
- A run record for every run
- Stop at any moment
See it as a table: what you install and what data flows
What you install and what data goes through it
This is how it works with the Reelease service in Madrid, where the pilot starts: you don’t install the platform. Your agents work in the cloud or on the operator’s computer, depending on the capabilities you give them, and only with plans signed by the platform. If your databases aren’t on the internet, the Client Bridge connects them from inside your network. In your cloud or on your premises it’s the same pieces, all inside your network.
| Piece | Where it is | Who installs it | What data goes through it |
|---|---|---|---|
Reelease serviceYour pilot starts here | Madrid (services) and Frankfurt (database) | No one: it’s a service | Configuration, knowledge of your systems and run records |
Reelease AgentDepending on the task | Each operator’s computer, on Mac, Windows or Linux | The operator, from a single-use link | Signed plans only. It never receives your credentials or the model keys |
Client BridgeIf needed | Your network, next to SQL Server, Oracle or PostgreSQL | Your team | Only what you publish. Your databases aren’t exposed |
AI modelThe one you choose | At the provider you choose | No one: you choose it in the platform | What the agent reads to do the task |
Reelease service
Your pilot starts here- Where it is
- Madrid (services) and Frankfurt (database)
- Who installs it
- No one: it’s a service
- What data goes through it
- Configuration, knowledge of your systems and run records
Reelease Agent
Depending on the task- Where it is
- Each operator’s computer, on Mac, Windows or Linux
- Who installs it
- The operator, from a single-use link
- What data goes through it
- Signed plans only. It never receives your credentials or the model keys
Client Bridge
If needed- Where it is
- Your network, next to SQL Server, Oracle or PostgreSQL
- Who installs it
- Your team
- What data goes through it
- Only what you publish. Your databases aren’t exposed
AI model
The one you choose- Where it is
- At the provider you choose
- Who installs it
- No one: you choose it in the platform
- What data goes through it
- What the agent reads to do the task
Your data, in the European Union
With our service, your systems’ information stays in the European Union (EU data residency) and the AI models run inside the European Union too. With your cloud or your premises, in the region you choose.
- Services in Madrid
- Analysis, planning and connections run on Google Cloud in Madrid.
- Database in Frankfurt
- Configuration, knowledge of your systems and run records, stored encrypted.
- Models in the European Union
- The AI models Reelease offers run inside the European Union.
- Queried, not copied
- The agent queries your databases at run time and makes no copies. The code you provide is used to understand your system.
Frequently asked questions
Where do actions run?
It depends on the action. The agent works in an isolated folder for each run, in the cloud or on the operator’s computer. Calls to your tools and systems go through the platform or a Client Bridge in your network. What the agent reads to do its work reaches the AI provider you use, through Reelease.
What do you install, and where does it run?
By default you install no servers: Reelease services run in Madrid and the database in Frankfurt, with your systems’ information and the AI models inside the European Union, and that is where the pilot runs. Your agents work in the cloud or, when the task needs it, on the operator’s computer, where the Reelease Agent is installed, and only with signed plans. If your databases aren’t on the internet, the Client Bridge connects them from inside your network. If you need it, we deploy Reelease in your own cloud or on your premises, in the region you choose, with a private AI model if you want one.
Where does your AI need to run?
Tell us your security and regulatory requirements, and we’ll propose the deployment that fits.