Skip to main content
Sigilix limits review volume to keep shared infrastructure stable. This page covers the window mechanics, burst behavior, and what happens at the limit.
Sigilix is in private beta. Rate limits are set per account during the beta rather than by a published Free/Pro/Max tier. The mechanics below (rolling window, coalescing, monitoring) are accurate; the exact number of reviews allowed for your account is provisioned when you’re onboarded. If you need more throughput, contact us.

​
The rolling window

Sigilix uses a rolling window keyed by GitHub installation. Your account is provisioned with a review allowance over that window during the private beta. The window is rolling, not fixed. At any moment, Sigilix counts how many reviews you’ve completed in the trailing window. As old reviews age out, fresh capacity is freed up. Usage windows reset on a 5-day cadence — not weekly.
Because Sigilix runs on cheap, reliable open and frontier models rather than a single expensive first-party API, included usage is far more generous than a comparable OpenAI- or Claude-based plan. See Models & Usage for the model roster, picking your own model, and the economics behind the larger windows.

​
What counts as a “review”

A review is one full pass of the specialist ensemble on a PR. That includes:
  • Initial review on pull_request.opened
  • Re-reviews on pull_request.synchronize (each push counts)
  • Reviews on pull_request.reopened and pull_request.ready_for_review
Mentions don’t count. Replying to @sigilix on a comment thread is a lighter pipeline that’s not subject to the rate limit.

​
Burst behavior

If your team pushes 20 commits to a single PR in 30 minutes, Sigilix sees 20 pull_request.synchronize events and tries to run 20 reviews. Without throttling, that would burn your entire budget on one PR. Sigilix coalesces synchronize events. When a synchronize event arrives, Sigilix waits ~30 seconds for additional pushes before starting the review. If more pushes arrive within that window, they’re collapsed into one review on the latest SHA. The earlier SHAs aren’t reviewed. This means: a rapid push-fix-push-fix sequence costs one review, not three.

​
Hitting the cap

When you hit your rate limit:
  1. Sigilix doesn’t review the PR
  2. A small comment is posted: “Rate limit reached. Next review available in ~42 minutes.”
  3. The review will run automatically once a slot frees up
Old reviews on prior SHAs of the same PR remain visible — they don’t disappear when you hit the cap.

​
Monitoring usage

​
Headers

Every Sigilix-posted review has a footer in its body that reports your current usage against the window: 
_Sigilix · 2 of 4 reviews used in the current window · resets in 38m_
Use this to gauge how close you are to the cap.

​
Webhook

For programmatic monitoring, a review.completed webhook is available. It includes: 
{
  "event": "review.completed",
  "pr": { "owner": "...", "repo": "...", "number": 42 },
  "rate_limit": {
    "window_hours": 5,
    "max_reviews": 10,
    "used": 6,
    "resets_at": "2026-05-05T03:42:00Z"
  }
}
See Webhooks for setup.

​
Hitting the limit regularly

If reviews queue during peak hours, or you’re hitting the cap multiple days per week, your account allowance may need raising. During the private beta, throughput is provisioned per account — contact us and we’ll adjust it.

sigilix.json

Full configuration schema.

Join the private beta

Pricing (per-seat + usage, BYO models) is handled per account during the beta.