Pricing & Billing
Query Subscription Tiers
| Tier | Monthly | Queries | Free Agents (per subscribed user) |
|---|---|---|---|
| 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. Billed per managed agent per month. | ||
| BYOK | $0 | Unlimited (your key) | 0 |
| Professional | $39 | 1,000 | 20 per subscribed user |
| Business | $99 | 5,000 | 20 per subscribed user |
| Enterprise | $249 | 50,000 | 20 per subscribed user |
Agent Seat Pricing
| Count | Per Seat/Month | Notes |
|---|---|---|
| First 20 per subscribed user | Free | Included with paid plans (scales with number of subscribed users) |
| 11–100 | $5 | Standard rate |
| 101–999 | $4 | 20% discount |
| 1K–9,999 | $3 | 40% discount |
| 10K+ | $2 | 60% discount |
Annual billing: Save 15% on both query subscriptions and agent seats.
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. Access your personal billing portal from Dashboard → Manage Query Subscription.
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 free agent seats to the organization pool, just like self-purchased subscriptions
AI Usage Observability
The Settings → AI Usage card shows per-workspace AI spend so admins can spot heavy consumers and trend the bill over time. Every AI call routed through ET Ducky — live sessions, multi-agent questions, smart reports, alert enrichment, inflection RCA — lands here, regardless of whether it ran on a platform key or a workspace BYOK key.
What you see
- Time window selector: Last 24 hours / 7 days / 30 days / This billing cycle.
- Total queries — calls successfully routed in the window.
- Total tokens — input + output combined, summed across all providers.
- Estimated cost — computed from provider list prices at the time of the call (your actual invoice from the provider may differ slightly).
- Top models — ranked by token spend so you can see whether Sonnet, Opus, Haiku, or a non-Anthropic provider drove the bill.
- Top consumers — users in the workspace by query count, for spotting power users or runaway scripts.
Usage data is captured at routing time, not on the provider invoice. Treat the cost column as an estimate; the authoritative number is whatever your provider bills (or, for platform keys, what ET Ducky bills via Stripe).
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.
Configuring
- Open Settings and find the AI Settings card.
- Choose a provider: Anthropic (Claude), OpenAI, Azure OpenAI, or others as supported.
- Paste the key. For Azure, also enter the endpoint URL.
- Optionally override the model (e.g.
claude-sonnet-4-6,gpt-4.1, your Azure deployment name). - Click Save. The router validates the key with a tiny test call before persisting.
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 logged in AI Usage with a fallback tag.
Quota interaction
- BYOK calls do not consume workspace queries. Your tier’s query pool stays untouched.
- Platform fallback calls do consume queries. If you see fallback entries piling up, fix the BYOK config — otherwise you’ll burn through the platform pool unintentionally.
Only organization admins can edit AI Settings. The key is encrypted at rest and never round-trips to the browser after save — the UI shows the last four characters only.