The institution hosts every component of the licensed platform on its own infrastructure. Its own cloud, its own data centre, or a combination. The institution's team operates the platform.
MonTechSys provides deployment tooling, reference architecture, documentation, and support. The institution owns operational responsibility end to end.
MonTechSys hosts and operates the licensed platform in a dedicated deployment for the institution. The institution retains governance. Data ownership, access control, audit rights, roadmap input, and exit rights.
Reduced operational burden without sacrificing ownership of policy, data, or roadmap.
The institution chooses which planes deploy in which model, per regulatory or operational requirement. The core banking plane might deploy sovereign while orchestration deploys managed. Or the other way around.
The shared substrate spans both. Data, audit, and event model remain coherent across the deployment boundary.
Start with the regulatory question. If the plane must be sovereign-deployed, the path is decided.
Then the operational question. Does the institution have platform-operations capacity to run this plane? If yes, sovereign is available. If not, managed removes the operational overhead.
Then the strategic question. Is infrastructure ownership itself the goal? Sovereign. Is the goal outcome, a modern engineered plane in production, without operational overhead? Managed. Both across different planes? Hybrid.
Every option is discussed in the technical conversation.