Free to run. Pay for history, export and forwarding.

One app token. A token groups the diagnostics of one web app on every hostname and route it runs on, so production and staging can share a token or have one each. Free covers 3 apps. Pro and Custom set no app limit; to stop abuse an account holds at most 200, and we raise that if you write to us.

Every event GenClass received for your apps, as it arrived: page sessions with versions, mode, device class, hostname and route (ids replaced), model loads, each decision with its diagnosis, confidence and action, detections, actions, undos and the periodic counts, plus when each batch arrived and a two-letter country. It covers events that arrived while the app was in your genclass.dev account, starting from the day paid plans opened, and reaches back 1 year (at most 90 days for the time before you upgraded). Download it from an app's dashboard as JSONL or CSV, or fetch it with GET /api/account/projects/<id>/events?from=&to= and a bearer token. It holds no page text: GenClass does not collect page text unless your app opts in to situation text, and then only the redacted text the model read. Typed passwords and payment fields, cookies, headers, request and response bodies, IP addresses and user agents are never collected, so they are never in an export.

When a paid plan ends, the account moves to Free: dashboards show the last 7 days, and forwarding and export stop. GenClass keeps every app's data for at least 90 days on any plan, so upgrading again brings those days back into view. Data older than 90 days is deleted 30 days after the paid period ends, so export what you want to keep before the plan ends, or upgrade again within those 30 days. Your apps, tokens and dashboard links keep working.

It is off until you turn it on for an app on its dashboard, on Pro or Custom. Then the genclass.dev collector sends that app's likely detections (not the ones marked possible) to the destinations you connect: Sentry, PostHog, Datadog, Slack, or a webhook whose requests are signed so you can check they came from GenClass. Each record has the diagnosis, confidence, page route, versions and a link to the dashboard, never page text. The same problem on the same page is sent at most once an hour, and an app sends at most 60 records an hour. Nothing is added to your app's code or bundle, data goes only to the tools you connect, and turning forwarding off, or the plan ending, stops it.

Reports on how people use your app's pages: clicks, dead clicks and rage clicks, how far they scroll, and the paths they take from page to page. It is being built now and is not in the runtime yet. Pro and Custom include it when it ships.

After you start Custom, a person from GenClass emails you within 1 business day. Together we pick the bugs that matter in your app, the data to train on (your app's events in GenClass and the bug reports you share with us) and when the model ships. We train a GenClass model on that data, measure its false reports on your app's normal traffic, and ship it as private model files your runtime loads with model.baseUrl.

Payments go through Stripe, which emails a receipt for each one; past receipts are under Manage billing on your account's billing page. Card details go to Stripe and never reach GenClass. For an invoice with your company's details, or a purchase order, email mehar@daybot.ca.

Refunds are by request: email mehar@daybot.ca from the address on your billing account. Cancelling stops the next charge, and the plan stays until the end of the month you paid for.

Not yet; both paid plans are monthly. If your company needs to pay for a year at once, email mehar@daybot.ca.