# Scalable Client Portal for 50K+ Users, Alternatives to Glide Business Plan User Limit?

**URL:** <https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471>\
**Category:** Ask for Help\
**Created:** [June 13, 2025, 4:30pm UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471 "2025-06-13T16:30:48Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mazen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mazen/32/84042_2.png) [@Mazen](https://community.glideapps.com/u/Mazen)\
**Post date:** [June 13, 2025, 4:30pm UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471/1 "2025-06-13T16:30:48Z")

</div>

Hi Gliders 👋

I’m currently building a client portal system using Glide, and I’ve hit a major concern regarding scalability.

The **Business Plan** only includes **30 private users** , and from what I understand, it starts charging per user after that. However, we already have **over 50,000 clients** , and once the system is fully built, each of them will need access to the portal for **booking services and tracking their order status**.

Given that the portal will be **self-service only** (just viewing status and booking), we don’t need advanced role-based features, just a **simple and scalable way** for each client to view and interact with their own data.

**My key questions:**

1. Is there any recommended workaround or alternative plan for supporting a large user base like this on Glide?
2. Would using **public apps with row-based filtering** be a more scalable approach?
3. Are there best practices for building **scalable client portals** that don’t require each user to be a “private” user under Glide’s licensing model?
4. Should I consider **integrating Glide with another front-end or authentication system** to handle this kind of volume?

I’d really appreciate any advice, suggestions, or experiences from others who’ve dealt with similar challenges.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![Mazen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mazen/32/84042_2.png) [@Mazen](https://community.glideapps.com/u/Mazen)\
**Post date:** [June 13, 2025, 4:35pm UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471/2 "2025-06-13T16:35:02Z")

</div>

Additional question:  
Can I **build the public-facing client portal inside my Maker team** , and at the same time, manage our internal admin/operations system under a separate **Enterprise team**?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [June 13, 2025, 4:56pm UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471/3 "2025-06-13T16:56:33Z")

</div>

You could do separate teams. The tricky part is sharing the same tables between both teams. I don’t think it’s officially supported, but I think it works to start building the second app in the same team folder with all the tables you need, and then transfer the app to the other team. The tables should stay linked between both apps in both teams.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [June 13, 2025, 10:49pm UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471/4 "2025-06-13T22:49:05Z")

</div>

> [@Mazen](#):
>
> Is there any recommended workaround or alternative plan for supporting a large user base like this on Glide?

I think you would face a dilemma here.

You have 50k users. The “spreadsheet” data sources only allow you to have max 25k.

Big Tables allow you to have 50k, but Glide does ​not allow a Big Table to be designated as the User Profiles table.

Going beyond 25k might require splitting your audience across multiple Glide apps, and that adds maintenance headache.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [June 13, 2025, 11:03pm UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471/5 "2025-06-13T23:03:26Z")

</div>

> [@Mazen](#):
>
> 1. Should I consider **integrating Glide with another front-end or authentication system** to handle this kind of volume?

I think that might be a violation of Glide’s Terms of Service. It got people banned before.

You should contact Glide’s Sales team to see what they can offer for use cases like this.

---

<div class="post-metadata">

**Author:** ![Mazen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mazen/32/84042_2.png) [@Mazen](https://community.glideapps.com/u/Mazen)\
**Post date:** [June 14, 2025, 12:33am UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471/6 "2025-06-14T00:33:39Z")

</div>

> [@ThinhDinh](#):
>
> It got people banned before.

Glad I asked before commiting 🙂

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [June 21, 2025, 12:34am UTC](https://community.glideapps.com/t/scalable-client-portal-for-50k-users-alternatives-to-glide-business-plan-user-limit/82471/7 "2025-06-21T00:34:29Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
