Glide’s pricing model and resource limitations make it well-suited for SMBs and non-mission-critical use cases, but it feels restrictive for larger organizations with more complex infrastructure needs.
Many enterprises already have resource configurations in place—Postgres, Redis, MongoDB, and other databases. However, Glide’s current approach forces reliance on its own data layer, limiting its ability to support apps that need to stitch together multiple dependencies.
For Glide to scale beyond SMBs, I think a more robust resource & integration layer is a must to gain buy on from these orgs. Instead of focusing primarily on Google Sheets and Airtable (which most engineers know aren’t scalable for serious workloads), Glide could:
• Expand native support for databases like Postgres, Redis, and enterprise-grade APIs.
• Provide a more flexible data layer, enabling direct connections instead of requiring data replication.
• Improve scalability, allowing apps to integrate seamlessly with existing infrastructure.
I’m really impressed with Glide’s editor and feature set (particularly their implementation of UI)—better than many competitors in some areas—but expanding its resource model would unlock higher-value use cases and larger customers
Would love to hear if this is something Glide is considering so we can build out some tools here.