FOR DESKTOP APP DEVELOPERS

A real window. No browser inside.

Aster draws your whole interface on the processor, in a native window on Windows and Linux. Call it from Rust, C or C++.

Sortable, filterable data tableDrawn by Aster

Built for the desktop

One small library. It draws everything itself.

A native window in one call

Windows 11 and Linux, with the system clipboard.

Quick when it moves, quiet when it doesn't

Only what changes is redrawn, and at rest it sleeps. Big windows at 2x scale are the slow case.

Next to no processor time when nothing moves.

Nothing else to install

Fonts are built in. No graphics drivers, no system fonts, no browser engine.

On Linux it links only the C runtime.

From your language

Rust directly. C, C++ or anything that can call C, through one header. Node.js and .NET bindings too.

One C header, 25 functions.

Where it fits

Aster is a UI toolkit that draws every pixel itself. There's no HTML or CSS.

A team chat app drawn by Aster: channels, direct messages, a conversation and a details panel, with made-up names.Drawn by Aster

Coming from a browser-based desktop shell

Browser-based shells ship a browser engine with every app. Aster is one native library that draws the interface itself.

Coming from a native widget toolkit

Some native toolkits can draw without a graphics card too. Aster also draws the same pixels in the browser, from the same Rust code.

Example scenarios (illustrative)

Read 3 short examples

An internal tool in one file

A small team writes its ops dashboard as one JavaScript file. In CI, the same file renders a picture of every screen to check each change.

A Markdown editor for big files

Our own Markdown viewer and editor is built on Aster. It runs on Windows and Linux.

Panels inside a Rust engine

A Rust tool draws its panels with Aster into a plain pixel buffer, then shows them its own way, as a texture or in its own window.

Good to know

  • Windows and Linux today. There's no macOS build.
  • One window per app, left mouse button only. Menus and dialogs are drawn inside the window; there's no system menu bar, tray icon or file picker.
3 more to know
  • No desktop screen-reader bridge, though every control has a name and role you can read. Input-method text arrives whole, the bundled fonts don't cover Chinese, Japanese or Korean, and emoji aren't supported.
  • Big windows at 2x scale are the slow case: a full redraw can take 70 to 140 ms. Small changes stay quick.
  • There's no HTML or CSS, so moving from a browser-based shell means rewriting the interface. Aster is before 1.0, so names can change.