Pricing & Billing
Query Subscription Tiers
| Tier | Monthly | Queries | Included Agent Seats (per subscription) |
|---|---|---|---|
| Data Retention | Configurable duration that cloud-stored data (events, metrics, correlations, sessions) is kept before automatic purge. Free tier: 14 days. Paid add-on tiers extend to 90, 365, or 730 days; health and hardware metrics past 14 days are kept as 5-minute and 15-minute summaries (see Data Retention). Billed per managed agent per month. | ||
| BYOK | $0 | Unlimited (your key) | 0 |
| Professional | $39 | 1,000 | 20 per subscription |
| Business | $99 | 5,000 | 20 per subscription |
| Enterprise | $249 | 50,000 | 20 per subscription |
Agent Seat Pricing
| Count | Per Seat/Month | Notes |
|---|---|---|
| 0–99 | $5 | Standard rate — the 20 seats included with each query subscription are deducted from your bill (scales with the number of query subscriptions) |
| 100–999 | $4 | 20% discount |
| 1,000–9,999 | $3 | 40% discount |
| 10,000+ | $2 | 60% discount |
Annual billing: Save 15% on both query subscriptions and agent seats.
Included AI queries: Each purchased agent seat adds 100 AI queries per month to your organization's shared query pool. The 20 seats included with each query subscription do not add queries.
Subscription Management
Personal Subscriptions
- Upgrade: Immediate with prorated billing
- Downgrade: Takes effect at next billing cycle
- Cancel: Full access until period end; data retained 30 days
All billing via Stripe. Open the billing portal for each part of your plan from Team → Subscriptions, which provides Manage Agent Subscription, Manage Query Subscription, and Manage Data Retention Subscription buttons.
Team Subscriptions (Admin-Purchased)
Organization admins can purchase subscriptions for team members who don't have their own. This is useful for onboarding new staff or ensuring every team member has access to AI diagnostics.
- Purchase: Dashboard → Manage Team Subscriptions → click Buy Plan next to an unsubscribed member → choose tier → complete Stripe checkout
- Billing: Charged to the organization's Stripe customer account, managed by the admin who purchased it
- Cancel: Admins can cancel any admin-purchased subscription immediately with prorated billing. Self-purchased subscriptions can only be managed by the subscriber.
- Pooling: Each admin-purchased subscription contributes its tier's query quota and 20 included agent seats to the workspace agent pool, just like self-purchased subscriptions. Purchased agent seats add 100 AI queries each to the pool; included seats do not.
When a Subscription Ends
Agents need a seat to collect and upload events. When an organization no longer has any agent seats, for example because its subscription lapsed, its agents go through the steps below. Nothing is uninstalled from your hosts.
- Unlicensed. Within about six hours the agents are marked unlicensed. On its next heartbeat each agent stops uploading events, and a Windows agent also stops event collection. It keeps sending heartbeats.
- Events waiting on the agent. While the organization has no licence, the server does not accept event uploads and asks the agent to try again later. The agent keeps the events in its local buffer and sends them once the licence is active again. If the buffer fills, the Windows agent drops the oldest unsent events first.
- Deactivated. An agent that stays unlicensed for 30 days is deactivated. On its next heartbeat it goes dormant: a Windows agent stops event collection and a Linux agent stops uploading events. It keeps sending heartbeats.
- Reactivated. When seats are available again, within about six hours the agents deactivated this way are reactivated and given seats, oldest agent first, up to the number of seats. Each agent resumes on its next heartbeat with its existing enrollment. No reinstall or re-enrollment is needed, as long as the agent is still installed.
Agent versions earlier than 2.7.8.7 do not go dormant when deactivated. They keep running and the server does not accept their data.
AI Usage Observability
The Settings → AI Usage card shows per-workspace AI consumption over the last 30 days. Every AI call routed through ET Ducky — live sessions, multi-agent questions, smart reports, alert enrichment — is recorded here, regardless of whether it ran on a platform key or a BYOK key. For a full breakdown of what each metric means and how the cache figures work, see AI Usage & Quotas.
The card shows headline counts (tokens, requests, enrichments, result-cache and prompt-cache hit rates), a daily token sparkline, a usage-by-type table, and a channel reliability summary. There is no time-window selector; the window is always the trailing 30 days.
Bring Your Own Key (BYOK)
Workspaces can plug their own AI provider key into ET Ducky and bypass the platform’s query-pool model for AI cost. Cost moves from per query (ET Ducky’s plan tiers) to per token (your provider invoice). All other features — ET Ducky’s prompt engineering, smart-reports planner, behavioral allowlist, inflection RCA — keep working unchanged. For full setup details see Bring Your Own AI Key (BYOK).
Configuring
- Open Settings and find the AI Settings card.
- Choose a provider: Anthropic (Claude), OpenAI, or Azure OpenAI.
- Paste the key. For Azure, also enter the endpoint URL and a deployment name in the Model field.
- Optionally override the model (e.g.
claude-sonnet-4-6,gpt-4o-mini, your Azure deployment name). - Click Save. The settings are persisted and the key status updates to reflect whether it has been validated on the next AI call.
The key is encrypted at rest and never returned to the browser after save. The UI shows a Key saved badge when a key is on file, and the status line reports the last validation time or failure reason.
Fallback behaviour
If a BYOK call fails (provider outage, key revoked, quota exhausted) the router automatically falls back to the platform key for that single call so the operator’s session doesn’t die mid-question. The failure is noted in the AI Settings status line.
Quota interaction
- BYOK calls do not consume workspace queries. Your tier’s query pool stays untouched.
- Platform fallback calls do consume queries. If fallbacks accumulate, fix the BYOK config to avoid draining the platform pool unintentionally.
Only organization admins can edit AI Settings.