Your app, monitored on autopilot

Vigilon keeps watch around the clock and tells you, in plain words, when something starts failing, gets slower, or stops running, and what changed.

You’ll get product updates and a beta invite by email. Unsubscribe anytime.

Node.jsPythonOpenTelemetry

ServicesEndpointsJobs
  1. Watches

    Every service, endpoint, and background job, around the clock.

  2. Compares

    Each one against its own history. Nothing to configure, no thresholds to set.

  3. Flags

    What broke, where, and since when. The serious ones reach your inbox.

What you get

Everything that matters, out of the box.

Vigilon emails you when a new error appears or a fixed one comes back, counts how often each one happens, and lets you mark it resolved.

Under the hoodExceptions grouped into error groups with resolve, mute and regression tracking; email alerts for new and regressed groups.

Docs Node.jsPython

Automatic insights

Six things Vigilon checks without being asked.

Vigilon keeps monitoring your services, endpoints and jobs for anomalies, and reports them through insights. Every insight says what changed, where, and since when.

HTTP errors

Error rate spikes

Opens when a service starts failing at least twice as often as it usually does at this time.

Turns critical past 10% errors. Closes itself after 30 minutes back near normal.

Example insightpayments-api
CriticalError rate up on payments-api after deploy v2.3.2
01 / 06
Background jobs

Monitor scheduled jobs and queue workers.

Track jobs alongside your services.

  • Missed runs: Flag jobs that do not run on schedule.
  • Traces for every run: Open a failed run and inspect its trace.
  • History and duration: Compare failure rate and p50/p95 runtime by job.

Docs Node.jsPython

Works with your AI coding tool

Ask your coding agent why your app is failing.

Connect Vigilon to your coding agent. Ask what broke, and it reads the errors and traces straight from Vigilon, then proposes the fix.

Why did POST /webhooks/stripe start failing after today’s deploy?
vigilon · list_error_groups→ SignatureVerificationError · 87 times
vigilon · get_trace 8dc4a12f→ fails at webhook.ts:84

The failures all come from signature verification. Today’s deploy parses the request body before Stripe sees it, so the raw payload is gone. The change is in webhook.ts. Want me to patch it?

  1. 01

    Connect your agent

    One command adds Vigilon to your coding agent. You sign in with your Vigilon account, no API key to paste.claude mcp add --transport http vigilon https://mcp.vigilon.io/mcp
  2. 02

    Ask what’s wrong

    Ask why something is failing or slower than it was. The agent pulls the errors and traces itself.
  3. 03

    Let it fix it

    It finds the line, explains the cause, and proposes the change.
OpenTelemetry

Send standard OpenTelemetry data.

Point any OTLP exporter at Vigilon. Run it beside your current backend. Keep your existing instrumentation.

Docs Use an existing OpenTelemetry setup

checkout-apipayments-workerscheduling-serviceOTLPVigilonany OTLP backend
Time to first signal

It’s so easy to get started.

We recorded the flow from signup to live telemetry in one take, as proof.

Signup to first signal
  1. 01

    Signup

    Create your workspace and start your plan.

  2. 02

    Create a project and API key

    Name the project after your product, then generate an API key under its settings page.

  3. 03

    Run the installer in your AI agent

    Run `curl -fsSL https://vigilon.io/agents/install.md` and follow the instructions in that file to set up Vigilon in this project.
  4. 04

    Add your API key

    VIGILON_API_KEY=[YOUR_API_KEY]
First signalorders-api · GET /api/orders · 200 · 142 ms
Early access

Join the early-access waitlist.

We’re looking for users who can use the product and give us feedback. Everyone on the waitlist gets 2 months of access to Vigilon for free.

You’ll get product updates and a beta invite by email. Unsubscribe anytime.