Skip to main content

Documentation Index

Fetch the complete documentation index at: https://radarhq.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

Three plans. Pricing is on the public Pricing page.

​
Plans

FreeTeamEnterprise
ClustersUp to 3Per-cluster pricingNegotiated
MembersUnlimitedUnlimitedUnlimited
SSO (SAML / OIDC)YesYesYes
Audit log retention7 days30 days365 days
MCP / PATsYesYesYes
MCP requests / dayFair-useFair-usePer contract
SupportCommunityEmailDedicated
Custom contractingNoNoYes
Self-hosted HubNoNoYes

​
Free tier

The Free tier covers most teams getting started:
  • 3 connected clusters.
  • All features that exist in OSS plus the Cloud control plane.
  • The same MCP / PAT / SSO surfaces as Team.
When you cross 3 connected clusters, you’ll see an upgrade prompt. Existing clusters keep working - no auto-disconnect - but new cluster create is gated until you either upgrade or remove a cluster.

​
Upgrading

Settings → Organization → Billing → Upgrade plan. We use Stripe Checkout. The first time you upgrade we lazy-create a Stripe Customer for your org and a subscription with one quantity per connected cluster. After checkout, your plan updates within a few seconds (Stripe webhook). After upgrade, the Manage billing button opens the Stripe Customer Portal where you can:
  • Update payment method.
  • Download invoices.
  • Change billing email.
  • Cancel.

​
How the per-cluster quantity tracks

When you connect a new cluster, we increment the subscription quantity. When you delete a cluster, we decrement. Stripe handles proration automatically - mid-cycle changes are billed at the next invoice. If a sync to Stripe fails (network blip), it retries on a backoff. The quantity always converges to the actual cluster count.

​
Past-due / payment failures

If a payment fails:
  • Stripe retries on its standard schedule (4 attempts over ~3 weeks).
  • The org’s status flips to past_due and a banner appears in the Billing page.
  • A billing.payment_failed event fires through Notifications and the in-app inbox.
  • All read functionality keeps working - we don’t cut access mid-incident.
If the subscription eventually goes to canceled due to non-payment, the org reverts to Free. You’ll lose access to clusters beyond the 3-cluster Free cap, but your data and members survive.

​
Invoices

Invoices live in the Stripe Customer Portal. Download as PDF. The “Bill to” line follows whatever address you set in Stripe. We don’t email invoices ourselves - Stripe does, to the billing email on the customer record. Update that in the Stripe portal under Account information.

​
MCP fair-use

The “fair-use” cap on MCP requests is intentionally vague: we’ll only contact you if we see a runaway pattern (~tens of thousands of calls/hour from one user). Routine AI usage is well below that.

​
Enterprise contracts

Enterprise opens up:
  • Annual prepay with PO support.
  • Custom SLA.
  • Self-hosted Hub (we deploy our control plane in your VPC; see the self-hosted page on the marketing site).
  • DPA, SOC 2 reports, custom MSAs.
  • Named slack channel + dedicated CSM.
Contact sales@skyhook.io or use the Talk to sales CTA in the Billing page.

​
Cancellation

Settings → Organization → Billing → Manage billing → Cancel (in Stripe). Cancellation takes effect at the end of the current billing period. Your org reverts to Free; data stays, clusters beyond 3 stop being usable.

​
See also