Updates to Glide’s new plans and pricing

I can live with the change but would love Google Analytics and some kind of API use on maker. I’m building a B2C app and targeting thousands of users. Anything above Maker is going to be way expensive on the user front.



If that changes, we’ll let you know. :+1:

1 Like

@NoCodeAndy I have another question. In the classic apps, we used to have a configurable tag above the images of the collections, in addition to a floating button that we used for various functions. They removed that; do they plan to add them back? Both functions were very useful.


May I correct this… In the New Business plan pricing the cost per active monthly user (above initial 20) is 10$ a month (if billed monthly) and 8$ per active monthly user if the plan billed yearly.

I’m on the free plan, so why do Updates increase and have a limit of 1000 Updates? What happens if this limit is reached?
Screenshot 2024-01-27 125316

Thank you, Glide team, for making huge efforts to accommodate people’s requests. I see it as you are working really hard at finding these compromises while still reassuring that Glide can grow as a company and become more powerful tool for us all to enjoy and benefit! In the past week I have noticed like never before that your team works really fast at solving anything that comes your way. You are the best! I really appreciate you all! Thank you!


Hi Pebi! Please see this thread:

1 Like

Hey @NoCodeAndy - I think your plans are moving in the right direction.

I’d ask you guys to seriously consider opening up your Glide Tables API for the Maker plan.


You’re already charging us updates when we sync with Google Sheets. Just charge us the same update when we write to the Glide Table instead :slight_smile:

And as you make more of your own integrations available to Maker, folks will be moving workflows away from Make/Zapier and into Glide - which means you charge us even more updates :slight_smile:

Seriously, limiting access to Glide API just makes no sense.

I know you have a native Zapier/Make app for the Maker plan in the making. Awesome. Obviously, these apps will be using Glide Tables API.

So why make Make/Zapier apps available to Maker plan, but not the raw API? :slight_smile: For example, we’re increasingly switching to ActivePieces for our workflows. So I’d be very happy to just use ActivePieces’ HTTP module to interact with Glide API :slight_smile:

Anyway - have a think.

With lots of love!



I think there are many Gliders wondering the same thing…

From the Glide Docs:

Internal business software for 90 employees:

  • Off-the-shelf SaaS solution. $5 per user per month. Total monthly ongoing: $450
  • Glide’s Business plan: 20 employees included in the plan ($250). 70 users on top at $8 monthly ($560). Total monthly ongoing: $810. You need to add to that the initial cost of building the app, whether it’s built internally (time) or externally (monetary).

You could jump to the conclusion that Glide is therefore not worth it.

Two things.

First, customization. In one case you need to adapt your processes to whatever the existing SaaS solution provides. In the other, the company builds exactly what it needs. I often tell prospects it makes little sense to rebuild existing solutions. Of course it’s fun and nerdy. Many love it and I’m among them. But that is not where the value is. Can you rebuild many existing SaaS solutions on Glide. Perhaps. But why bother?

Second, Glide makes increasingly more sense when a company builds multiple apps. Take the example above. At 1 app, the extra customization would need to justify the extra cost. At 2 apps, the company might break even. Granted, one needs to take into account the cost of the build. What happens at 5 apps, 10, 15, or more? What happens when whipping up a Glide app becomes so easy that anybody inside a company can do it, like any text document, spreadsheet or deck of slides?

The way you could see it, Glide might be attempting to build a new category of office software. Currently, in any office suite, we have documents (vertical text and images), spreadsheets (tables of numbers), slides (text and images for presentations). These are formats in which we create, update and display information. None of them correspond to the way we consume information in our personal lives, which is through apps. Glide can be seen as a new category of office software, to consume text, numbers and images, add to that actions and automation, in a format we are all comfortable with. When a company starts using an office suite, they don’t think of creating 1 single document, 1 single spreadsheet, or 1 single deck of slides. They think in terms of “many”. Why limit your thinking to 1 single Glide app? This is why the Team+ plans offer unlimited apps. Of course the analogy has its limits (I know some will find valid arguments to contradict this) and this view might not in fact correspond to Glide’s long term strategy, but it’s one way of seeing it. All of this to say that in my view using Glide on Team+ plans makes increasingly more sense as you, or the company, builds more applications.


Hey, @Darren_Murphy. I appreciate you pointing out this list. Do you happen to have any insight on the timeline for the remaining components becoming available (e.g., Favorites)?

Also, while the Button component was migrated (obviously) the “floating” style for buttons didn’t make it over like @Jose_Ignacio pointed out:

Never considered this direction… that would be revolutionary. :muscle:


No I don’t, sorry.
What I do know is that there are some major enhancements for Collections in the works that are due to drop later this year.

Given that updates are no longer counted with native tables on the new plans, it wouldn’t surprise me if the favourites component is de-prioritised now. Because it’s easy enough to roll your own favourites. That’s just speculation on my part, so please don’t quote me :slight_smile:


I understand that you are not paid for developing & maintaining Glideapps :slight_smile:
We should probably almost double the 5$ to incorporate our own “developers” costs.

Thanks for these sound remarks.

Usually, companies prefer to start & test with 1 app.

What happens if the Glide pricing model changes again -:slight_smile:

I used to think like this 1 year ago, I don’t anymore: Glide is of course much simpler than code, but it is not that simple; very few non-tech people will learn “relation”, “actions” etc.

1 Like

Slick! I wasn’t around for classic apps, so I never saw those. :sweat_smile:

I’ll pass this along to the product team. It’d be a nice enhancement to collections.


That’s where many of our larger customers really shine. They don’t treat Glide as a platform for a single app. Instead they’re building entire suites of discrete custom apps for different teams.

1 Like

I can speak from experience on this one, because the company I work at is a Glide Enterprise customer. Currently, we have a suite of 10 Glide Apps that are actively used on a daily basis.


Are you in our expert program? You should not pay for Glide on behalf of your customer—they should pay for Glide directly.