You approved a policy. Now what? Tero enforces it. You choose where and how. Some options are immediate and automatic. Others delegate to your engineers.Documentation Index
Fetch the complete documentation index at: https://docs.usetero.com/llms.txt
Use this file to discover all available pages before exploring further.
Enforce at edge
Execute policies before data leaves your network. Drop, sample, transform, redact.
Enforce in provider
Configure exclusion filters and routing rules directly via API. No deployment required.
Open PRs
Fix instrumentation at the source. Tero opens the PR, your team reviews.
Create tickets
Assign work to engineers in Linear or GitHub Issues.
Notify
Alert teams in Slack or email.
Set SLOs
Quality targets for teams to meet. Track progress over time.
Which to use?
| Method | Resolution | Reversible | Best for |
|---|---|---|---|
| Enforce at edge | Immediate | Reversible | Most policy categories |
| Enforce in provider | Immediate | Reversible | No Edge deployed |
| Open PRs | Variable | Reversible | Code-level fixes |
| Create tickets | Variable | — | Human decisions needed |
| Notify | Variable | — | Awareness |
| Set SLOs | Ongoing | Reversible | Long-term tracking |