Refleks

Refleks documentation

Plans, quotas, and paid evaluation

Refleks uses separate account, site, message, and crawl-job limits. The pricing cards show the plan defaults; this page explains how those limits are enforced when real requests arrive.

Plan defaults

Values below are the current server-side defaults. Prices and taxes are shown separately on the pricing page and confirmed by Paddle at checkout.

PlanSites / accountPages / siteMessages / UTC monthRefresh jobs / UTC day
Free1501005
Starter12001,00010
Pro550010,00050
Business202,00050,000200

The Free plan is available without a card. There is no separate time-limited product trial in the current billing code: the paid evaluation is covered by the 14-day first-paid-purchase refund guarantee, subject to its one-time abuse protections.

Account and site allocation

Site and page limits are related, but they are not the same counter.

  • Sites: the account can create up to the plan’s site count. Site creation is checked atomically, so a request over the cap is rejected before a new site is created.
  • Pages: the crawler’s page target is per site. A Pro account can have up to 500 crawled pages on each entitled site, subject to its site allocation; it is not a single 500-page pool shared across five sites.
  • Dashboard totals: account usage may display an aggregate page allowance for orientation, but the crawl and page checks enforce the per-site limit.
  • Downgrades or cancellation: existing sites are not deleted by the plan check. Sites outside the current allocation remain stored but cannot be crawled, served by the widget, or used for chat until you upgrade or remove an earlier site. Allocation is based on the account’s ordered site list.

Message quota behavior

The monthly message cap is account-wide across all of your sites.

  • Visitor and dashboard chat messages for entitled sites count toward the same account-wide UTC-calendar-month total.
  • When that monthly total reaches the plan cap, new chat requests are rejected with a rate-limit response until the next UTC month. The rejected request is not saved as a new user message.
  • Visitor traffic also has per-visitor/per-IP hourly and short burst protections. Those are abuse controls, not additional monthly capacity.
  • Dashboard test chat has a separate limit of 20 user messages per site per 10 minutes, and successful tests still count toward the account-wide monthly cap.
Conditional

Deployment-wide AI safety controls

Provider and embedding budgets can also pause work for every plan when a deployment-wide cost, token, or maintenance control is reached. Those internal safeguards are separate from the plan quotas listed above and may return a temporary-unavailable response.

Refresh and re-crawl limits

A refresh means a new crawl job. It is not an automatic schedule in the current product.

  1. Each accepted refresh consumes one account-wide crawl job for the current UTC day. The default plan caps are Free 5, Starter 10, Pro 50, and Business 200.
  2. The same site has a five-minute cooldown after its most recent finished or failed job, and this cooldown applies to every plan. A crawl already queued or running also prevents another active job for that site.
  3. The Free plan has an additional rolling safety guard in the server (20 jobs in the last 24 hours by default, when enabled). The plan’s 5-per-UTC-day cap normally becomes the tighter limit. Paid plans skip this specific legacy guard but still use their plan cap and same-site cooldown.
  4. A request that fails validation, ownership, email verification, cooldown, or site allocation does not enqueue a job. If enqueueing itself fails after reservation, the server attempts to return that crawl reservation.

The Free daily crawl value can be adjusted by a deployment setting; paid plan values are the server defaults above. No public promise is made about a fixed completion time because crawl duration depends on the site, network, content, and active worker pressure.

What happens when a cap is reached

Supported

Site cap

New site creation is rejected with the current plan and used/limit values. Upgrade or delete an existing site.
Conditional

Crawl/page cap

A refresh is rejected at the daily job cap or cooldown; a crawl itself stops at pages-per-site and records skipped or diagnostic details when other rules apply.
Not supported

No silent overage

Refleks does not continue accepting chat or crawl work beyond the server-side quota, and it does not turn a cap into an automatic paid overage.

A cap response does not by itself delete indexed pages. A successful future crawl can replace the active snapshot; a failed or incomplete refresh leaves the previous active snapshot in place. See change detection and snapshot safety.

Paid evaluation and refunds

The paid plan can be evaluated with real usage, without the old page/message threshold.

  • For a customer’s first paid purchase, a full refund can be requested within 14 calendar days of that purchase. You may use the service during the evaluation; there is no 10-page or 10-message eligibility threshold.
  • The guarantee is intended as a one-time first-purchase protection. It does not apply repeatedly after a prior refund or to an account cycling through purchases and refunds.
  • Fraud, chargebacks, deliberate quota circumvention, materially abusive automation, or termination for a Terms violation may make the guarantee unavailable. Mandatory consumer rights are unaffected.
  • Cancellation stops the next renewal; it does not automatically prorate the current billing period. Refund requests are handled through the Refund Policy and Paddle, the merchant of record.

Compare localized totals on Pricing, or use quota troubleshooting when a request is unexpectedly blocked.