Read-only pilot · Explicitly reported metadata
Know where async work failed. Recover it safely.
Follow evidence from request to external effect—without sending customer payloads or putting Nestarc in your data path.
Recovery actions are not enabled.
Scroll to follow the execution →
- Request, Observed
- Database, Observed
- Outbox, Observed
- Queue, Observed
- Worker, Failed
- Webhook, Not observed
- External effect, Not observed
One operation.
Many places to lose the thread.
A successful request is not proof the work finished. A queued job is not proof the side effect happened.
Scroll to follow the execution →
- Request, Observed
- Database, Observed
- Outbox, Observed
- Queue, Observed
- Worker, Failed
- Webhook, Not observed
- External effect, Not observed
- Observed
- Open
- Stalled
- Failed
- Not observed
See the evidence.
Not the payload.
Correlate each stage with bounded, metadata-only evidence. Keep retries, stalls, and uncertainty visible instead of guessing.
The current pilot is read-only. Recovery controls are not enabled.
exec_7F2ALocal data plane.
Hosted control plane.
Your requests, transactions, jobs, webhooks, and side effects stay in your environment. Nestarc receives only a strict operational projection.
The agent is designed and fixture-tested to fail open. If Nestarc is unreachable, customer work continues while diagnostic evidence may be incomplete.
- Your applicationRuns customer work
- NestJS agentReports allowlisted metadata
- Nestarc control planeCorrelates read-only evidence
Built to know less.
Allowed
- Opaque identifiers
- Stage and status
- Timing and attempts
- Fixed error codes
- Connection health
Outside the contract
- Customer request/response bodies
- Customer headers and business secrets
- Webhook payloads
- Raw logs and stack traces
- SQL text and results
- Customer PII
Every v1 message is allowlisted, size-bounded, and default-deny.
Evidence before
certainty.
At-least-once queues do not become exactly-once because a dashboard exists. Nestarc preserves incomplete and conflicting evidence instead of manufacturing a replay-safe verdict.
- 01Deterministic
- 02Conservative
- 03Read-only first
Bring one hard async workflow.
Start with one persistent staging path and help shape the evidence required for safer recovery.
Recovery controls are not enabled.