Self-Hosted Licensing
Coming soon: how licensing will work for self-hosted Abrova Trace — a free tier with no licence key, and a licence key from Abrova for larger installations.
Self-hosted Abrova Trace is not available yet, and licence prices are not set. This page describes how licensing will work. To talk about a licence for your company, contact us.
Licensing#
Self-hosted will work immediately with a free tier. A licence key from Abrova raises the limits and turns on the larger features.
Just run the Docker containers and start tracking errors. No sign-up, no licence key, no payment.
What a licence changes#
| Feature | Free tier | With a licence |
|---|---|---|
| Projects | 1 | More, set by your licence |
| New issues / month | 50 | More, set by your licence |
| Team members | 2 | More, set by your licence |
| Error tracking & Logs | Yes | Yes |
| APM & Web Vitals | No | Yes |
| Source maps / dSYM | No | Yes |
| Custom alert rules | 1 | More, set by your licence |
| Cron monitors | 1 | More, set by your licence |
| Integrations | More channels | |
| Spike detection | No | Yes |
Licences are paid in Toman. For prices and a licence for your company, contact us.
What Happens When a Limit Is Reached#
"New issues / month" in the table above means new issues per month. An error is counted the first time it is seen, when it creates a new issue. Further events of an issue that already exists are not counted.
When the monthly limit is reached:
- New issues are not stored until the limit resets at the start of the next month.
- Events of issues that already exist keep updating them — counts and last-seen times stay current.
- Your apps are never disturbed. The API still answers success (
200), with a body that says the event was not stored, so no SDK retries, queues or logs an error:
{
"status": "dropped",
"code": "plan_limit_reached",
"metric": "errors_monthly",
"limit": 50,
"used": 50,
"resets_at": "2026-11-01T00:00:00.000Z"
}(limit and used are example values; they reflect your licence.)
Performance monitoring needs a licence that includes it. Without it, spans and Web Vitals sent by your apps are answered the same way (200, "status": "dropped", "code": "feature_not_in_plan") and are not stored.
The project, alert rule and cron monitor limits apply when you create one: creating beyond the limit is refused.
How to Activate a Licence#
- Contact us to get a licence key for your company
- Open your self-hosted Console → Dashboard → License
- Paste the key and click Activate
How Licensing Works#
- The licence key is tied to your account, not to a specific server
- Your server validates the licence every 24 hours
- If your server can't reach Abrova, it uses the limits it has cached (7-day grace period)
- When a licence ends, you have 7 days before the server goes back to the free tier
- Going back is graceful — existing data is preserved, limits reduced
What Happens When a Licence Ends#
- Projects beyond the free limit become read-only (newest kept active)
- Members beyond the limit can still log in but can't be added to projects
- Licensed features (APM, source maps) stop working — performance data sent by your apps is no longer stored
- All existing data is preserved — nothing is deleted
- Activating a licence again instantly restores all features