Questions, answered.

No. You build a Sensor visually — pick an event type, scope it to a watchlist, and choose where to send it. If your tool speaks webhooks, it already speaks Evinor.

Most teams have their first Sensor firing within ten minutes. Point a signed webhook at n8n, Zapier, or Make and start building right away.

Yes. Every Sensor can be backtested against real history — you'll see exactly how many matching events fired in the last 90 days before you commit. Backtesting is free and doesn't use credits.

Today we cover corporate events — acquisitions, funding rounds, layoffs, leadership changes, IPOs, partnerships, and product launches. The engine generalizes to new event types and entities over time.

A typed, versioned JSON envelope — a discriminated type, the extracted roles with the canonical entity each one resolved to, a confidence band, and a provenance list naming every outlet that corroborated it. It's plain, predictable JSON your automation never has to guess about. Field by field: the envelope reference.

"DBX", "the SF lakehouse firm", and "Databricks, Inc." all resolve to one stable entity your workflow can key on across every event — no fuzzy matching downstream.

Events carry a confidence band — HIGH, MEDIUM, or LOW — plus one provenance entry per corroborating outlet. Gate your workflow on the band, or require N outlets before it acts. The band is optional on the wire: we omit it rather than fabricate one when the underlying signals are missing, so read an absent band as unknown, not low.

Verified in minutes, not milliseconds — fast enough to act on, slow enough to be right. And there's no polling loop: you subscribe once and each event is pushed to you when it's verified.

Webhooks and Slack are live today. n8n, Zapier, and Make all work through the generic signed webhook. HubSpot and a native n8n node are coming soon.

No. Forty outlets covering the same acquisition collapse into one canonical event. Your automation runs exactly once — the event is the dedupe.

Yes. Every delivery carries a base64 HMAC-SHA256 signature in the X-Evinor-Signature header, so you can verify it came from Evinor before your workflow acts on it. It signs the envelope's canonical form — RFC-8785 JSON canonicalization, with sender.signature removed — not the raw request body, so don't HMAC the bytes you received. Each Sensor has its own signing secret, and you can rotate it anytime. Step-by-step: the verification recipe.

Deliveries retry automatically with backoff. You can inspect every attempt, its status, and latency in the trigger log.

A watchlist is a set of named entities — companies, people, products, and more — that you want to track. Scope a Sensor to a watchlist and it only fires for events involving those entities.

Yes. Add any entity by name. If it isn't already in our graph, we provision it and research it for you in the background — resolving it to a canonical entity and, for companies, gathering firmographics like headquarters, size, and key people.

Each entity shows a research status: Researching while we look it up, Tracked once we've resolved and enriched it, or Unknown if we couldn't find a confident match. Company enrichment runs for organizations; other entity types show as Tracked once resolved.

If automatic research can't find a confident match, the entity shows as Unknown. Remove and re-add it with a different name — or, for a company, its website URL — to help us resolve it.

Your watchlists are private to you by default. Evinor also publishes a few curated public lists anyone can use. On the free tier you can create up to three watchlists.

Credits are how Evinor meters usage. Each account gets an allowance that resets every period, and you spend credits only when your Sensors do real work.

Only a Sensor match uses credits — charged once per event, per Sensor. Building Sensors, backtesting them, and creating watchlists are all free.

The free tier includes 100 credits per period. Your balance resets to 100 at the start of each period — unused credits don't roll over.

Your Sensors keep matching and every match is recorded, but delivery pauses until your balance is topped up. Delivery resumes automatically on new matches once you have credits again — you won't silently lose the record of what matched.

Not through self-serve checkout yet. If you're hitting your limit, get in touch and we'll sort out more capacity.

Today Evinor runs on a free tier — 100 credits per period, up to five Sensors, and three watchlists. Paid plans with higher limits are on the way. Early design partners get concierge onboarding, so reach out and we'll scope something to your usage.

Yes. Evinor has a free tier — not a time-limited trial — so you can build Sensors, backtest them, and receive live events within your credit allowance at no cost.

No. There's nothing to cancel on the free tier, and your Sensors and watchlists stay saved. If paid plans arrive, they'll be month-to-month with no lock-in.