What's your plugin model for Rust? Are they compiletime or interpreted?

The plugins are natively compiled Rust crates, not interpreted or dynamically loaded.

We considered WASM and libloading, but plugins often require database connections or other privileges. With WASM, supporting that would be the SDK’s responsibility.

Dynamic loading with libloading didn’t offer enough benefit for this design, so we chose modular crates compiled into the application.

▲

rileycalhoun022 5 hours ago | parent [-]

The compile-time choice makes sense for a gateway: plugins sit in the hot path and often need database or queue access, which is awkward to expose through a WASM sandbox. The cost is the workflow verdverm points out: there is no prebuilt image to just pull and run. Do you plan to publish an official build with the default plugin set, for people who don't need custom plugins?

	▲	Andydy25 5 hours ago \| parent [-]
		We do have an official build on GitHub Releases with first-party plugins built in.