Codeac ↔ GitHub: Can Inactive Repositories Pause Billing?

Question

Goal
Determine a cost‑control strategy for a minimal‑traffic project that uses Codeac’s GitHub integration, while keeping the service active for occasional review requests.
Constraints
Codeac’s free tier allows one active repository and 1,000 review comments per month. Beyond that, each repository and each comment incur fees, and unused comment capacity does not roll over. The public documentation does not mention a method to suspend or pause billing for repositories that become inactive; billing appears to continue until the repository is deleted.
Uncertainty
It is unclear whether an inactive repository can be temporarily disabled or if the billing cycle will still accrue charges until the repository is removed. The integration uses OAuth and webhooks, but no explicit “pause” feature is documented.
Questions

Does Codeac automatically stop billing a repository that has no active pull requests or review activity?
Is there an API or dashboard option to suspend or pause billing for a repository without deleting it?
If no such option exists, what is the recommended workflow to avoid charges while keeping the integration available?

Tasadduq Burney · Answer

Direct Answer
Codeac does not automatically stop billing for inactive repositories, and there is no dashboard or API option to pause billing without disconnecting the repository. As long as a repository remains connected via OAuth and webhooks, it counts toward your active-repository quota and incurs the per-repository fee regardless of pull-request activity.

How the Billing Model Works

Per-connected-repo pricing: Each linked GitHub repository is treated as an active seat. The free tier includes one repository; additional repositories add a recurring charge.
No activity-based suspension: Zero pull requests, zero review comments, or months of inactivity do not trigger an automatic billing pause.
No "pause" toggle: The standard Codeac dashboard (as of the current public product) lacks a suspend/pause button. The only documented way to stop the per-repo charge is to disconnect the repository from the Codeac integration.

Recommended Workflow to Avoid Charges While Keeping the Option to Re-enable

Disconnect the repository from the Codeac dashboard (Repositories → select repo → Disconnect/Remove). This immediately removes it from your active-repo count and stops the recurring fee.
Keep the GitHub repository intact. Disconnecting only severs the Codeac integration; your code, history, and GitHub settings remain untouched.
When you need reviews again, reconnect. Re-add the repository through the Codeac "Add Repository" flow. This re-establishes webhooks and OAuth permissions. Note that reconnection may trigger a batch of review comments on any open pull requests, consuming comment quota.

Caveats to Verify on Your Plan

Some higher-tier plans may retain custom rule sets or configuration after disconnection; others reset to defaults on reconnect. Check your plan details or test with a non-critical repo first.
If you have many open PRs at reconnection time, expect a surge of review comments that could exceed the monthly 1,000-comment free allowance.

One Diagnostic Detail Needed
Does your Codeac dashboard show a "Pause" or "Suspend" toggle next to individual repositories in the Repositories list? If yes, the workflow changes—use that toggle instead of disconnecting. If no, proceed with the disconnect/reconnect cycle above.

Codeac ↔ GitHub: Can Inactive Repositories Pause Billing?

Goal

Constraints

Uncertainty

Questions

1 answer

Direct Answer

How the Billing Model Works

Recommended Workflow to Avoid Charges While Keeping the Option to Re-enable

Caveats to Verify on Your Plan

One Diagnostic Detail Needed

Your perspective belongs here.

0 question comments