Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vijil.ai/llms.txt

Use this file to discover all available pages before exploring further.

This page helps you assess readiness for a self-hosted Vijil deployment. Complete this checklist before beginning infrastructure work.

​
Team Readiness

Self-hosted deployment requires coordination across multiple teams. Verify you have access to people with these skills:
Skill AreaRequired ForCan You Access?
Kubernetes administrationCluster setup, Helm deployments, troubleshootingRequired
Cloud IAM (AWS/GCP/Azure)Service accounts, role policies, cross-service permissionsRequired
Database administrationPostgreSQL provisioning, backup configurationRequired
Network/SecurityVPC configuration, security groups, TLS certificatesRequired
Auth0 administrationApplication setup, SSO configurationRequired
In smaller organizations, one platform engineer may cover multiple areas. The critical factor is having someone with permissions to provision each resource type.

​
Timeline Expectations

A typical deployment takes 2–4 weeks:
PhaseDurationActivities
Prerequisites1 weekProvision infrastructure, configure networking
Deployment1 weekInstall Vijil, configure data stores
Integration1 weekConnect Auth0, test agent connectivity
Validation3–5 daysTest evaluations, verify Guardrails
Factor in additional time if you need to request cloud resources through an internal procurement process.

​
Infrastructure Requirements

Before deploying Vijil, ensure you have the following resources available:
  • AWS Account: You must have access to an AWS account with sufficient permissions to create and manage EKS clusters, RDS/Aurora databases, OpenSearch domains, and S3 buckets.
  • AWS CLI: Install and configure the AWS CLI on your local machine.
  • kubectl: Install kubectl to interact with your Kubernetes cluster.
  • IAM Permissions: Ensure your AWS user/role has permissions to create and manage EKS, RDS/Aurora, OpenSearch, and S3 resources.
  • Basic Kubernetes Knowledge: Familiarity with Kubernetes concepts and resource management is required.
  • Networking: Understanding of VPC, subnets, and security groups in AWS.

​
Dependencies

The following AWS resources and services are required for a production deployment of Vijil Evaluate:

​
Core

  • Amazon EKS Cluster: The primary compute environment for running Vijil Evaluate services.

​
Datastores

  • PostgreSQL Database: Used for persistent storage of application data. This can be provisioned using:
    • Amazon Aurora (PostgreSQL-compatible) – recommended for high availability and scalability.
    • Amazon RDS for PostgreSQL – suitable for smaller-scale or non-production deployments.
    • Any other PostgreSQL solution you want that your EKS cluster has permission to access

​
Object Storage

  • Amazon S3: A single S3 bucket for storing evaluation artifacts, configuration files, Diamond resources, and file uploads. You will also need to add CORS configurations to the bucket so that it can accept signed URL file uploads from your browser. Below is an example of what to add in an AWS S3 bucket’s CORS configuration (it will be very similar in the cloud storage equivalents of other cloud providers):
    JSON
    [
  {
      "AllowedHeaders": [
          "*"
      ],
      "AllowedMethods": [
          "GET",
          "PUT",
          "POST",
          "HEAD"
      ],
      "AllowedOrigins": [
          "https://*.yourdomain.com"
      ],
      "ExposeHeaders": [
          "ETag",
          "x-amz-request-id",
          "x-amz-id-2"
      ],
      "MaxAgeSeconds": 3000
  }
]

​
Authentication

  • Auth0 - You will require an Auth0 account and the ability to create an Auth0 application in your tenant

​
Summary Table

DependencyAWS Service / ProviderPurposeWho Creates It
ComputeEKSRun Vijil workloadsCustomer
Relational DBAurora/RDS (PostgreSQL)Persistent application dataCustomer
Object StorageS3Evaluation artifacts, configs, file uploadsCustomer
TLS CertificateACMHTTPS for console and API domainsCustomer
DNSRoute 53Domain routing for console and APICustomer
Container ImagesECR (cross-account)Pull Vijil container imagesVijil + Customer
Diamond ArtifactsS3 (copy to customer bucket)Evaluation harnesses, detector configs, model weightsVijil copies to customer S3
AI RuntimeBedrock AgentCoreCustom harness executionCustomer
Block StorageEBS CSI DriverPersistent volumes for telemetryCustomer
Pod AWS AccessEKS Pod IdentityScoped AWS credentials for podsCustomer
LLM API KeyGroq, OpenAI, Anthropic, or localDiamond evaluation and report generationCustomer
Evolution EngineDarwin (separate Helm chart)Agent evolution (optional)Customer
Items marked Vijil + Customer or Vijil require coordination with the Vijil team. Request ECR access and Diamond artifact copies early to avoid blocking your deployment.
Note: All resources should be provisioned in the same AWS region for optimal performance and cost efficiency.
Once these pre-requisites and dependencies are in place, you can proceed to the deployment steps.
Last modified on May 13, 2026