# What is Glider

> A browser-based broadcast graphics system: design scenes, wire them to live data, play them to air.

Glider documentation · Getting Started · Web page: https://cgglider.com/docs/overview/

Sections of this page: [Introduction](https://cgglider.com/docs/overview.md) · [Core concepts](https://cgglider.com/docs/overview/concepts.md) · [Anatomy of the editor](https://cgglider.com/docs/overview/anatomy.md) · [Reading paths](https://cgglider.com/docs/overview/who-its-for.md)

The problem Glider solves and the shape of the product.

Glider is a real-time graphics program for live production. You build scenes on a canvas, connect their fields to live data — an API poller, a spreadsheet, an operator control panel — and play them to a browser output that a vision mixer or streaming encoder can key over video.

Everything runs in the browser against a Next.js server. The editor lives at /editor, the on-air output at /view/<pageId>, and every action the editor performs is also available over the HTTP API and an MCP server, so the same page can be driven by an operator, an automation system, or an AI agent.

## The three surfaces

- [Editor](https://cgglider.com/docs/workspace-layout.md): Design, wire and rehearse. Panes, tabs and docks around a canvas.
- [Output](https://cgglider.com/docs/live-output.md): The clean render that goes to air. No chrome, no editor state.
- [Control surfaces](https://cgglider.com/docs/rundown.md): Control panels, the rundown, and a Stream Deck for the operator.

![The Glider editor: scene panel, canvas, inspector, and the bottom dock.](https://cgglider.com/docs-shots/overview-editor-full.png)

> **On-air safety:** Glider treats what is on air as sacred. Edits are staged in the editor and only reach the output through an explicit publish or a live-linked page; wiring checks hard-fail before go-live rather than letting a broken binding reach the screen.