feat: embed providers as wasm modules#120
Merged
jeroenrinzema merged 11 commits intomainfrom Jan 24, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR introduces a plugin architecture for providers by implementing them as WASM (WebAssembly) modules using Extism. This enables sandboxed execution of provider integrations and lays the groundwork for third-party provider modules via WASM uploads.
Changes:
- Implemented WASM module registry and runtime infrastructure for loading and executing provider plugins
- Renamed database columns
type/grouptomodule/channelto align with the new provider architecture - Refactored pub/sub subject naming for consistency (e.g.,
events.projects.*→events.process.*)
Reviewed changes
Copilot reviewed 78 out of 95 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| services/nexus/internal/wasm/registry.go | Generic WASM module registry with thread-safe operations |
| services/nexus/internal/wasm/module.go | WASM module loader using Extism plugin system |
| services/nexus/internal/wasm/providers/provider.go | Provider-specific WASM wrapper with send functionality |
| services/nexus/internal/providers/registry.go | Provider registry initialization with embedded FS loader |
| services/nexus/internal/providers/channels/*.go | Channel-specific request composers (email, SMS, push) |
| services/nexus/internal/store/providers.go | Database layer updated with module/channel terminology and new CRUD operations |
| services/nexus/internal/pubsub/schemas/events.go | Refactored subject naming for consistency across streams |
| services/nexus/internal/pubsub/consumer/campaigns.go | Campaign send handler using provider registry |
| services/nexus/internal/journeys/action.go | Journey action handler for campaign triggers |
| services/console/src/types.ts | Updated TypeScript types to use module/channel naming |
| services/console/src/api.ts | API client updated to use channel/module parameters |
| modules/providers/*/main.go | Example WASM provider implementations (logger, resend, twilio) |
| pkg/modules/providers/*.go | Shared provider types for WASM modules |
| go.mod | Added Extism SDK and dependencies |
| Makefile | Added WASM module build targets |
Comments suppressed due to low confidence (1)
modules/providers/logger/README.md:1
- The heading incorrectly says 'Resend' but this is the Logger provider. It should say '# Logger'.
410ab99 to
457a3c3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR changes the way on how providers are defined by embedding them as WASM modules. The WASM modules are right now in a early alpha stage and are under active development. The vision with these WASM modules is that at some point it will be possible to embed third party WASM modules by simply uploading your compiled WASM module.