> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vikat.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# In-VPC Deployments

> Deploy Vikat within your private cloud infrastructure with VPC isolation, custom networking, and enhanced security controls for enterprise environments.

In-VPC (Virtual Private Cloud) deployments allow you to run Vikat entirely within your private cloud infrastructure, providing maximum security, compliance, and control over your AI gateway deployment.

## Supported Cloud Providers

Vikat supports INVPC deployments across all major cloud providers:

<div className="grid grid-cols-2 md:grid-cols-3 gap-4 my-6">
  <div className="flex items-center gap-2 p-3 border rounded-lg">
    <span>Google Cloud Platform</span>
  </div>

  <div className="flex items-center gap-2 p-3 border rounded-lg">
    <span>Amazon Web Services</span>
  </div>

  <div className="flex items-center gap-2 p-3 border rounded-lg">
    <span>Microsoft Azure</span>
  </div>

  <div className="flex items-center gap-2 p-3 border rounded-lg">
    <span>Kubernetes</span>
  </div>
</div>

## Architecture Benefits

### Security & Compliance

* **Network Isolation**: Complete isolation within your VPC with no external network dependencies
* **Data Sovereignty**: All data processing occurs within your controlled environment
* **Evidence for your audit**: every request carries an attested policy decision
  and a tamper-evident audit chain, which is what an auditor asks you to produce.
  Vikat itself holds no SOC 2, ISO 27001 or HIPAA attestation — the deployment is
  yours, and so is the certification.
* **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
* **You own availability**: the gateway runs in your infrastructure, on your
  monitoring, behind your load balancer. There is no uptime SLA from Vikat,
  because Vikat does not operate the deployment.

### 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

## Availability

There is no Service Level Agreement.

This page previously specified 99.95% monthly uptime, a downtime formula, a
partial-downtime rule and a list of monitored components. None of that was
deliverable: the gateway runs inside your network, on infrastructure Vikat has no
access to and does not monitor. An SLA is a commitment about a system you operate
and we cannot observe.

What the in-VPC model does give you is that availability is entirely within your
control — your redundancy, your failover, your alerting, with no dependency on a
vendor's status page.

## Support & Maintenance

### Technical Support

* **Support**: by email ([support@vikat.ai](mailto:support@vikat.ai)) or a shared Slack channel, during
  business hours. There is no 24/7 rota — say so rather than discovering it
  during an incident.
* **Multiple Channels**: Platform, email ([support@vikat.ai](mailto:support@vikat.ai)), 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

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

## Cost Optimization

### Resource Sizing

* **Development**: 2 vCPU, 4GB RAM minimum
* **Production**: 4+ vCPU, 8GB+ RAM recommended
* **High Availability**: Multi-zone deployment with load balancing

### Scaling Strategies

* **Horizontal Pod Autoscaling**: Based on CPU/memory utilization
* **Vertical Pod Autoscaling**: Automatic resource adjustment
* **Cluster Autoscaling**: Node pool expansion/contraction