I would like to know the limitations on
the Explorer plan please, if we take a
explorer plan and make an app, can we use it
commercially? or sell it?
I would like to know the limitations on
the Explorer plan please, if we take a
explorer plan and make an app, can we use it
commercially? or sell it?
The limitations are explained on the Pricing Page.
In general, Glide is not the right tool for consumer/commercial Apps. You can try, but you will quickly find that the usage limits are far too restrictive for these types of Apps.
Thank you so much Darren, so kind of you to respond, yes, the limitations are there even with Explorer plan, I tried with simple Meeting Room reservation app for small offices to be used internally, it works well as features, like, show Busy with Red color, Available with Green color when idle, and next meeting information below, It’s simple but works for internal usage, other apps usually connects to Exchange Server and Office 365, but, this is stand alone, and can server small organizations with 3-4 meeting rooms. But, my question again is: if we are within the users limitations, can we sell it? while paying the minimum subscription to the glide? Appreciate your valuable input, Thanks
I second Darren, Glide isn’t ideal for consumer apps.
Three cases where it can work for consumer apps in my experience:
Building the prototype or minimum viable product for said consumer app. This initial version can be deployed in the market to validate product-market fit, it can be clickable and truly functional. But the app won’t technically scale to millions of users and you’ll have trouble finding a profitable business model.
A website that looks like an app and that doesn’t need signed-in users. Glide then acts as a website builder. Because Glide is a managed platform, the project owner (creator, developer, builder) gets a lot of things out of the box: hosting, storage, a content delivery network, managed scaling, continuous integration and deployment, a built-in database, built-in interface components, a library of native integrations and actions, user authentication and permissions, SSL security, custom domain and branding. Pay the subscription and get all of that (and more) just like that. This is practical for non-technical project owners or even technical builders who want a solution where they can focus more on building and deploying and less on setting up the tech.
Community apps.
The most solid use case for Glide does remain internal business applications to replace a spreadsheet, processes, pen and paper.
Yes, as long as you don’t violate Glides Terms of Use, you are free to try and monetise your App in anyway that you want to.
Great, appreciate once again that you have taken time to answer my query. Thank you so much Darren, Have a great day ahead.
Hi Nathan,
Thank you for taking the time to share such a detailed and thoughtful response. I really appreciate the clarity you provided and the effort you put into explaining the different use cases for Glide.
Your insights on prototypes/MVPs, website-style apps, and community apps were particularly helpful, and it definitely gave me a better perspective on where Glide fits best and where it may have limitations for large-scale consumer applications.
Thanks again for your time and for helping clarify this.
Best regards,
Lodhi