- Loader
- fired
- Render
- confirmed
Verdict
Healthy
The widget loaded and it painted. You get volume and render p95, by domain and by version.
Observability for embeddable widgets
Your widget is live on 340 customer sites.How many is it broken on right now?
Vigie watches your widget from your customers' sites, not from yours. Which customer, which version, which page, since which hour — before the customer emails you.
A 1.8 KB gzip loader, loaded async. No URLs to enter: the inventory discovers itself.
Customer fleet
last hour window
- 331healthy
- 6broken
- 3never heard from
- app.northwind.exampleCSPv2.14.011:20
- shop.bluefig.exampleCSPv2.14.009:05
- portal.lumen-co.exampleDOMv2.13.402:41
The problem
A blocked widget cannot report its own failure.
Your code runs on somebody else's machine. A CSP tightened on a Tuesday evening, a blocking extension, a redesign that removes the container, a CMS that rewrites the script tag: the widget never starts. It throws no exception, because there is no code in memory to throw one. Your telemetry stays green. Your customer's page has a hole in it.
Your server logs
See nothing. The failure is in a browser, on a domain that is not yours.
Your error tracker
Sees nothing. No error was thrown: nothing executed.
Your support inbox
Sees everything, last. The ticket arrives days after the breakage, and sometimes never.
Absence is the signal. And absence cannot send itself.
The model
Two signals, three states, no guessing.
The beacon loads in two stages. The loader fires before your widget; the reporter confirms the render completed. The gap between the two carries all the information.
- Loader
- fired
- Render
- never arrived
Verdict
Broken
The loader started, the render never came. You know which customer, which version, which page, since which hour. This is the alert the product is bought for.
- Loader
- silence
- Render
- silence
Verdict
Never heard from
Either the page was not visited, or everything is blocked upstream. Vigie settles it with the domain's history — never on a single hourly window.
The inventory
You enter no URLs.
You probably cannot list the domains your widget runs on. Customers install it, move it to a subdomain, resell it white-label, leave it on a staging page. Vigie does not need the list: every execution declares it.
- 01
You serve the loader
From your own CDN, inside the snippet your customers already paste. 1.8 KB gzip, async, no dependencies.
- 02
Domains announce themselves
Every origin that executes your code shows up in the fleet, with its version, within minutes. Including the ones you had forgotten.
- 03
The baseline forms
After seven days of history per domain, silence becomes readable and alerting turns on.
The snippet your customers paste
<script src="https://cdn.your-company.example/vigie-loader.js"
data-vigie-key="pk_live_8f3c…"
data-vigie-version="2.14.0" async></script>Then, inside your widget, one line the moment it has painted: markRendered(). The reporter finds the loader in the page, adopts its counters, and exactly one request leaves per hour.
Widget in an iframe? The loader sits in the parent page and hands the customer origin to the reporter over a handshake: inside the frame, location is your own domain and the referrer cannot be trusted.
In the product
Six things the dashboard gives you.
Customer fleet
A wall of domains, ordered by sessions affected, not alphabetically.
Non-execution detection
The one signal no error tracker can produce, by construction.
Health per version
Which version runs where, and which one breaks on arrival.
Render p95 budget
95th-percentile render time, by domain and by version, by hour.
Alerts that name the customer
The alert names the affected customer. Not an aggregate error rate.
Silent ingest
The ingest API answers 204 to everyone and never confirms that a key exists.
What it is not
Vigie replaces none of the tools you already run.
It is not APM.
Vigie does not trace your backend, open spans or time your queries. Keep the tool that does.
It is not a site monitor.
A site monitor checks that one page responds, and it is bought by the owner of that page. Vigie is bought by you, the widget vendor, and watches hundreds of pages you do not control.
It is not a third-party script scanner.
Those tools protect a site from scripts like yours. Same buyer: the host site. None of them tells you how many of your customers your own widget fails to start on.
The honest comparison
You already have error telemetry. It is good.
Any serious vendor already runs Sentry or its equivalent, and we are not going to pretend otherwise. Here is exactly where the line falls.
| The question | An error tracker | Vigie |
|---|---|---|
| My widget just threw an exception | Yes, with the stack and breadcrumbs | Yes, but aggregated per customer domain |
| My widget never started on this site | Nothing. No code in memory, so no error | Broken state, customer named, start hour |
| How many of my customers am I broken on? | A global error rate, with no customer denominator | A list of domains, each with its history |
| Which customers have never been heard from? | Not a question it can represent | Settled by history, once the baseline exists |
Pricing
By the number of monitored customer domains.
Not by event volume. You know how many customers you have; nobody knows their event count in advance, and nobody enjoys a bill that tracks somebody else's traffic.
Watch
Up to 100 customer domains
199 €/ month
A first widget in production, a fleet you could still list by hand.
- 100 monitored customer domains
- All three states, per domain and per version
- 30 days of history
- Email alerts that name the customer
- 2 ingest keys
Fleet
Up to 500 customer domains
349 €/ month
The fleet outgrew what support can hold in its head, and versions now coexist.
- 500 monitored customer domains
- Everything in Watch
- 90 days of history
- Outbound webhooks and threshold alerts
- Side-by-side version comparison
- 10 ingest keys
Atlas
Up to 2,000 customer domains
499 €/ month
Several widgets, several white labels, a team that lives in the dashboard.
- 2,000 monitored customer domains
- Everything in Fleet
- 13 months of history
- Multiple widgets on one account
- Hourly window export
- Unlimited ingest keys
Excl. VAT, billed monthly, no commitment.
In every plan
- Self-discovering domain inventory
- 1.8 KB gzip loader served from your own CDN
- Anonymous ingest, always answering 204
- No cookies, no visitor identifiers
- Ingest key rotation and revocation
Beyond 2,000 domains
Write to us with your domain count and the versions you have in circulation. You get a price back, not a qualification form.
Email usQuestions
What people ask before they sign.
How heavy is the loader on my customer's page?
4.0 KB minified, 1.8 KB gzip, loaded async with no dependencies. The reporter, which lives inside your widget, is 6.5 KB gzip. Neither adds a blocking request: traffic leaves once an hour, aggregated.
What data leaves my customer's site?
The origin, the page path truncated to 120 characters with the query string stripped, your widget version, the hour rounded to the hour, and counters: loads, renders, errors, blocks, p95. No cookies, no visitor identifier, no page content, nothing a user typed.
What happens if my ingest key leaks?
The ingest API answers 204 to every request, valid or not, so it never confirms that a key exists. A stolen key lets somebody push noise into your account; it reads nothing at all. Keys are revoked and replaced from the dashboard.
When does my first alert arrive?
Not in the first week, and that is deliberate. It takes seven days of history per domain to tell "silent" from "not visited". During that period the dashboard shows the baseline being built, and a domain never heard from is never painted green.
My widget ships white-label. Does this work?
That is the normal case. Vigie groups by origin, not by customer name: you map origins onto your accounts afterwards. A widget served in an iframe works too, through the handshake between the parent page loader and the reporter.
Does this replace my error tracker?
No, and it is not meant to. Keep it for exceptions, stacks and breadcrumbs. Vigie answers a question that tool cannot ask: how many of my customers is my widget not running on at all.
What if my customers block the ingest domain?
Then the domain goes silent, and Vigie says so instead of painting it green. That is precisely why "never heard from" exists as a state separate from "healthy".
How many of your customers, right now?
Serve the loader in the snippet your customers already paste. The first domains appear within the hour; the baseline is ready in seven days.
No commitment. No qualification call.
- 331healthy
- 6broken
- 3never heard from