# Everock

Error tracking, runtime health, and evidence for your connected agent.

## Documentation

- [Everock documentation](/llms.mdx/docs/content.md): Connect your application, understand production, and give your agent the context to act.
- [How it works](/llms.mdx/docs/how-it-works/content.md): Follow telemetry from your application to its evidence, runtime health, and your connected agent.
- [Quickstart](/llms.mdx/docs/guides/quickstart/content.md): Connect a project, install one runtime, and verify your first real event.
- [Projects and components](/llms.mdx/docs/guides/projects/content.md): Connect multiple applications and repositories to one shared project.
- [CLI](/llms.mdx/docs/agents/cli/content.md): Authenticate once and let your existing coding agent configure the project.
- [MCP and agents](/llms.mdx/docs/agents/mcp/content.md): Give your coding agent evidence, progress reporting, and controlled project tools.
- [GitHub and repositories](/llms.mdx/docs/agents/github/content.md): Distinguish local checkout identity from an authorized GitHub connection.
- [Agent-managed settings](/llms.mdx/docs/agents/settings/content.md): Let your agent tune detection and alert thresholds without exposing notification credentials.
- [Browser SDK](/llms.mdx/docs/sdks/browser/content.md): Observe client errors, requests, performance, and user sessions in a JavaScript app.
- [Next.js](/llms.mdx/docs/sdks/nextjs/content.md): One install for error tracking across the browser, Server Components, route handlers, and server actions.
- [Vite](/llms.mdx/docs/sdks/vite/content.md): A plugin plus a one-line init() for any Vite app — React, Vue, Svelte, or Solid.
- [NestJS](/llms.mdx/docs/sdks/nestjs/content.md): Server error capture for your NestJS backend — observe and rethrow, so your own error handling runs untouched.
- [Node](/llms.mdx/docs/sdks/node/content.md): The framework-agnostic server SDK — errors, outbound services, and databases, detected below the framework.
- [Cloudflare and edge](/llms.mdx/docs/sdks/edge/content.md): Instrument a fetch-based worker and flush within its invocation lifetime.
- [Framework adapters](/llms.mdx/docs/sdks/frameworks/content.md): Preserve framework routes and errors while sending the same endpoint measurements.
- [Python](/llms.mdx/docs/sdks/python/content.md): FastAPI, Flask and Django telemetry through OpenTelemetry.
- [Errors and detection](/llms.mdx/docs/features/errors/content.md): Understand why an event becomes evidence, an anomaly, or an incident.
- [Requests and endpoints](/llms.mdx/docs/features/requests/content.md): Inspect real traffic and optionally add a separate availability check.
- [Performance](/llms.mdx/docs/features/performance/content.md): Read browser vitals, request latency, and their actual coverage.
- [Session replay](/llms.mdx/docs/features/session-replay/content.md): Record limited DOM context around an error, with masking and consent.
- [Privacy and consent](/llms.mdx/docs/features/privacy/content.md): Control what leaves the runtime before it reaches the collector.
- [Tracing and OpenTelemetry](/llms.mdx/docs/features/tracing/content.md): Correlate supported requests and export JavaScript spans into the same project.
- [Delivery and diagnostics](/llms.mdx/docs/features/reliability/content.md): Understand bounded queues, retries, persistence, sampling, and dropped events.
- [Environments and releases](/llms.mdx/docs/features/releases/content.md): Associate runtime evidence with the application version that produced it.
- [Webhooks](/llms.mdx/docs/features/webhooks/content.md): Mark an inbound webhook route and it becomes a monitored service with its own uptime line.
- [Source maps](/llms.mdx/docs/features/source-maps/content.md): Upload your source maps so production stack traces symbolicate back to the code you wrote.
- [Home and history](/llms.mdx/docs/platform/home/content.md): Read the project overview without confusing unknown data with healthy traffic.
- [Activity and findings](/llms.mdx/docs/platform/activity/content.md): Follow an investigation performed by your own agent.
- [System and services](/llms.mdx/docs/platform/system/content.md): Distinguish repository structure, observed dependencies, and active checks.
- [Codebase](/llms.mdx/docs/platform/codebase/content.md): Publish architecture context for each application without uploading its checkout.
- [Users and sessions](/llms.mdx/docs/platform/users-sessions/content.md): Connect captured failures with the people and journeys they affected.
- [Notifications and agent handoff](/llms.mdx/docs/platform/notifications/content.md): Know which delivery channels are implemented and what must run to receive them.
- [Usage and limits](/llms.mdx/docs/platform/usage/content.md): Understand protective ingestion limits before treating them as a bill.
- [Browser SDK settings](/llms.mdx/docs/platform/browser-settings/content.md): Change optional browser capture without mistaking a toggle for an installation.
- [Self-hosting](/llms.mdx/docs/operations/self-hosting/content.md): Run the repository stack and configure public infrastructure explicitly.
- [Troubleshooting](/llms.mdx/docs/operations/troubleshooting/content.md): Find the missing link between installation and received evidence.
- [SDK configuration](/llms.mdx/docs/reference/configuration/content.md): Use runtime-specific options instead of assuming every adapter captures the same things.
- [Keys and authentication](/llms.mdx/docs/reference/keys/content.md): Keep public ingestion, secret build uploads, and agent sessions separate.
- [Coverage and compatibility](/llms.mdx/docs/reference/compatibility/content.md): Choose the actual runtime entry and understand the boundaries of automatic detection.
- [API and data access](/llms.mdx/docs/reference/api/content.md): Understand the transport behind the dashboard, CLI, and MCP.
- [SDK API reference](/llms.mdx/docs/reference/sdk-api/content.md): Call the correct API for the browser, Node, or edge runtime.

Full documentation: /llms-full.txt