> ## Documentation Index > Fetch the complete documentation index at: https://docs.cubic.dev/llms.txt > Use this file to discover all available pages before exploring further. # Subscription > Free and paid cubic plans. Start with a 7-day free trial, with no credit card required. Everyone on your team is enabled by default during the trial. Choosing a paid plan at checkout starts billing immediately. After the trial, continue on the free plan or upgrade to a paid plan. ## Free plan The free plan includes 20 AI reviews per month, shared across repositories in your GitHub organization. The quota resets on the 1st of each month. Review comments show how many reviews remain. ## Paid subscriptions For paid AI review access, cubic's subscription cost is determined by the number of developer seats you choose to activate. Each active seat corresponds to a unique GitHub user within your organization. AI review usage on paid plans is measured in reviewed lines, with an allowance per paid seat that is pooled across your team. * **Seat-based billing:** You are billed based on the number of *active* seats you assign to your team members (GitHub users). * **Flexible seat management:** You can manage seat assignments at any time, both during your free trial and after it ends. * **Customizable checkout:** When you purchase a subscription, you select the exact number of seats you need. * **Ultrareview:** Paid and trial plans include Ultrareview for high-risk or complex PRs. Ultrareviews count toward your team's reviewed-lines allowance at 3× the standard rate. * **Subscription management:** Seat assignments and active seats can be viewed and managed through the subscription tab in your settings: [https://www.cubic.dev/settings?tab=subscription](https://www.cubic.dev/settings?tab=subscription) ### Seat scope across organizations Seat assignments are scoped to the selected GitHub organization. If your company uses cubic in multiple GitHub organizations, assigning a seat in one organization does not automatically assign that user a seat in another organization. The seat count shown in **Settings → Subscription** applies to the selected organization. For example, `86/155 seats assigned` means that organization has 86 active developer seats out of 155 available seats. Other linked organizations do not consume that organization's available seats. ### Usage and flex capacity See [AI review usage and limits](/account/ai-review-usage) for what counts toward your allowance. Other features, such as local reviews and coding agents, have separate limits. Enable [flex capacity](/account/flex-capacity) on a paid plan to buy extra reviewed lines when the included allowance runs out. An admin sets the monthly spend limit in **Settings → Subscription**. ### Assigning seats To manage seats as an admin, go to **Settings → Subscription**: * Toggle the switch next to a developer to assign or unassign a seat. * To update several developers, select their checkboxes and use **Update seat status**. Members and viewers cannot change seats. See [Roles and permissions](/account/roles-and-permissions) for the full permission list. To set a work email for the selected organization, open **Settings → Subscription & team** and click the pencil beside your email under **Team members**. Enter the address and press **Enter** to save. Weekly summaries, trial emails, and codebase scan completion emails use this address; your GitHub email stays the same. ### Automatic seat management Enable automatic seat management in your subscription settings to assign seats to new organization members and remove seats when members leave. These changes affect billing. Existing manual assignments remain. For example, if 3 of 10 developers have seats, enabling automatic assignment gives a seat to the next developer who joins, bringing the assigned total to 4. It does not assign the other existing members. ## Bot seat management cubic creates a separate bot row when a recognized bot, such as `devin-ai-integration[bot]`, first opens a PR. Bot reviews are disabled by default; an admin can enable them in subscription settings. Enabled bots do not require paid developer seats. Their reviews consume the team's shared reviewed-line allowance. ## Frequently asked questions Pro requires a seat for each active developer in the installation, including developers whose seat toggle is off. Active means opening at least 15 PRs in the last 30 days. Bots are excluded. This minimum applies because Pro's codebase scans cover the whole repository. Team does not have this activity-based minimum. No. Everyone is enabled during the trial so your team can try cubic. Before upgrading, go to **Settings → Subscription** and unassign users who do not need seats, individually or through **Update seat status**. Choose your paid seat count at checkout. Pro still requires enough seats to cover its active-developer minimum. Check that you're viewing the GitHub organization linked to your cubic integration in Vercel. A subscription linked to your personal GitHub installation does not automatically cover a separate organization. If the wrong installation is linked, contact [support](/account/support) with the organization name and your Vercel subscription details so we can help correct the connection. Yes. We offer an annual subscription at a 20% discount off the monthly rate. Select "12 months" on the checkout page, and the discount will apply automatically. You can enter your coupon or promo code on the subscription checkout screen: Screenshot showing the promo code field on the checkout page You can cancel your subscription at any time from **Settings → Subscription → Manage plan**. You'll keep full access until the end of your current billing period; after that you won't be billed again. To change your seat count after your subscription has started, go to [**Settings → Subscription**](https://www.cubic.dev/settings?tab=subscription) and click on **Manage plan**. This will direct you to our billing portal (Stripe) where you can adjust the number of seats. Prorated charges or credits will be applied based on your changes. We currently accept all major credit cards (Visa, MasterCard, American Express) and PayPal. For enterprise customers, we also support ACH bank transfers. Contact support to set them up. Nonprofits and schools can receive a 50% discount. Please [contact support](mailto:contact@cubic.dev?subject=Nonprofit%20Discount) to verify your eligibility. Yes. Public repositories on the free plan use a separate public fair-use allowance. On paid plans, reviews of public PRs from workspace members count toward the team's reviewed-line allowance; reviews from external contributors do not. See [public-repository usage](/account/ai-review-usage#faq) for details. Cancelling a subscription, disconnecting GitHub, and deleting your account are separate actions. See the [Support FAQ](/account/support#faq) for each one. For billing questions, [contact support](/account/support).