Documentation

Quick Start

Get TigerIdentity up and running in less than 15 minutes. This guide walks you through signing up, connecting your first identity source, and creating your first access policy.

Sign Up for TigerIdentity

Create your account and get instant access to the platform.

Visit the TigerIdentity dashboard
Create your organization
Get your API key and organization ID

Install the CLI

Install the TigerIdentity CLI to manage your configuration.

# Install via npm
npm install -g @tigeridentity/cli

# Or via Homebrew (macOS)
brew install tigeridentity/tap/tiger

# Verify installation
tiger --version

The CLI provides commands for policies, connectors, and more
Supports all major platforms: macOS, Linux, Windows
Auto-completion available for bash and zsh

Connect Your First Source

Connect TigerIdentity to your identity provider or infrastructure.

# Create a connector configuration file
cat > okta-connector.yaml <<EOF
version: v1
kind: Connector
metadata:
  name: okta-prod
  type: okta
spec:
  domain: your-domain.okta.com
  apiToken:
    secretRef: okta-api-token
  syncInterval: 5m
  resources:
    - users
    - groups
    - applications
EOF

# Deploy the connector
tiger connector create -f okta-connector.yaml

# Verify sync status
tiger connector status okta-prod

Supports 50+ identity sources out of the box
Real-time sync with configurable intervals
Automatic entity resolution and deduplication

Create Your First Policy

Define who can access what, when, and under which conditions.

# Create a policy file
cat > eng-db-access.yaml <<EOF
version: v1
kind: Policy
metadata:
  name: eng-db-access
  description: Engineers can access production DBs during business hours with MFA
spec:
  subjects:
    - type: group
      id: engineering
  resources:
    - type: database
      environment: production
  actions:
    - read
    - write
  conditions:
    - type: time
      businessHours: true
      timezone: America/Los_Angeles
    - type: mfa
      required: true
      maxAge: 1h
  effect: allow
  ttl: 8h
EOF

# Deploy the policy
tiger policy create -f eng-db-access.yaml

YAML-based policy language for readability
Support for complex conditions and context
Automatic policy validation before deployment

Verify Access Decisions

Test your policy and start enforcing access decisions.

# Simulate an access request
tiger policy simulate \
  --policy eng-db-access \
  --principal [email protected] \
  --resource db://prod-postgres \
  --action write

# Example output:
# ✓ Access ALLOWED
#   Policy: eng-db-access
#   Reason: All conditions satisfied
#   - MFA verified (1 minute ago)
#   - Time: Business hours (9:00 AM PST)
#   Session TTL: 8 hours

# Integrate with your application
curl -X POST https://api.tigeridentity.com/v1/decisions/evaluate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "principal": "[email protected]",
    "resource": "db://prod-postgres",
    "action": "write"
  }'

Test policies in simulation mode before enforcement
Sub-50ms decision latency at p95
Comprehensive audit logs for all decisions

Next Steps

Now that you have TigerIdentity running, explore these topics to deepen your understanding.

Core Concepts

Learn about principals, resources, policies, and the TigerIdentity architecture.

Advanced Policy Patterns

Explore more complex policy examples including time-based access, approval flows, and risk scoring.

Connector Reference

Browse all 50+ supported connectors for identity providers, cloud platforms, and SaaS applications.

API Reference

Integrate TigerIdentity decisions into your applications with our REST API and SDKs.

Ready to Get Started?

Start Free Trial Book a Demo