Deployment Model
Single-tenant by design
Section titled “Single-tenant by design”Each institution receives dedicated database and cache instances. There is no sharing of data, storage or processing across tenants. This separation is structural: each tenant runs on its own instances, eliminating cross-access at any layer.
Hosting options
Section titled “Hosting options”The Guardline Suite can be deployed in four ways. All deliver the same functionality; the difference lies in the operating model and the level of control over the infrastructure.
Cloud Guardline
Section titled “Cloud Guardline”The institution uses the infrastructure managed by Guardline. Guardline's operations team is responsible for provisioning, maintenance, updates and monitoring.
Best for: institutions that prefer to delegate infrastructure operations and stay focused on configuring and using the platform.
Considerations: the institution depends on Guardline for infrastructure changes and needs to confirm that data center locations meet its data residency requirements.
Customer cloud
Section titled “Customer cloud”Deployment happens in the institution's own cloud (AWS, GCP or Azure). Management can be shared between Guardline and the customer's technical team, or owned entirely by the customer.
Best for: institutions that already operate cloud infrastructure and want to keep the platform within their own governance controls.
Considerations: requires coordination between technical teams for updates and maintenance. The institution takes partial or full responsibility for the infrastructure.
Dedicated server
Section titled “Dedicated server”The platform is installed on dedicated infrastructure in a data center chosen by the institution.
Best for: institutions with specific physical data location requirements or that operate with their own data center providers.
Considerations: initial provisioning and hardware maintenance are owned by the institution or by the contracted data center provider.
On-premise
Section titled “On-premise”Installation in the institution's internal environment, behind the corporate firewall.
Best for: institutions with security policies that require data to stay inside their internal network.
Considerations: requires the institution to maintain the infrastructure needed to run the platform. Updates may require additional coordination with the Guardline team.
Deployment diagram
Section titled “Deployment diagram”The diagram represents the structure of a single tenant. Each institution has its own database and cache instances, with no cross-tenant access.
Sandbox environment
Section titled “Sandbox environment”The sandbox environment is available under contract. It mirrors the production configuration with synthetic data, allowing the institution to:
- Test onboarding journeys with simulated data
- Simulate transactions in the decision engine and review the responses
- Operate the Decision Desk with test cases
- Validate partner integrations in a controlled environment