Third-Party Services
We use the following third-party services to operate Tero:| Service | Purpose | Data Processed | Location | Trust Center |
|---|---|---|---|---|
| Google Cloud Platform | Infrastructure hosting | Control plane data, backups | United States | GCP Trust Center |
| Anthropic | AI classification (default) | Telemetry samples (not persisted) | United States | Anthropic Trust Center |
| OpenAI | AI classification (configurable) | Telemetry samples (not persisted) | United States | OpenAI Trust Portal |
| WorkOS | Authentication (SSO) | User email, authentication tokens | United States | WorkOS Security |
| Stripe | Payment processing | Billing information, payment methods | United States | Stripe Security |
Self-Hosted Option
When you self-host the control plane, you control which third-party services are used: Required - None. Self-hosted control plane runs entirely in your infrastructure. Optional - You can configure Tero to use your own AI provider (AWS Bedrock, Azure OpenAI, etc.) with your API keys and data residency requirements. Not applicable - GCP, WorkOS, and Stripe are only used for Tero-hosted control plane.Data Flow
Tero-hosted control plane:- Your observability platform API (read-only) → Tero control plane (GCP)
- Telemetry samples → AI provider (Anthropic or OpenAI) → Classification results → Tero
- User authentication → WorkOS → Tero
- Billing events → Stripe → Tero
- Your observability platform API (read-only) → Your infrastructure
- Telemetry samples → Your AI provider (or none) → Your infrastructure
- No external services required