Feature Flags
Control feature availability across your Aira deployment.
Overview
Aira uses feature flags to gradually roll out new features and let customers control what is enabled in their deployment.
- Cloud customers: features are enabled by the Aira team based on your plan
- Self-hosted customers: you control your own flags via environment variables or the dashboard
Checking your flags
curl -s https://your-domain/api/v1/feature-flags \
-H "Authorization: Bearer YOUR_API_KEY" | jq .flagsSelf-hosted: enabling features
Two ways to enable a feature:
1. Dashboard
Go to Settings > Feature Flags (admin only) and toggle the flag on.
2. Environment variable
Add ENABLE_{FLAG_NAME}=true to your .env file and restart:
# Example: enable Slack integration
echo "ENABLE_SLACK_INTEGRATION=true" >> /opt/aira/.env
docker rollout api # zero-downtime restart
docker compose restart worker # worker is non-HTTP, safeAvailable feature flags
| Flag | Default | Description | Status |
|---|---|---|---|
| compliance_reports | Enabled | EU AI Act, DORA, ISO 42001 compliance reports | GA |
| slack_integration | Disabled | Slack notifications for approval requests | Beta |
| teams_integration | Disabled | Microsoft Teams notifications via Incoming Webhook | Beta |
| github_code_governance | Disabled | GitHub PR code review governance with policy enforcement | Beta |
| github_auto_merge | Disabled | Auto-merge clean PRs after governance scan passes | Beta |
Beta features
Features marked as Beta are functional but may change. They are disabled by default. To opt in:
- Cloud: contact support@airaproof.com to enable for your organization
- Self-hosted: enable via environment variable or dashboard
Feature flags are cached for 5 minutes. After changing a flag, allow up to 5 minutes for the change to take effect, or restart the API service for immediate effect.
Disabling a GA feature flag may break existing workflows that depend on it. Only disable GA flags if you have a specific reason.