Home
/
For your team
/
Engineering

For engineers: one tag, five install paths, no DNS change

No routing change, no CDN change, no build-step dependency, and fail-open by design so we can never take your checkout down.
Start for free
Talk to an expert

What does engineering get from script monitoring?

HTML, Next. No routing change, no CDN change, no build-step dependency, and fail-open by design so we can never take your checkout down. The rest of this page sets out what that means day to day.

Five ways in

HTML, Next.js, Vite, the CLI, or an AI-assisted setup. All of them produce the same first-party tag.

Fail-open, always

If our service is unreachable your page renders and your checkout completes. We are a monitoring dependency, never an availability dependency.

Nothing in the traffic path

No DNS change, no CDN change, and your site traffic is never routed through us. Deep script analysis happens on our infrastructure against scripts we fetch ourselves.

Scope as configuration

Selector rules define payment-page scope, which also defines what you are billed for. Diagnostics show which pages matched and which did not, so misconfiguration is visible rather than silent.
One first-party tag, added the way your stack already ships code. No DNS change and no CDN change, because your traffic is never routed anywhere.
Everything here is on every plan, including the free one.
Start for free
See pricing

Frequently asked questions

Read the FAQ
Minutes for the tag itself. Adding it through a tag manager needs no deploy at all. The longer part is deciding your payment-page selectors, which is a scoping conversation rather than an engineering one.
There is one, as with any tag, and it is designed to be small: the tag is lightweight, loads asynchronously, and the heavy analysis of each script happens off the page rather than in the visitor's browser.
Yes, and scope needs care. In an SPA the payment step may not be a distinct document load, so scope is defined by route and by the presence of the payment form rather than by a server-rendered URL.
Yes, with API keys managed in the console, covering the inventory, alerts and evidence. There is also hourly S3 CSV export if you would rather pull batches.
Yes, it will if your policy does not allow it, which is expected and correct. The quickstart covers the directives to add. If you are running a strict nonce-based policy, that is worth raising during setup.

Try it on your own payment pages.

Free forever on 1,000 page views a month, no credit card.

Free forever plan. No credit card.