Error grouping
The same root error arriving 500 times with different user ids and line numbers becomes a single record. Normalisation weighs the message, the exception type and the first five stack frames together.
500 events → 1 issue
on watch · data in Türkiye · KVKK compliant
Errorbird combines Sentry-style error grouping, Seq-compatible log management and uptime + SSL + domain monitoring. It is API-first: the data can live in your own panel too.
No credit card · 3 monitors and 5,000 events free
Unresolved: 5 · Resolved: 0 · Ignored: 0
NullReferenceException: Cart not found
OutOfMemoryException: report rendering
Payment provider responded slowly
Last 24 hours · 445 events
Database, queue and backups all in the TR region — written into the contract.
PII scrubbing on by default, a data processing agreement and an audit trail ready to show.
A fixed monthly price with invoices in TRY and e-invoice compatible numbering.
Reads .tr expiry dates that most foreign services simply cannot.
Right now
With Errorbird
Six modules, one data model. Everything is read from the same API.
The same root error arriving 500 times with different user ids and line numbers becomes a single record. Normalisation weighs the message, the exception type and the first five stack frames together.
500 events → 1 issue
CLEF and OTLP compatible ingest. On Serilog only the server URL and the key change — no code change.
INF Order created {OrderId}=48213
WRN Payment provider slow 2.4 s
ERR Cart not found {UserId}=***
HTTP, TCP port, certificate chain and domain expiry. An incident never opens without confirmation from at least two locations, so a single location fault raises no false alarm.
99.98%
2/2 locations confirmed
Email and Slack/Discord. Alerts fire when the threshold is met, so a one-off network blip stays silent — and recovery notices are automatic.
Everything the dashboard shows comes from the public API. Ready-made React components drop the issue list, uptime badge and SSL countdown into your own product.
GET /api/v1/projects/{id}/summary
{
"openIssues": 5,
"uptime24h": 99.98,
"sslDaysLeft": 61
}
Every end client is isolated in its own workspace. Brand colour and logo flow into the widgets automatically; your client never sees Errorbird.
Your agency
A secret and a publishable key pair are generated for you.
Change the Serilog sink URL or redirect your OTLP collector.
Enter a URL or a domain — no code change needed.
Log.Logger = new LoggerConfiguration()
.WriteTo.Seq(
serverUrl: "https://api.errorbird.com/api/v1/ingest",
apiKey: "ebrd_secret_…")
.CreateLogger();
Same sink. Only the address and the key change.
var summary = await errorbird.GetSummaryAsync(ct);
var issues = await errorbird.ListIssuesAsync(
new IssueListQuery(Limit: 10), ct);
return Results.Ok(new { summary, issues.Items });
Errorbird.Client (NuGet) and @errorbird/client (npm) read SDKs.
Anyone adding error tracking and uptime monitoring to their own project. One organisation, a few projects, minutes to set up.
For teams watching dozens of client sites and applications who want to present the data under their own brand. Isolation and white-label are there from day one.
Unpredictable usage-based billing was rejected on purpose. You know the bill at the start of the month.
Hobby
Personal / trial
TRY 0/ per month
Pro
Solo / small team
TRY 490/ per month
Business
Growing team
TRY 1,490/ per month
Agency
Agency / reseller
TRY 2,990/ per month
Enterprise
Enterprise
Quote based
Prices exclude VAT.
In Türkiye. Database, queue and backups all sit in the TR region — a written commitment in the data processing agreement, and one you can verify in the API response.
Scrubbing is on by default. Fields such as password and token are never stored, and national id, card, IBAN, phone and email patterns are masked before the event reaches the queue. You can add your own patterns.
No. On Serilog the Seq sink stays as it is; only the server URL and the API key change. With OpenTelemetry you point the collector at the OTLP endpoint.
An incident never opens without confirmation from at least two locations. A single location having network trouble marks the monitor degraded without alerting, and a probe failing on its own is never counted as your outage.
Yes — that is the product thesis. Everything the dashboard shows is read from the public API, and the browser-safe publishable key is limited to a domain allowlist.
No. When the quota is spent, ingest returns 429 and you are offered an upgrade. No surprise invoice is issued.
The free plan needs no credit card. Setup is creating a project and changing one log address.