Plugins overview

Buntime ships a set of core plugins under plugins/. They are ordinary plugins (nothing special compared to ones you write) and demonstrate every part of the plugin system: persistent routes, service sharing, request hooks, and micro-frontend UIs.

Core plugins

These plugins are enabled by default in the runtime.

Plugin	Base path	Purpose
plugin-gateway	/gateway	CORS, rate limiting, the micro-frontend app-shell, and SSE monitoring
plugin-proxy	/redirects	Dynamic reverse proxy and redirect rules
plugin-turso	(service)	Durable SQL via Turso; exposed to other plugins through provides()

Note

plugin-turso has no base — it’s a service provider. Other plugins reach its TursoService via ctx.getPlugin("@buntime/plugin-turso").

Enabling and disabling plugins

A plugin’s default state is set by enabled in its manifest.yaml. Plugins can also be toggled at runtime without a restart:

curl -X POST http://localhost:8000/api/plugins/%40buntime%2Fplugin-gateway/disable

The change edits the manifest on disk, so it survives restarts. See Plugin System → Hot reload.

Explore

Gateway Edge middleware: CORS, rate limiting, app-shell, monitoring.

Turso Durable SQL provider with local and sync modes.

Proxy Reverse proxy with static and dynamic rules.