Introducing GlideOS

Announcements
1

Hello Gliders,

GlideOS, our new AI builder for internal business apps, is now available in beta.

GlideOS instantly turns your spreadsheets into powerful apps with AI.

  1. Get started with a spreadsheet, doc, or prompt
  2. Continue building by chatting with the GlideOS agent
  3. Your apps live within GlideOS projects alongside shared data and context
  4. Publish in one click; GlideOS handles the hosting, security, and auth
  5. Invite your colleagues to GlideOS to build alongside you in the same team

Try GlideOS by signing up for a paid plan

You can also join the waitlist for our upcoming Free plan.

Learn more about using GlideOS in our docs

What’s happening to the existing Glide?

The Glide you’ve known for 7+ years is now Glide Classic, our visual no-code builder.

Glide apps built in Glide Classic are unaffected by GlideOS.

They’re separate, co-existing platforms with their own teams, subscriptions, and apps.

Reminder: GlideOS is in early beta.

We’ve spent years building Glide Classic. GlideOS is a fresh start.

We’re shipping faster than ever, based on what we see and hear from customers.

Bring your GlideOS questions and feedback to our new GlideOS section:

5

Congratulations for the launch. Looking forward to see what is built on the new platform.

6

Excited to see this launch officially. Is there an explanation somewhere of how credits are used? Its it each prompt?

7

Woohoo! Welcome to GlideOS, everyone!

Here’s a little demo to see some of our perspective on what GlideOS is for, and how it’s different from other tools: Building Trusted Business Apps with Instruments | Loom

8

Every prompt consumes credit.

The amount of credits consumed depends on the prompt and what the AI works with.

You can refer to the docs for more detail:

(Still a lot to add - we’re developing the GlideOS docs alongside the platform.)

9

I get an error when trying to login from the link in the email: “handoff failed: 401 domain_not_allowed”

Any ideas?

10

I’m so confused. The first video I have come across has tools about debugging AI builds, like that’s going to be a big thing… I haven’t seen anything that transforms a spreadsheet into a beautiful app. I was expecting lots!

Can’t wait to see how this helps make building apps better… But also triggered at the thought of my current apps being sunsetted as classic apps with spiraling subscription fees.

please provide more info and demos!

11

General sign-up is not yet open, but if you go through the pricing page, I believe you can get in.

12

Does anyone know if GlideOS is going to be mandatory at some point? Let’s say, do we have to switch to this 100% AI model, or can we choose to stay with the current model, where we have more control over the applications? We want to know if we can continue working calmly with the current version and not be forced to switch to the 100% AI model. Thanks!

13

More to come. :slight_smile:

Last week’s release of GlideOS was our early soft launch.

You’ll see more from the team over the coming weeks and months.

Glide Classic and GlideOS are separate, co-existing platforms.

In the long run, we expect GlideOS to be a better experience, but it’s still early days.

You can continue using Glide Classic and building like you’re used to.

14

How would the data tables in Glide OS work with integrations using Make, Zapier, etc.?

15

GlideOS is a separate platform from Glide Classic.

We don’t have native integrations with Make, Zapier, etc… at the moment.

16

What are some ways that data would flow in, as opposed to entering it within Glide OS?

17

You can use APIs to bring data in. I have a GlideOS app that lets me fetch data from an API and populate my data tables. What other sources did you want?

18

API was it, thanks for letting me know. Did you know ahead of time you could do that, or did you just get there with prompts?

19

I was able to do similar things and other vibecoding tools, so I assumed Glide West could do it as well. It did take a bit of prompting, but eventually got it working (the biggest hurdle was that the API is not well documented).

When I recommend perhaps is to create a standalone utility app (Glide) these instruments) whose only purpose is to fetch data from the API and sync the data tables.

Since data is shared across all apps in a singular project, you can dedicate this app to syncing data, and the other apps can just be user interface