You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/accounts-billing/plan-pricing.md
+48-73Lines changed: 48 additions & 73 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -409,74 +409,37 @@ If you only had 2 projects total and delete one, you’ll be able to create a ne
409
409
</p>
410
410
</details>
411
411
412
-
### Individual Users (former Standard/Pro)
412
+
### Teams (Growth/Business)
413
413
414
414
<details>
415
415
<summary>
416
-
I’m on Standard – what’s changing with the new Individual plan?
416
+
What happens to projects with multiple collaborators?
417
417
</summary>
418
418
<p>
419
-
The new Individual plan priced at $39/month is a $9 increase from your current Standard plan but it delivers significantly more value and power for solo developers.
420
-
</p>
421
-
<p>
422
-
This change is based on feedback we’ve heard consistently: the previous Standard plan didn’t give individual users enough capability to build and ship full-featured apps on their own.
423
-
</p>
424
-
<p>
425
-
You’ll now get access to:
419
+
Starting September 4, 2025, all project collaboration must occur within a team (Growth or Business). This means:
426
420
</p>
427
421
<ul>
428
-
<li>Unlimited API endpoints</li>
429
-
<li>One-click app store deployment</li>
430
-
<li>Ability to publish libraries</li>
431
-
<li>One free custom domain</li>
422
+
<li><strong>Team projects.</strong> Everyone on your team keeps full edit access. Any project collaborator who is not a paid seat on your team will be switched to view-only access at the project level until they’re added as a paid team member.</li>
423
+
<li><strong>Projects not associated with a team.</strong> The project owner keeps full edit access and all other project collaborators become view-only members on that project. To keep editing together, move the project into a team and invite those collaborators as team members.</li>
424
+
<li><strong>Solo projects:</strong> If you are the only editor, nothing changes. You retain full edit access.</li>
432
425
</ul>
433
-
</details>
434
-
435
-
<details>
436
-
<summary>
437
-
I’m on Pro – what’s changing with the new Individual plan?
438
-
</summary>
439
-
<p>
440
-
The new Individual plan will cost less ($39 instead of $70) and still includes all the core solo-development features you had: unlimited projects, unlimited API endpoints, code/APK download, push notifications, payments/ads integrations, etc.
441
-
</p>
442
426
<p>
443
-
However, some advanced collaboration and localization features that were part of Pro are moving to higher tiers. Specifically:
427
+
If you plan to continue collaborating with users outside your organization, we recommend purchasing separate team plans per organization to maintain separation between projects and collaborators.
444
428
</p>
445
429
<ul>
446
-
<li>GitHub integration</li>
447
-
<li>One-click localization</li>
448
-
<li>Team commenting</li>
449
-
<li>Unlimited automated tests</li>
450
-
<li>Snapshot backups</li>
451
-
<li>Multiple development environments</li>
430
+
<li>If you are developing for multiple clients, consider <ahref="https://contra.com/opportunity/rWlmk2Yv-become-a-flutter-flow-agency">applying</a> to become a FlutterFlow Expert Agency if you haven’t already. Approved agencies may qualify for the Agencies Expansion add-on on the Business plan, which allows continued project-based collaboration with paid external users outside of your team.</li>
452
431
</ul>
453
432
<p>
454
-
These will no longer be included on Individual. If you rely on these for your workflow, consider the Growth plan (which supports two collaborators and includes GitHub integration, localization, etc.).
455
-
</p>
456
-
<p>
457
-
The good news is that if you don’t need those team-oriented tools, the Individual plan gives you the same power to build and deploy apps – at nearly half the price of Pro. We want to make sure you’re on the plan that fits your needs best.
433
+
Note: If you choose to migrate to a new paid plan before September 4, 2025, any collaborators not on your team will immediately move to view-only access at the time of conversion.
458
434
</p>
459
435
</details>
460
436
461
-
### Teams (Growth/Business)
462
-
463
437
<details>
464
438
<summary>
465
-
What happens to projects with multiple collaborators?
439
+
I’m currently on a Teams plan and want to change the number of users. Can I still do this on or after August 4, 2025?
466
440
</summary>
467
441
<p>
468
-
Starting August 20, 2025, all project collaboration must occur within a team (Growth or Business). This means:
469
-
</p>
470
-
<ul>
471
-
<li><strong>Team projects:</strong> Everyone on your team keeps full edit access. Any project collaborator not on your team switches to view-only until they’re added as a paid team member.</li>
472
-
<li><strong>Projects not associated with a team:</strong> The project owner keeps full edit access and all other project collaborators become view-only members on that project. To keep editing together, move the project into a team and invite those collaborators as team members.</li>
473
-
<li><strong>Solo projects:</strong> If you are the only editor, nothing changes. You retain full edit access.</li>
474
-
</ul>
475
-
<p>
476
-
If you plan to continue collaborating with users outside your organization, we recommend purchasing separate team plans per organization to maintain separation between projects and collaborators.
477
-
</p>
478
-
<p>
479
-
Note: If you choose to migrate to a new paid plan before August 20, 2025, any collaborators not on your team will immediately move to view-only access at the time of conversion.
442
+
No. As a part of the existing Teams plan retirement, team size will be locked on August 4, 2025. To adjust your team size after that date, please transition to one of the new plans (Growth or Business).
480
443
</p>
481
444
</details>
482
445
@@ -485,17 +448,17 @@ Note: If you choose to migrate to a new paid plan before August 20, 2025, any co
485
448
I am currently on a Teams plan with 6+ users and do not want to migrate to the Enterprise plan – how do I stay on the Business tier and how will I be charged?
486
449
</summary>
487
450
<p>
488
-
Teams with more than 5 users who do not wish to move yet to an Enterprise contract will be priced based on bundles of 5 seats under the Business tier based on the number of users in their Team as of August 20, 2025. For example:
451
+
Teams with more than 5 users who do not wish to move yet to an Enterprise contract will be priced in bundles of 5 seats under the Business tier, based on the number of users in their team as of September 4, 2025 and billed on a monthly basis. For example:
489
452
</p>
490
453
<ul>
491
-
<li>A team with 6–10 users will be charged $500 × 2 = $1,000/month</li>
492
-
<li>A team with 11–15 users will be charged $500 × 3 = $1,500/month</li>
454
+
<li>A team with 6-10 users will be charged $495 x 2 = $990/month</li>
455
+
<li>A team with 11-15 users will be charged $495 x 3 = $1,485/month</li>
493
456
</ul>
494
457
<p>
495
-
This option allows larger retail teams to continue operating under the Business feature set without immediate contract negotiation but will be available only to existing 6+ seat teams for 12 months to ensure continuity without immediate contract negotiation.
458
+
This option allows larger retail teams to continue operating under the Business feature set without immediate contract negotiation but will be available only to existing 6+ seat teams for 12 months from September 4, 2025 through September 4, 2026 to ensure continuity without immediate contract negotiation.
496
459
</p>
497
460
<p>
498
-
Note: Your seat count will be locked based on your team size as of August 20, 2025. You may reduce seats later, but will not be able to add more or expand beyond the feature set and usage limits of the current Business tier (except for any run-time features already in use that are grandfathered).
461
+
Note: Your seat count will be locked based on your team size as of September 4, 2025. You may reduce seats later, but will not be able to add more or expand beyond the feature set and usage limits of the current Business tier (except for any run-time features already in use that are grandfathered).
499
462
</p>
500
463
<p>
501
464
However, if you would like to maintain a single account, collaboration across all of your team members, enterprise level features and support, please reach out to <ahref="mailto:[email protected]">[email protected]</a>.
@@ -507,23 +470,25 @@ However, if you would like to maintain a single account, collaboration across al
507
470
Can I belong to multiple teams? How will that be billed?
508
471
</summary>
509
472
<p>
510
-
Yes, users can now belong to multiple teams in FlutterFlow – this is a new capability as part of our updated team and collaboration structure. Each team is treated as a separate billing entity, with its own plan, users, and usage limits.
473
+
Yes, users will be able to belong to multiple teams in FlutterFlow in the new plans – this is a new capability as part of our updated team and collaboration structure. Each team is treated as a separate billing entity, with its own plan, users, and usage limits.
511
474
</p>
512
475
<p>
513
476
If you are added as an editor on more than one team, you will count toward the seat total on each of those teams, and each team will manage your seat and billing as part of their own subscription. You will not be billed individually – all billing remains centralized at the team level.
514
477
</p>
515
-
478
+
<p>
479
+
Note: you can also be added as a view-only collaborator on projects that are a part of different teams. View-only collaborators do not count toward any seat limits or billing.
480
+
</p>
516
481
</details>
517
482
518
483
<details>
519
484
<summary>
520
485
Can I share projects across multiple teams?
521
486
</summary>
522
487
<p>
523
-
No, projects cannot be shared across multiple teams. Each project belongs to a single team, and access is managed within that team’s structure.
488
+
No, projects cannot be shared across multiple teams. Each project belongs to at most one team, and access is managed within that team’s structure.
524
489
</p>
525
490
<p>
526
-
If you want someone from another team to collaborate on a project, they must be invited into your team and assigned a role (e.g., editor or viewer). They will then count toward your team’s seat usage and billing.
491
+
If you want someone from another team to collaborate on a project, they must be invited into your team as an editor. They will then count toward your team’s seat usage and billing.
527
492
</p>
528
493
<p>
529
494
This approach ensures consistent permissions, secure collaboration, and clean billing across organizations.
@@ -535,10 +500,10 @@ This approach ensures consistent permissions, secure collaboration, and clean bi
535
500
What if I want to continue collaborating with project collaborators who are not on a Teams plan with me?
536
501
</summary>
537
502
<p>
538
-
With the new pricing model, collaboration is only supported within shared Teams plans. This means that to work together on a project, all collaborators must be part of the same Growth, Business, or Enterprise team.
503
+
With the new pricing model, collaboration is only supported within shared Teams plans. This means that to work together on a project, all collaborators must be part of the same Growth, Business, or Enterprise team. However, users can now be members of multiple teams at the same time, which allows you to create separate teams for different projects, depending on who you need to collaborate with.
539
504
</p>
540
505
<p>
541
-
However, users can now be members of multiple teams at the same time, which allows you to create separate teams for different projects, depending on who you need to collaborate with.
506
+
Project-level collaboration (where individuals outside your team could be added to specific projects) is being phased out to simplify permissions, ensure security, and support shared billing.
542
507
</p>
543
508
<p>
544
509
Project-level collaboration (where individuals outside your team could be added to specific projects) is being phased out to simplify permissions, ensure security, and support shared billing.
@@ -558,7 +523,7 @@ This change ensures that every project has clear ownership, consistent permissio
558
523
I build apps for clients (agency/freelancer). What plan should I choose?
559
524
</summary>
560
525
<p>
561
-
We now offer multiple plan options to support agencies of all sizes – whether you’re a solo freelancer, a fast-growing studio, or an established consultancy. We believe the best path depends on your team size and how you prefer to work with your clients:
526
+
We will now offer multiple plan options to support agencies of all sizes – whether you’re a solo freelancer, a fast-growing studio, or an established consultancy. We believe the best path depends on your team size and how you prefer to work with your clients:
562
527
</p>
563
528
<ul>
564
529
<li>
@@ -573,27 +538,37 @@ We now offer multiple plan options to support agencies of all sizes – whether
573
538
<strong>Agencies with more than 5 developers:</strong>
574
539
<ul>
575
540
<li>
576
-
If your client plans to manage the code, we recommend encouraging your client to purchase their own Enterprise plan and inviting your agency developers as Team members on the plan. To learn more about our Enterprise offering, they can reach out to
<li>We recommend encouraging your client to purchase their own Enterprise plan and inviting your agency developers as Team members on the plan. To learn more about our Enterprise offering, they can reach out to <a href="mailto:[email protected]">[email protected]</a>.</li>
544
+
</ul>
578
545
</li>
579
546
<li>
580
-
If you intend to maintain the code on behalf of your client, we recommend exploring our new Application-Specific Usage (ASU) licensing model, designed for agencies managing multiple clients.
581
-
This offering includes MSP volume discount pricing (VDP) and is custom tailored to your multi-client business.
582
-
To learn more and see if you qualify, please reach out to
If you intend to maintain the code on behalf of your client:
548
+
<ul>
549
+
<li>
550
+
If your agency has under 13 developers, you may qualify for our new Agencies Expansion package coming out with the Business plan, available to FlutterFlow Expert Agencies.
551
+
<ul>
552
+
<li>As part of the add-on, you can:</li>
553
+
<ul>
554
+
<li>Purchase up to 7 additional seats beyond the 5 included in Business at $65/seat/month (12 seats total per team).</li>
555
+
<li>Invite individual paid users to specific projects without requiring them to be team members.</li>
556
+
</ul>
557
+
<li>To become eligible, you can apply to be an Expert Agency through our <a href="https://contra.com/opportunity/rWlmk2Yv-become-a-flutter-flow-agency">Contra page</a>. Existing Expert Agencies listed on Contra will be pre-approved to select the Agencies Expansion package starting August 4, 2025, regardless of team size.</li>
558
+
</ul>
559
+
</li>
560
+
<li>
561
+
For larger agencies with more than 12 developers and managing multiple enterprise-level clients, we recommend exploring our new Application-Specific Usage (ASU) licensing model. This offering is custom tailored to your multi-client business with Enterprise features, Managed Service Provider (MSP) volume discounts, and potential for co-marketing opportunities. To learn more and see if you qualify, please reach out to
0 commit comments