Billing, limits and retention

Upgrading and managing billingCopy Anchor Link

Only admins can see Admin Console > Billing. It shows:

• Your current plan and usage: active contributors this month and the number you are billed for, pipelines and runs this month.
• Each plan's price, monthly or yearly (yearly is cheaper per month). Enterprise is yearly only.
• Banners when a payment is past due, a trial is running, or the subscription will cancel at the end of the period.

To change plans:

• From Free: click Upgrade on a plan. Payment happens in Stripe Checkout.
• Already paying: each plan shows Upgrade or Downgrade, which opens the Stripe customer portal. Manage billing opens it too. There you can switch plans (prorated), update your payment method, see invoices and cancel at the end of the period.
• Enterprise: click Contact Sales. Enterprise is on a contract, so moving from Enterprise to another plan also goes through sales.

Active contributorsCopy Anchor Link

Team, Business and Enterprise are priced per active contributor. You pay for the people who change code or run pipelines, not for everyone who signs in.

• Who counts: anyone who opened or pushed to a pull request in a connected repository, or started a pipeline run Prodgator received, in a calendar month (UTC). A person on several providers counts once, matched by linked accounts, then by commit email, then by an admin merge. Bots never count.
• Who is free: viewers. Approvers are whoever a policy names, and approving a deployment or a pull request never makes someone a billed contributor.
• Admin Console > Contributors lists who counted in each of the last 13 months. Admins can exclude an account, merge two accounts into one person, and keep commit email addresses out of the count.
• Volume price: contributors after the first 100 cost less each. There is no cap on contributors on Team and Business.
• Enterprise is yearly only, with a minimum of 50 contributors.

How you are billed depends on the interval:

• Month to month: each bill covers the previous month's active contributors. You do nothing.
• Yearly: you commit to a number of contributors. If a month goes above it, the commitment is raised at the end of the quarter and the difference is prorated. It is never lowered during the term, and you can raise it yourself with Raise commitment in Admin Console > Billing, which shows the prorated charge before you confirm.

In Checkout, the contributor count starts at the number who counted last month, and Checkout also asks for:

• Your full name (required) and your business name (optional). They appear on your invoices.
• A promotion code, if you have one.

The text under the Subscribe button links to the Terms and Privacy Policy, and to support@prodgator.io for questions.

Inviting people never needs a payment step: members and viewers are unlimited on every plan.

When you reach a limitCopy Anchor Link

• Runs per month: at 80% your organization gets a notification. Once the limit is reached, new runs are not recorded until the next calendar month. Runs already recorded keep updating until they finish.
• Pipelines: runs of a workflow that has not run yet this month are not recorded once the limit is reached. Workflows already counted keep working.
• Active contributors on Free: the Free plan includes 5. Over that, nothing stops: gates and pipeline data keep working, admins see a banner and get an email, and the upgrade prompt stays until you pick a paid plan.
• Pull request gates on Free: one repository can have a pull request gate, with the basic rules. Other repositories keep their pipelines and runs but not a gate.
• API keys: you cannot create another key until you revoke one.
• Security report uploads: the next upload for the same pipeline run (or, outside a run, the same repository and commit) is refused with a message that names the limit. Other runs and commits are not affected. Uploads made outside a run also have an hourly safety limit per organization.
• AI credits: an AI action runs only when enough credits remain for its full price. Otherwise it is skipped with a message until the allowance resets on the 1st of the month (UTC), or until you add a credit pack (see AI credits and limits).

Data retentionCopy Anchor Link

Prodgator keeps runs, deployments, alerts and other history for your plan's retention window, then deletes it.

• Lists, filters and the time range on the Pipelines page stop at the window. A note says so when you reach the oldest run.
• DORA metrics and analytics periods longer than the window are shortened to it.
• The v1 API moves an earlier since forward to the window and sets meta.retention_clamped to true.
• If you move to a plan with a shorter window, older data is removed within a week.

The limits themselves are on Plans and features.