Exemplar Dev

Welcome to the Exemplar Dev documentation.

• Website: exemplar.dev 
• Console: console.exemplar.dev 

Platform overview

Exemplar is a unified developer platform that brings together uptime and synthetic monitoring, status pages, incidents, and on-call—plus a service catalog, agentic developer workflows, and AI copilots for Day 2 Ops. Day 2 Ops is the post-launch slice of the SDLC: run, observe, and safely change software already in production (for example restarts or rolls with guardrails and audit trails, time-bound access to logs or production, capacity changes, secret rotation, or patches outside a single large release).

Core areas include:

• Monitoring and incident management — Triage, collaborate, and resolve from alert through postmortem. Synthetic checks, uptime monitoring, heartbeats, SSL expiry, and visibility across your stack.
• Third-party monitors — Aggregate public vendor status and incident feeds in one place so you can see when major cloud and SaaS dependencies are degraded or down without tab-hopping.
• Status boards and pages — Live boards for components, active incidents, and subscriber-facing updates (for example email, Slack, SMS).
• On-call — Rotations, escalations, and paging aligned with your services and teams.

AI Copilot for Day 2 Ops surfaces the same ideas in the IDE: ask about incident status, vendor status, maintenance windows, who is on-call, and more. Product capabilities are also available as MCP (Model Context Protocol) tools in editors and AI clients such as Cursor and Claude, so dashboard actions can be invoked from your workflow.

On the roadmap, Exemplar is expanding automation (workflows, webhooks, Kubernetes-oriented catalog integration), deeper service catalog discovery, and governance and compliance for governed changes with policy checks and approvals—whether triggered from an agent, the console, a deploy, or a webhook.

For the latest product positioning and feature highlights, see exemplar.dev .

Blog

Editorial posts on reliability, platform engineering, and AI-assisted operations: exemplar.dev/blog .

• Developer autonomy and the work that repeats after ship  — Why post-launch change dominates; self-service Day 2 Ops with guardrails and audit history.
• Agents, context, and guardrails on a unified platform  — From code completion to production actions; Context Lake, catalog, governance, and AI Copilot / MCP.

Next steps

• SRE — Monitoring, incidents, status pages, vendor signals, and operational detail.