Plans, usage & your account

For org admins.

This guide covers the self-serve side of running a Hekkos org: your plan tier and what it unlocks, how usage is measured, what happens when you hit a limit, and how to export or delete your org’s data. For the operator side (configuring Stripe, flipping enforcement), see the SaaS go-live runbook.

Plans at a glance

The paid plan comes in repo-count bands — you pay for the number of repositories you keep governed, and the per-repo price falls as you scale up. Every paid band shares the same token/operation budgets; only the repository cap differs between them. The exact numbers and prices are set by your deployment’s operator; the launch defaults are shown here.

	Free	Starter	Growth	Scale	Enterprise
Repositories scanned	5	25	100	500	Unlimited
Price (monthly)	—	$99	$299	$799	Custom
Price (annual, ~2 months free)	—	$990	$2,990	$7,990	Custom
Monthly LLM-token budget	500K	5M	5M	5M	5M
Docs standardized / month	50	1,000	1,000	1,000	1,000
Questions answered / month	200	5,000	5,000	5,000	5,000
Chat retrieval	Keyword (full-text)	Semantic + AI answers	Semantic + AI answers	Semantic + AI answers	Semantic + AI answers

Enterprise is unlimited and sits above Scale — it isn’t a self-serve checkout option; it’s arranged with whoever operates your deployment and set on their side. Scale is a finite 500-repo band on purpose: past it you move to Enterprise rather than an unlimited flat price.

The current numbers for your org — your band, repo count against its cap, and prices — are always shown on the Usage & Billing page and the Plans comparison (pricing) table in the dashboard, which reflect the effective values, never a hardcoded marketing number.

What “usage” means

Hekkos meters two things a customer can reason about, plus one internal guardrail:

• Docs standardized — each time a suggestion PR standardizes a doc type for a repo, it’s one doc_standardized operation.
• Questions answered — each grounded chat / RAG (retrieval-augmented generation) answer is one question_answered operation.
• Token budget (internal guardrail) — the raw LLM tokens spent this month. You rarely think about it directly; it’s a cost cap that also stops runaway use.

All three reset monthly. The Usage & Billing page shows current-period gauges and a short history of prior months.

Chat retrieval by plan

Chat answers questions over your committed docs, and your plan sets the retrieval mode: Free matches by keyword and returns the matching passages; Team matches by meaning and writes a cited AI answer. Both are scoped to your org and respect per-document access restrictions identically — the full keyword-vs-semantic comparison lives in retrieval modes.

Hitting a limit

When an org reaches a plan limit, Hekkos tells you clearly instead of failing silently:

• In chat, an over-quota or over-budget question returns a typed prompt: admins see an Upgrade button; members see “ask an admin to upgrade.”
• On Home, an admin sees an inline banner when the org is at (or near) a limit.
• Approaching a limit (~80%), the Usage & Billing page nudges before you’re cut off.

Enforcement is a deployment setting (OPERATION_BILLING_ENABLED). When it’s off, usage is still recorded and displayed — you just aren’t cut off.

Effective tier & the past-due grace period

Your effective tier can differ from the raw plan for a short window:

• A past-due Team org (a failed payment, in Stripe dunning) keeps full Team functionality for a 7-day grace period, then degrades to Free-tier limits until payment recovers — paying the outstanding invoice restores Team automatically.
• A self-hosted deployment with no valid license is treated as Free regardless of plan.

The Usage & Billing page always shows the effective budget and limits — the figures actually enforced — not a stale column value.

Upgrading, downgrading & managing your subscription (SaaS)

From Usage & Billing (admin only):

1. Upgrade — starts a Stripe Checkout for the band you pick. If your deployment offers annual billing, the page defaults to annual (2 months free) with a toggle to switch to monthly; otherwise billing is monthly. You’ll be asked to accept the terms (a consent checkbox) before checkout opens on Stripe’s hosted page (with address/tax collection if the deployment enabled it). On success your org flips to the paid plan at that band, its token budget is raised, and repo discovery re-runs so any repos the Free cap skipped get scanned. If you cancel at checkout, no charge is made and nothing changes.
2. Manage subscription — opens the Stripe customer portal to update the card, download invoices, switch bands (up or down), or cancel. A cancellation returns the org to Free at period end.

Changing bands (up or down)

Band changes are self-serve, both directions, through the Stripe customer portal (Manage subscription). A switch is immediate and prorated by Stripe — moving Starter → Growth mid-cycle charges the prorated difference and raises your cap right away; moving Growth → Starter lowers it and credits the unused portion. Because the band you’re entitled to is always derived from the price you’re actually paying, the change takes effect as soon as Stripe confirms it:

• Moving up re-runs repo discovery so repositories your smaller cap had skipped get picked up under the larger one.
• Moving down applies the smaller cap through the freeze behavior below.

When a downgrade puts you over the new cap

If you downgrade to a band whose cap is below your current governed-repo count (say Growth/100 → Starter/25 while 40 repos are active), Hekkos never deletes anything. Instead it freezes the newest-over-cap repositories:

• The newest repos (by the date they were added) are frozen first, so your longest-standing, most-relied-on repos keep being governed.
• A frozen repo is paused, not removed — its docs, history, and scan data stay intact. It is skipped by scanning and drift, excluded from chat answers (so a paused repo can’t serve stale truth), and its Trust badge shows “paused” instead of a score.
• Usage & Billing shows an “N repos paused” count, and Home shows a banner, so you can see exactly how many are over the cap.
• Re-upgrade restores them — moving back up unfreezes repos oldest-first until you’re back under the new cap, exactly reversing the freeze. Nothing is lost by downgrading and later changing your mind.

Caution

The Upgrade / Manage buttons appear only when the deployment has Stripe configured — and a comped (operator-granted) org sees neither. A comped org’s plan and band are set by the operator and are not managed through Stripe, so it can’t self-upgrade or switch bands through checkout; ask whoever operates your deployment if that needs to change.

Exporting your data

Settings → Data & danger zone → Download my data (admin) returns a single org-scoped JSON bundle: your org profile, members, repos, doc standards & paths, selections, and open suggestions. It contains no secrets (no encrypted keys or credentials) and no other org’s data.

Deleting your organization

Settings → Data & danger zone → Delete organization (admin) permanently removes the org. To guard against accident it requires you to type the org’s exact name to confirm. On confirm, Hekkos:

1. Cancels the live Stripe subscription (if any), then
2. Enqueues a background purge of the org’s data.

Danger

Deleting an org is permanent — it cannot be undone. And if billing can’t be reached to cancel a live subscription, the delete is refused rather than leaving a subscription billing with no org behind it — contact support in that case.

Legal

Public legal pages are served at /legal/terms, /legal/privacy, and /legal/dpa. Until your deployment’s operator has had counsel review and approve them, they show a “template — have counsel review” banner. Checkout includes a consent step, and a dismissible cookie notice appears on first visit.

---

Related: chat & retrieval modes · getting started · operator: SaaS go-live runbook