Every feature

What ForgeOps does

9 deep dives, from how grouping actually works to what's gated behind the Business plan. Pick one below for the full detail.

Automatic grouping

Every exception is fingerprinted from its class, message, and backtrace, so the same bug reported a thousand times shows up as one issue, not a thousand.

Alerting

Slack, Microsoft Teams, email, SMS, a voice call, or a generic webhook for your own tooling, configured per project, per trigger.

Heartbeats

A cron job or recurring task that's supposed to run but silently stopped raises nothing, so nothing would otherwise tell you.

Dashboards

Any data source crossed with any of its own dimensions, filters, and display types, fully combinatorial, arranged on a drag-and-drop grid you rearrange freely.

SSO

Every organization brings its own identity provider, but linking an IdP login to an existing account still always has to be proven from the account's own side, never just asserted by the IdP.

Uptime monitoring

An active check against a real URL, on its own schedule, for the specific case where the app just isn't reachable at all -- not something an exception tracker alone can ever see.

Multi-tenant, role-based

organization_id lives on every tenant-owned table directly, and access is always resolved from your own membership -- an organization you don't belong to 404s, the same as one that doesn't exist at all.

Reports

New issues, total events, tickets filed, incident downtime, and an assignment breakdown, for any date range -- the exact same computation whether you're looking at it on demand or it's landing in your inbox on a schedule.

PII scrubbing

A likely-sensitive value never reaches the job queue in the first place, only the request that reported it -- key-name matches and shape-based pattern matching, combined, before anything is persisted.