Bring Claude, Cursor, ChatGPT, or any MCP client. GlideOS gives it apps, data, and workflows.
01 / The team layer
Your agent is replaceable. Your software is not. GlideOS keeps every app, table, permission, and workflow in one shared system.
Field Inspections · Acme only
Alex builds in ChatGPT
Sam continues in Cursor
The app, data, and permissions stay in GlideOS—even when the builder or agent changes.
Hosting and storage
The app is not on someone’s machine.
Database
Shared, live business data.
Code storage
No GitHub required. Git is optional.
Team permissions
Keep apps private to the company.
Workflows
Automations live next to the apps.
Edit in GlideOS
Lose the agent, keep the software.
02 / Why BYOA
Your agent already knows your files and chat. Glide joins that conversation.
Keep search, files, and other connectors. Add Glide’s apps, data, and workflows.
Use the model on the plan you already pay for. Glide credits still cover Runtime AI and workflows GlideOS runs.
03 / Use cases
Build an app, use context from another tool, query live data, or ship a workflow.
Claude Code · Claude Max · Fable
Stay in Claude Code. Pick Fable or Opus. GlideOS hosts it.
ChatGPT
The file and the thread stay. Glide is another tool in the same chat.
Cursor Agent · Fable
Query live tables the way you’d grep a repo. No new dashboard required.
Terminal agent
Same MCP. Build the app, query the data, or leave a workflow running.
A remote server for your org. Your agent signs in as you and can build apps, query data, and ship workflows. More in the GlideOS MCP docs.
GlideOS Team+