Stop triaging your errors.
Get the cause instantly.

The platform for ops engineering management. Get notified when something’s down, click through the evidence, jump to the exact line to fix.

Why is checkout throwing 500s?

Invariancejust now

Checkout 500s started 88 min ago, right after deploy checkout@2026.5.118 (#1043). The batch-tax change returns undefined for unknown SKUs, so tax computes to NaN and crashes at tax.ts:45. ~12% of attempts are failing.

checkout error rate1.2% → 8.4%

deploy #1043tax.ts:45INC-204Sentry · 3.8k events

Ask Invariance anything…

Always on

Point it at your stack. Soma does the rest.

Soma watches your systems 24/7, monitoring for errors and letting you know the moment something goes wrong.

app · monitors

checkout · error rate1.2%

within the normal band · all systems healthy

What you get

The finding, the fix, the handoff.

When something breaks, Soma opens a finding with the full case attached, and a fix ready for your coding agent.

Find

A finding with the full case.

Not an alert that says something broke. A finding that says what broke, which deploy caused it, who owns it, and where in the code to look.

findings · checkout 500s

Findings3 open

Checkout 500s traced to unchecked tax-rate access

checkout opened by agent

3,812 errors→deploy 9f3c2ab→#1043

Fix in src/pricing/tax.ts:42

Duplicate payout transfers from naive retry

N+1 query inflating orders endpoint latency

Ship

A change, ready to ship.

The suspect line is identified and a guarded change is drafted, ready to hand to your coding agent. You review, you ship.

github · pull request

soma/checkout#1043 Ready to merge

Batch tax lookups in a single round-trip

leo/batch-taxmain

src/pricing/tax.ts:45+14−6

Guarded change drafted by the agent · 2 min ago

Track

Nothing falls through the cracks.

Every finding is tracked, assigned, and linked to its evidence. If it's not fixed, Soma knows.

app · findings

Findingstracked

Checkout 500s traced to unchecked tax-rate access

checkout· 6 evidence· Hardik

open

Duplicate payout transfers from naive retry

payments· 4 evidence· Mira

open

N+1 query inflating orders endpoint latency

checkout· 2 evidence· Sara

open

findings · checkout 500s

Findings3 open

Checkout 500s traced to unchecked tax-rate access

checkout opened by agent

3,812 errors→deploy 9f3c2ab→#1043

Fix in src/pricing/tax.ts:42

Duplicate payout transfers from naive retry

N+1 query inflating orders endpoint latency

Ask anything

Your company’s knowledge, answered with citations.

Ask in plain language. Soma answers from one grounded graph of your Slack, GitHub, Granola, Sentry, and more. Every claim cited to its source, nothing hallucinated.

Which deploy caused the latency spike?

invariance-api@2026.5.44 (#1038) — the LRU embedding cache change. p95 rose 38% right after it shipped.

DatadogGitHub · #1038

Who owns the payments service, and who's on call?

Mira Chen owns payments; Sara is on call this rotation.

CODEOWNERSPagerDuty

Is there a security risk in auth?

Yes — jwt.verify has no algorithms allowlist (verify.ts:18), an algorithm-confusion surface.

Linear · AUTH-58code

What did we decide about payout retries?

Retries must reuse the idempotency key (ADR in memory). The naive retry in #1041 was rolled back.

GranolaMemory · ADR-0007

From Invariance

Two products, one understanding of your systems.

Platform

Soma

The AI-native observability platform. Point it at your stack, and it watches every agent run, catches every failure, and hands your coding agent the exact line to fix.

Open platform

Open source

GPS

Repo memory for coding agents. Teach your agent how your repo works once; GPS brings that context back every time the code is touched. It’s also how Soma understands your codebase.

View on GitHub

Used by engineers at