Question 1

What counts as a committed event?

Accepted Answer

One committed event is one data point accepted into a monitor — a single metric value you stream in. Only points the monitor actually ingests are metered; rejected or malformed payloads are not billed. Your monthly total is the sum across every monitor.

Question 2

How does overage work on Pro?

Accepted Answer

Pro includes 5M committed events per month. Beyond that, you pay $20 per additional 1M — prorated to the million, not rounded up to a new plan. Set an optional monthly spend cap and we stop metering (and alerting on new data) once you hit it, so there are no surprise bills.

Question 3

What happens if I go over on the free tier?

Accepted Answer

The free tier includes 100k committed events per month on a single monitor. If you approach the cap we email you first; you can upgrade to Pro in a click or let ingestion pause until the next cycle. Nothing auto-charges — the free tier never needs a card.

Question 4

Do you charge per monitor or per seat?

Accepted Answer

Neither is the primary meter — you're billed on committed events, so a fleet of low-volume monitors stays cheap. Tiers do cap monitor count (1 on Free, up to 10 on Pro, unlimited on Team) and seats are unlimited on paid plans.

Question 5

Is the SDK open source? Can I run the engine myself?

Accepted Answer

The Python SDK is open source (MIT) — but it's a thin, typed client for our REST API, not the engine. The anytime-valid engine (the detectors, fleet-wide false-discovery control, and the backtest gate) runs in the ValidAnytime cloud: you stream your metric values in and read alarms back. There's no self-hosted engine today, so the cloud tiers are how you run it — and the free tier never needs a card.

Question 6

Can I switch tiers or cancel anytime?

Accepted Answer

Yes. Upgrade, downgrade, or cancel whenever — billing is monthly with no lock-in. Downgrades apply at the next cycle so you keep the volume you've already paid for.

Question 7

What do you actually store about my systems?

Accepted Answer

Only what the ingest API accepts: a numeric metric value, an optional numeric label, an optional timestamp, and your event id — plus each monitor's name and configuration, and the alarms it produces. There is no field for prompts, features, or user records, so that data cannot end up here even by accident; the API is served over HTTPS only.

Question 8

How long is my data retained?

Accepted Answer

Pro includes 90 days of event history — the window your charts and backtests read. We're pre-launch, so retention beyond that isn't a published rate-card line yet: if Team-scale compliance needs a specific window, tell us and it goes in your agreement rather than in fine print.

Question 9

Do you have SOC 2 or an SLA?

Accepted Answer

Not yet, and we'd rather say so than imply otherwise: there is no SOC 2 report or formal SLA today. Team plans come with priority support, and if you need uptime or support terms in writing, that's part of the design-partner conversation. The strongest security control we offer from day one is the data-minimal API above — we never hold data you didn't choose to send as a number.

Question 10

Is there annual pricing?

Accepted Answer

Billing is monthly at launch, with no lock-in in either direction. If your procurement process needs an annual invoice, ask — while we're this early, annual terms are negotiated per team rather than published as a rate card.

Question 11

Do you work with design partners?

Accepted Answer

Yes, actively. If you run a model fleet, an eval pipeline, or a KPI stream where false alarms are burning trust, we'll help wire up monitors, tune budgets against your history, and shape the roadmap with you. Email hello@validanytime.com with a sentence about your streams.

Rigor that starts free.

Open SDK

Free cloud

Pro

Team

What counts as an event?

What will it cost you?

Which tier is right for you?

How billing works

Stop guessing whether it broke.