Installation
Choose the deployment method that works best for your organization. TigerIdentity supports SaaS, self-hosted, and Kubernetes deployments.
Prerequisites
Before you begin
- Node.js 18+ or Python 3.9+ (for CLI)
- Docker 20+ and Docker Compose 2.0+ (self-hosted only)
- Kubernetes 1.24+ and Helm 3.8+ (Kubernetes only)
- Access to identity sources you want to connect (Okta, Azure AD, etc.)
Installation Methods
Choose the deployment option that best fits your requirements and infrastructure.
SaaS (Recommended)
Fully managed service with zero infrastructure overhead
Key Features
- Instant setup - no infrastructure required
- Automatic updates and patches
- 99.99% uptime SLA
- Built-in monitoring and alerting
- SOC 2 Type II compliant
Sign up for an account
Visit tigeridentity.com and create your organization
Get your credentials
Copy your API key and organization ID from the dashboard
Start integrating
Use the API or CLI to connect your identity sources
Self-Hosted (Docker)
Run TigerIdentity on your own infrastructure
Key Features
- Full control over data and deployment
- Air-gapped environment support
- Custom networking and security
- Single-tenant isolation
Download docker-compose.yml
Get the official Docker Compose configuration
Configure environment
Set required environment variables
Start services
Launch all TigerIdentity services
Kubernetes
Production-grade deployment with Helm
Key Features
- High availability and auto-scaling
- Native Kubernetes integration
- GitOps-friendly configuration
- Multi-region support
Add Helm repository
Configure the TigerIdentity Helm chart repo
Customize values
Configure your deployment parameters
Deploy with Helm
Install TigerIdentity to your cluster
Self-Hosted with Docker
Use Docker Compose to run TigerIdentity on your own infrastructure.
1. Create docker-compose.yml
version: '3.8'
services:
postgres:
image: postgres:15
environment:
POSTGRES_DB: tigeridentity
POSTGRES_USER: tiger
POSTGRES_PASSWORD: changeme
volumes:
- postgres-data:/var/lib/postgresql/data
redis:
image: redis:7-alpine
volumes:
- redis-data:/data
clickhouse:
image: clickhouse/clickhouse-server:23
volumes:
- clickhouse-data:/var/lib/clickhouse
nats:
image: nats:2.10-alpine
command: "-js -sd /data"
volumes:
- nats-data:/data
tigeridentity:
image: tigeridentity/platform:latest
ports:
- "8080:8080"
environment:
TIGER_DATABASE_URL: postgres://tiger:changeme@postgres/tigeridentity
TIGER_REDIS_URL: redis://redis:6379
TIGER_CLICKHOUSE_URL: clickhouse://clickhouse:9000
TIGER_NATS_URL: nats://nats:4222
depends_on:
- postgres
- redis
- clickhouse
- nats
volumes:
postgres-data:
redis-data:
clickhouse-data:
nats-data:2. Start Services
# Start all services docker-compose up -d # Check status docker-compose ps # View logs docker-compose logs -f tigeridentity
3. Verify Installation
# Health check
curl http://localhost:8080/health
# Expected response:
# {"status":"healthy","version":"1.0.0"}Kubernetes with Helm
Deploy TigerIdentity to Kubernetes with our official Helm chart.
1. Add Helm Repository
helm repo add tigeridentity https://charts.tigeridentity.com helm repo update
2. Create values.yaml
# values.yaml
replicaCount: 3
image:
repository: tigeridentity/platform
tag: latest
pullPolicy: IfNotPresent
ingress:
enabled: true
className: nginx
hosts:
- host: tiger.example.com
paths:
- path: /
pathType: Prefix
resources:
limits:
cpu: 2000m
memory: 4Gi
requests:
cpu: 500m
memory: 1Gi
autoscaling:
enabled: true
minReplicas: 3
maxReplicas: 10
targetCPUUtilizationPercentage: 70
postgresql:
enabled: true
auth:
database: tigeridentity
username: tiger
redis:
enabled: true
architecture: replication
clickhouse:
enabled: true
shards: 2
replicaCount: 23. Install with Helm
# Install TigerIdentity helm install tigeridentity tigeridentity/tigeridentity \ --namespace tigeridentity \ --create-namespace \ --values values.yaml # Check deployment status kubectl get pods -n tigeridentity # Get service URL kubectl get ingress -n tigeridentity
CLI Installation
Install the TigerIdentity CLI to manage policies, connectors, and more.
npm (Node.js)
npm install -g @tigeridentity/cli # or with yarn yarn global add @tigeridentity/cli
Homebrew (macOS)
brew tap tigeridentity/tap brew install tiger
Configure the CLI
# Set your API credentials tiger config set api-key YOUR_API_KEY tiger config set org-id YOUR_ORG_ID # Verify configuration tiger status # Expected output: # ✓ Connected to TigerIdentity # Organization: Example Corp (org_xyz789) # API Version: v1 # Status: Healthy
Environment Variables
Configure TigerIdentity using environment variables for the CLI or SDKs.
TIGER_API_KEYRequiredtk_live_abc123...TIGER_ORG_IDRequiredorg_xyz789TIGER_API_URLhttps://api.tigeridentity.comTIGER_LOG_LEVELinfoTIGER_TIMEOUT30Need Help with Installation?
Our team can help you choose the right deployment method and get set up quickly.