GPUI-CEGPUI-CE
Community-maintained · MIT OR Apache-2.0

A GPU-accelerated
UI framework
for Rust.

GPUI-CE keeps the hybrid immediate/retained UI framework behind Zed's interface moving on its own schedule — independently maintained, openly governed, and built for anyone shipping fast, native UI in Rust.

01 — At a glance

Views compose like functions.

A minimal counter view: state lives on the struct, layout reads like a stylesheet, and every frame is rebuilt cheaply and diffed onto the GPU.

src/counter.rs
// a small view over app state
struct Counter {
    count: i32,
}

impl Render for Counter {
    fn render(&mut self, cx: &mut Context<Self>) -> impl IntoElement {
        div()
            .flex()
            .gap_3()
            .p_4()
            .bg(rgb(0x131315))
            .child(format!("count: {}", self.count))
            .child(
                button("increment").on_click(cx.listener(
                    |view, _, cx| {
                        view.count += 1;
                        cx.notify();
                    }
                ))
            )
    }
}

02 — What you get

Everything a native UI needs, nothing it doesn't.

GPU-accelerated rendering

Every frame is composited on the GPU through a native Metal, Vulkan, or Direct3D backend, keeping interfaces fluid under heavy layout churn.

Hybrid render model

Compose views with the ergonomics of immediate-mode UI while GPUI-CE retains and diffs the element tree for you between frames.

Native performance

No DOM and no browser runtime. GPUI-CE talks directly to the platform's windowing, input, and graphics layers.

Cross-platform

One codebase targets macOS, Windows, and Linux, with consistent input handling, text shaping, and accessibility behavior.

Community governance

Releases, RFCs, and roadmap decisions happen in the open, decided by maintainers and contributors instead of a single vendor.

Batteries included

Flexbox-style layout, text shaping, animation primitives, and an accessibility tree ship in the core crate.

03 — Why a community edition

The framework, kept moving on its own terms.

GPUI was built to serve one editor's roadmap. GPUI-CE exists so the framework itself can grow independently — its own versioning, its own review process, and a contribution path open to anyone building with it, not only those building Zed.

Origin
Forked from the gpui crate built by Zed Industries for the Zed editor.
Release cadence
Decoupled from Zed's editor release schedule.
Governance
Public RFCs and a maintainer team drawn from active contributors.
Scope
UI framework only — no editor-specific APIs or dependencies.
License
MIT OR Apache-2.0, unchanged from upstream.
Affiliation
Independent project, not affiliated with or endorsed by Zed Industries.