Deployment Options & Requirements - Encord

On this page

Deployment Options
Deployment Requirements

On Premise / Air-gapped deployment options are only available to Enterprise customers.

Deployment Options

Option	Pros	Cons
Cloud	Ready to start on day 1 (no initial & on-going configuration required) Inexpensive and no maintenance required for client Secure (SOTA encryption, data resides client-side, etc.)	May not be appropriate for classified environment data restrictions
Virtual Private Cloud (VPC)	Compatible with GCP/Azure/AWS Higher level of control over application accessibility May fulfill classified and highly sensitive data restrictions	Client to maintain hardware compatibility and software versioning Requires in-house Kubernetes expertise No real-time software updates
On-Premise / Air-gapped	May fulfill classified and highly sensitive data restrictions	Client to maintain hardware compatibility and software versioning Requires in-house Kubernetes expertise No real-time software updates Expensive to set up and maintain Client has to procure hardware and maintain network setup Network and app security maintained by client

Deployment Requirements

Deployment Option	Setting up OS and Encord App	Management and Monitoring	Solution Engineer Hours
Cloud	None required	Standard cloud support	None
Virtual Private Cloud (VPC)	Terraform for rolling out environment Ansible installation script for packages Kustomize scripts for deployments	Monitoring setup Remote support Upgrade rollouts	100 hours
On-Premise / Air-gapped	Based Installation Setup (Raid + OS) Ansible installation script for packages Kustomize scripts for deployments	Monitoring setup Remote support Upgrade rollouts	200 to 250 hours

Active FAQ Vulnerability Disclosure Programme