Everock documentation
Connect your application, understand production, and give your agent the context to act.
Everock connects runtime errors, requests, sessions, services, and release context with your own coding agent. The SDK captures supported signals; the platform groups evidence; your agent investigates and works on the fix.
Every guide is also available as Markdown. The CLI and MCP use your authenticated project access; there is no separate internal repair-model subscription to configure.
Start with Everock
Create a project and verify a real runtime event.
How it worksFollow a signal from capture to investigation.
Projects and componentsConnect separate repos and runtimes to one product.
Your agent and MCPRead evidence and publish investigation progress.
Install your runtime
Choose the entry that actually runs your application. Hybrid apps usually need both a browser and a server installation.
npm install @everock/sdk@beta
import { init } from '@everock/sdk';
init({
publicKey: 'pk_YOUR_PROJECT_KEY',
endpoint: 'https://collector.example.com',
});
See the coverage matrix for browser, Node, Next.js, NestJS, Vite, edge, and native-mobile boundaries.
Explore the platform
Events, requests, performance, environments, and releases.
Activity and findingsEvidence, user impact, and your agent’s working state.
System and servicesObserved dependencies and optional availability checks.
Users and sessionsIdentify affected users and open eligible replays.
Operate responsibly
Configure privacy and consent, inspect delivery diagnostics, and read the current notification channels and usage limits. Self-hosted deployments have their own infrastructure and retention requirements.