On-Premises Deployment

Run Protecto inside your own infrastructure or private cloud for full data residency control and air-gapped environments.

In the on-premises model, Protecto runs inside your infrastructure — your own data center or a private cloud environment (AWS, GCP, Azure).

Overview

Aspect	Details
Hosting	Customer-managed
Infrastructure	Single-tenant
Network	Fully private
Upgrades	Customer-controlled
Best for	Strict data residency or regulated environments

Area	Description
Runtime	Containerized Protecto services
Networking	Internal VPC or data center network
Data storage	Fully controlled by customer
External access	Optional and configurable

Protecto provides deployment artifacts and configuration guidance during onboarding.

You define the base URL. For example:

https://protecto.internal.company.com

All API paths remain identical to SaaS:

API	Method	Full endpoint
Mask	`PUT`	`https://protecto.internal.company.com/api/vault/mask`
Unmask	`PUT`	`https://protecto.internal.company.com/api/vault/unmask`
Data Scan	`PUT`	`https://protecto.internal.company.com/data-scan/data-scan-async`

This model is commonly used for healthcare, finance, and government organizations.

Protecto provides reference architectures and recommended defaults. No API-level changes are required when switching from SaaS to on-premises.

For on-premises or private cloud inquiries, contact help@protecto.ai to receive deployment artifacts and architecture guidance.

Was this page helpful?

Last updated 3 weeks ago