What did the product accept?
Attach the proof reference to the access or agent action event your pipelines already emit.
Logs show what ran. Proofs show what was allowed.
Your monitoring tools already show what happened. NEUS adds the decision that allowed it, including the check, status, limits, and expiration. Reviewers can open that record beside existing logs and answer a simple question: was this action allowed?
Put the approval record beside existing logs
Is approval still current?
Surface revoked or expired proofs that still appear in recent action streams.
What stays in security monitoring?
Full telemetry, metrics, and incident timelines stay in your observability stack. NEUS is the trust-decision object.
Analytics and observability in the NEUS productHow it works
Attach the decision, then review
- 1Record one protected decisionRequire a NEUS proof check on a high-value access or agent path.
- 2Emit the proof referenceInclude the proof id with the event your analytics pipeline already stores.
- 3Open review from either sideFrom the log jump to current proof status; from the proof jump to the incident timeline.
- 4Refuse stale approvalRefuse new actions when status changes; keep investigating with both systems.
Portable proof
Current
One check. Reusable everywhere it is accepted.
SubjectAcme Ops | Organization
CheckOrganization
ScopeAccess | Payout
StatusActive
Expires2026-12-01
Connected apps confirm status before access without the full source file.
Integration options
Use the path closest to your first protected decision.
- Hosted check
- Start without building a custom screen
- JavaScript
- Add the check to a product backend
- HTTP
- Check a proof from any service
- React
- Drop the flow into an existing interface
- Connect NEUS
- Bring checks into any chat, IDE, or job runtime
What stays true
Clear checks at the moment they matter.
- See what ran and what was approved
- Open one record instead of collecting screenshots
- Keep monitoring in your current tools
Useful next decisions
Observability questions
How proofs add approval context to existing logs.