Pricing issues with GlideOS

I’ve been heavily testing the beta of GlideOS and I’m impressed with what it delivers.

But the pricing scheme is a real challenge. Not that it’s too expensive per se, but rather that it’s sort of impossible to know how much your project is going to cost to build–at any point in the process really, but particularly at the start. And once you’re sort of deep into an app, you’re unlikely to abandon it (c.f. the “sunk cost fallacy.”) so you keep adding credits in the smallest increment hoping that this will be the final refill. Until it’s not, and you find yourself thinking “gone already?!?”

I want to suggest to the Glide team that I think that frustration could be a liability for this success of this new endeavor. Especially when the model for glideOS is a business tool that someone in the company uses to build apps for the company team to use. Fine for me cause I’m the owner of our small business, but if you’re spending someone else’s money like this, for which it will be impossible to tell your boss the budget for the project until you’ve already blow through it all…that could backfire.

The lack of transparency on prompts = credits is also sometimes a little maddening when you pay for the Agent’s “mistakes.” I’ve shared with the team elsewhere that It would be useful to at least be able to track prompt-by-prompt how much you’re using in credits; a table in the billing section for example. Hopefully that is on the way.

But also, if I’m not mistaken they have already nudged up the cost of credits. I believe a week or so ago additional credits–once you’ve used your included credits–were .10 per credit. Now they are .12. I assume this was done to incentivize upgrading your plan over just refilling credits. I’m not sure what the happy medium is but I feel like a more generous set of credits in the plan or maybe adjusting how quickly they are expended when using your plan credits would be good so folks don’t feel like they are endlessly chasing a finished product with more and more $$$.

@NoCodeAndy and @david for visibility.

Hey @BLA_68,

Apologies for the delayed response here, and thanks for the post.

Transparency on credit consumption is one of the biggest pieces of feedback we’ve received over the last couple months. The team’s aware of it, and working through how to best address it.

One of the challenges is that credit usage is highly variable depending on what a user is trying to do. While we work some magic on the GlideOS side to optimize for token efficiency, we don’t know how the models will react to a user’s specific prompts.

This is true across the board for AI agents and agentic software development, though. We see the meter running while we build. That’s a first. The industry as a whole is figuring it out.

Still… compare the relative cost of that to the time spent on doing this manually.

For larger organizations concerned about AI credit/token costs: our MCP server is in the works, which should help with the economics. We shared a preview on LinkedIn.