Deployment — Docker
Container-based execution, in your infrastructure.
Docker is a containerization and deployment technology, not a data platform. In a containerized deployment, beVault's components run in the environment defined with your teams: same deployment tools, same security rules, same operations as the rest of your application landscape.
- Runs in the environment defined with your teams
- Reproducible and isolated environments
- On-premises, cloud, or hybrid deployment
- Run by your teams, with your tools
Why it matters
What containerization changes in practice
This topic looks technical, but it's often the one that unlocks — or blocks — IT department sign-off.
On your side
In a containerized deployment, beVault's components run in the environment defined with your teams. Data never leaves that environment.
Reproducible environments
Development, staging, and production run on the same foundation, reducing discrepancies between environments.
Segregation
The component fits within your network, access and logging rules, like any other application.
Portability
On-premises, cloud or hybrid: Docker lets you adapt the platform's execution to your infrastructure environment.
Process
From installation to day-to-day operation
- 01
Technical scoping
Target environment, resources, access to source systems and the target database, applicable security rules.
- 02
Deployment
Deployment of containers in your environment, using your usual deployment tools.
- 03
Environments
Separation of working and production environments, aligned with your existing practices.
- 04
Operations
Monitoring, backups and recovery procedures handled by your teams, documented at go-live.
Frequently asked questions
Docker and beVault
Who operates the infrastructure?
Your teams. The components run in the environment defined with you, which is precisely the point for organizations with sovereignty requirements.
Is it compatible with our container orchestrator?
Compatibility depends on your container environment and its operational constraints. It's assessed during technical scoping to define the right deployment mode.
Does this change the target database?
No. The platform's execution mode and the target database are two separate choices.
What about reversibility?
The data and the structures produced stay within the environment defined with you. Deployment, operations and evolution conditions are scoped from the start.
Next step