In-VPC Deployments

In-VPC (Virtual Private Cloud) deployments place the DeepIntShield data plane in your cloud boundary. Configured model providers, identity systems, telemetry destinations, and an optional managed control plane may still require explicit egress; review the deployment data-flow diagram and contract for your topology.

Supported Cloud Providers

Available targets depend on the purchased deployment package and the networking features of the target. Confirm the supported architecture with DeepIntShield before committing infrastructure:

Google Cloud Platform

Amazon Web Services

Microsoft Azure

Cloudflare

Vercel

Benefits

Security & Compliance

Network Isolation: Private ingress and controlled egress within your VPC policies
Data Sovereignty: Keep gateway-side processing in your controlled environment; configured upstream and export destinations remain part of the data flow
Compliance Controls: Can support regulated deployments when configured and operated with the required organizational controls; obtain a compliance and legal review for your use case
Zero Trust Architecture: Implements principle of least privilege with granular access controls

Performance & Reliability

Low Latency: Direct communication between services within your network
High Availability: Multi-zone deployment with automatic failover capabilities
Contracted Availability: Service levels, if purchased, are defined by the applicable order form and SLA

Control & Customization

Custom Networking: Configure subnets, routing, and security groups to your specifications
Resource Management: Full control over compute, storage, and network resources
Scaling Policies: Define auto-scaling rules based on your usage patterns

Service Level Agreement

Availability commitment

The figures below apply only when they appear in your executed SLA; the deployment architecture by itself does not create an availability guarantee.

Example contracted target: 99.95% monthly uptime for covered core components
Downtime Calculation: (Total Minutes - Downtime Minutes) / Total Minutes × 100
Partial Downtime: Reduced functionality counted as 50% downtime

Core Components Covered

The following components are monitored for SLA compliance:

Gateway instance
Log ingestion pipeline

Exclusions

SLA excludes downtime due to:

Scheduled maintenance (14-day advance notice)
Downstream provider incidents
Client hardware/software/network issues
Third-party AI provider outages
Client misuse or unauthorized modifications

Support & Maintenance

Technical Support

Critical Support: Coverage hours and response targets follow the purchased support plan
Multiple Channels: Platform, your DeepIntShield support contact, or Slack Connect
Audit Trail: Detailed logs for any data access during troubleshooting

Maintenance Windows

Scheduled Maintenance: 14-day advance notice for major updates
Security Patches: Immediate or 14-day delayed application (your choice)
Continuous Updates: Regular feature improvements with 7-day advance notice

Getting Started

Prerequisites

VPC with appropriate CIDR ranges
Kubernetes cluster (GKE, EKS, or AKS)
Container registry access
DNS configuration for internal routing

Deployment Process

Infrastructure Setup: Configure VPC, subnets, and security groups
Cluster Preparation: Set up Kubernetes cluster with required permissions
DeepIntShield Installation: Deploy using provided Helm charts or manifests
Configuration: Apply your specific settings and integrations
Validation: Run connectivity and performance tests
Go Live: Begin routing production traffic