Getting Started with TigerGate
Deploy TigerGate and run your first security scan in under 10 minutes
Installation
Install on K8s, Docker, ECS, or bare metal
Quick Start Tutorial
Run your first scan in 5 minutes
Architecture Overview
Understand how TigerGate works
System Requirements
Prerequisites and supported platforms
Installation
TigerGate supports multiple deployment options. Choose the method that best fits your environment.
Kubernetes (Recommended)
kubectl apply -f https://install.tigergate.dev/agent.yamlOr use Helm: helm install tigergate tigergate/agent
Docker
docker run -d --privileged \
-e TIGERGATE_TOKEN=your_token \
tigergate/agent:latestAWS ECS
Add the TigerGate sidecar to your task definition:
{
"name": "tigergate-agent",
"image": "tigergate/agent:latest",
"essential": false,
"environment": [
{"name": "TIGERGATE_TOKEN", "value": "your_token"}
]
}Quick Start Tutorial
Sign up for TigerGate
Request a demo at tigergate.dev/demo
Connect your cloud accounts
Add AWS, GCP, or Azure credentials with read-only access for cloud scanning
Connect your repositories
Link GitHub, GitLab, or Bitbucket for code scanning (SAST, SCA, secrets)
Run your first scan
Click "New Scan" and select the resources to scan. Results appear in minutes.
Deploy the eBPF agent (optional)
For runtime protection, deploy the agent to your Kubernetes cluster or servers
Architecture Overview
TigerGate uses a centralized SaaS architecture with optional agents for runtime monitoring.
Platform Components
Only the eBPF agent runs in your environment. All scanning, analysis, and reporting happens in the TigerGate cloud.
System Requirements
eBPF Agent Requirements
- Linux kernel 4.15+ (5.7+ for LSM enforcement)
- 64-bit x86 or ARM architecture
- 50MB RAM, <3% CPU overhead
- Outbound HTTPS (port 443)
Supported Platforms
- Kubernetes (EKS, AKS, GKE, OpenShift)
- Docker & Docker Compose
- AWS ECS & Fargate
- Bare metal & VMs (systemd)