Deployment model

Single-tenant by design

Each institution receives dedicated database and cache instances. No data, storage, or processing is shared between tenants. This separation is structural: each tenant operates on its own instances, which eliminates the possibility of cross-access at any layer.

Hosting options

The Guardline Suite can be deployed under any of four hosting options. All of them deliver the same functionality; the difference lies in the operating model and in the control over the infrastructure.

Guardline Cloud

The institution uses the infrastructure managed by Guardline. The Guardline operations team is responsible for provisioning, maintenance, updates, and monitoring.

Recommended for: institutions that prefer to delegate infrastructure operations and keep their focus on configuring and using the platform.

Considerations: the institution depends on Guardline for infrastructure changes and must validate whether the data center locations meet its data residency requirements.

Customer cloud

The deployment takes place in the institution’s own cloud (AWS, GCP, or Azure). Management can be shared between Guardline and the customer’s technical team, or taken over entirely by the customer.

Recommended for: institutions that already have cloud infrastructure and want to keep the platform within their own governance controls.

Considerations: requires coordination between the technical teams for updates and maintenance. The institution takes partial or full responsibility for the infrastructure.

Dedicated server

The platform is installed on dedicated infrastructure, in a data center chosen by the institution.

Recommended for: institutions with specific requirements for the physical location of data, or that operate with their own data center providers.

Considerations: initial provisioning and hardware maintenance are the responsibility of the institution or of the contracted data center provider.

On-premise

Installation in the institution’s internal environment, behind the corporate firewall.

Recommended for: institutions with security policies that require data to never leave their internal network.

Considerations: requires the institution to maintain the infrastructure needed to operate the platform. Updates may require additional coordination with the Guardline team.

Deployment diagram

The diagram represents the structure of an individual tenant. Each institution has its own database and cache instances, with no cross-access between tenants.

Sandbox environment

The sandbox environment is available under contract. It replicates the production configuration with synthetic data, allowing the institution to:

• Test onboarding journeys with simulated data
• Simulate transactions in the decision engine and evaluate the responses
• Operate the Decision Desk with test cases
• Validate integrations with verification providers in a controlled environment