Documentation

Desktop App

How the Spirefy Studio desktop app is put together: a native shell, a system WebView, and a plugin engine compiled in.

Browse documentation

Spirefy Studio is a real native desktop application, not a web page in a wrapper. It uses your operating system’s own WebView for the interface and compiles the plugin engine straight into the binary, so there is one app to install and nothing else to run.

One native binary

The app ships as a single binary for macOS, Windows, and Linux. The plugin engine and its WebAssembly runtime are compiled in, so there is no separate runtime or background service on your machine. It uses the operating system’s WebView (WKWebView, WebView2, or WebKit2GTK) rather than bundling a browser, which keeps it far smaller than an Electron app and quick to start.

The shell and the plugins

The app is a thin shell, the window, the menu bar, the status bar, and the layout, provided by the desktop framework. Everything inside that shell is a plugin: the Imports, API Workshop, Workflows, and Exports pages, the importers and exporters, the curation engines that lint and govern inside the API Workshop, and the tools. The Technology page covers how this works in depth.

The Plugin Manager and profiles

Because the features are plugins, you decide which ones are loaded. The Plugin Manager lets you turn plugins on and off and save a set as a named profile. Load a lean profile for a focused task, then switch to a fuller one later. Switching happens in place, without reloading the window, and plugins untouched by the switch keep their state.

Your data stays local

The app works on your machine. Your APIs, the model you build from them, and your settings live locally. The paid pieces that need an account, team features and the built-in AI subscription, check in when you sign in, but the core app does not send your work anywhere.