Plugins

A plugin is a signed extension you add to Speedwave. Some plugins add an integration Speedwave can call, others add resources for Claude to use: skills, commands, agents, and hooks. Plugins sit on top of the open-core product. The Speedwave core is Apache-2.0-licensed, and plugins are distributed separately from it.

Plugins are written, developed, and shipped exclusively by Speednet, and only Speednet signs them. Every plugin ships as an Ed25519-signed ZIP package, and Speedwave checks that signature when you install it, and again every time it loads the plugin: rendering container setup, building the image, mounting resources, listing plugins in the UI, and auditing plugins at startup. Change one byte of any file in the package and the next check fails, so a tampered plugin does not load.

You install a plugin once for your user account, then enable it per project. The same plugin can run enabled on one project and disabled on another, and each project keeps its own credentials for it. See using plugins for the install and setup steps.

A plugin’s worker runs under the same hardening as Speedwave’s built-in workers: no privileged mode, no host networking, a read-only root filesystem, and credentials it can only read, never write. Browse what Speednet has built so far in the plugin catalog.

Plugin catalog The plugins Speednet builds and signs: GLPI, Figma, Presale Generator, Stallion.

Using plugins Install a plugin, enable it for a project, and set its credentials.

Writing a plugin Build a plugin and have it signed.

For how signature verification and isolation work under the hood, see the plugin mechanism.