Synapse Packs and Plugin Bundles for Installable Ecosystem Presets #48

Open
opened 2026-05-24 03:09:00 +02:00 by FTMahringer · 0 comments
FTMahringer commented 2026-05-24 03:09:00 +02:00 (Migrated from github.com)

Problem / Motivation

Synapse already plans bundles in early mock/idea files, but this should be tracked as a first-class feature.

Single plugins are useful, but many real setups will require multiple plugins, templates, workflows and presets that belong together.

Examples:

  • Homelab Monitoring Pack
  • Proxmox Operations Pack
  • OpenAI-Compatible Provider Pack
  • Discord Channel Pack
  • Local AI Runtime Pack
  • Developer Starter Pack
  • Company/Internal Plugin Pack

A pack/bundle system would make Synapse easier to install, share, version and publish.

Related issues:

  • #30 Plugin Store Website
  • #38 Plugin API & Ecosystem Architecture Refactor for Long-Term Extensibility
  • #47 Monitoring Provider Plugins
  • #44 Synapse Node Agent for Linux Hosts, Homelabs and Infrastructure Integrations

Proposed Solution

Introduce Synapse Packs / Plugin Bundles as installable ecosystem presets.

A pack could include:

  • plugins
  • plugin dependencies
  • workflows
  • templates
  • ECHO presets
  • Digital Twin topology templates
  • dashboard widgets
  • provider/channel defaults
  • documentation
  • example configurations

Example manifest:

id: synapse-pack-homelab-monitoring
name: Homelab Monitoring Pack
type: pack
version: 1.0.0
requiresSynapse: ">=3.0.0"
plugins:
  - synapse-plugin-prometheus
  - synapse-plugin-loki
  - synapse-plugin-uptime-kuma
  - synapse-plugin-netdata
workflows:
  - incident-summary
  - service-down-alert
presets:
  - echo-homelab-diagnostics
  - digital-twin-homelab-map

Pack Types

Possible pack categories:

starter-pack
integration-pack
monitoring-pack
provider-pack
automation-pack
company-pack
local-only-pack
developer-pack

Use Cases

Homelab Monitoring Pack

Installs integrations for Prometheus, Loki, Uptime Kuma and Netdata and adds ECHO diagnostic presets.

Proxmox Operations Pack

Installs Proxmox reader integration, node agent support, workflows and dashboard widgets.

Company/Internal Pack

A company can host an internal pack that installs only approved internal plugins, workflows and templates.


Security / Governance Requirements

  • packs must declare all included plugins and permissions
  • install-time permission summary
  • trusted/verified pack badges
  • support for internal/company plugin stores
  • compatibility checks
  • dependency checks
  • optional lockfile for reproducible installs
  • ability to uninstall or disable a pack cleanly

Future Ideas

  • pack lockfiles
  • pack templates
  • one-click install from plugin store
  • internal pack registry
  • pack update channels
  • pack signing
  • pack compatibility matrix
  • pack migration scripts

Priority

Medium / High

Packs would make the Synapse ecosystem much easier to use once plugins, workflows and integrations grow.

## Problem / Motivation Synapse already plans bundles in early mock/idea files, but this should be tracked as a first-class feature. Single plugins are useful, but many real setups will require multiple plugins, templates, workflows and presets that belong together. Examples: - Homelab Monitoring Pack - Proxmox Operations Pack - OpenAI-Compatible Provider Pack - Discord Channel Pack - Local AI Runtime Pack - Developer Starter Pack - Company/Internal Plugin Pack A pack/bundle system would make Synapse easier to install, share, version and publish. Related issues: - #30 Plugin Store Website - #38 Plugin API & Ecosystem Architecture Refactor for Long-Term Extensibility - #47 Monitoring Provider Plugins - #44 Synapse Node Agent for Linux Hosts, Homelabs and Infrastructure Integrations --- ## Proposed Solution Introduce Synapse Packs / Plugin Bundles as installable ecosystem presets. A pack could include: - plugins - plugin dependencies - workflows - templates - ECHO presets - Digital Twin topology templates - dashboard widgets - provider/channel defaults - documentation - example configurations Example manifest: ```yaml id: synapse-pack-homelab-monitoring name: Homelab Monitoring Pack type: pack version: 1.0.0 requiresSynapse: ">=3.0.0" plugins: - synapse-plugin-prometheus - synapse-plugin-loki - synapse-plugin-uptime-kuma - synapse-plugin-netdata workflows: - incident-summary - service-down-alert presets: - echo-homelab-diagnostics - digital-twin-homelab-map ``` --- ## Pack Types Possible pack categories: ```text starter-pack integration-pack monitoring-pack provider-pack automation-pack company-pack local-only-pack developer-pack ``` --- ## Use Cases ### Homelab Monitoring Pack Installs integrations for Prometheus, Loki, Uptime Kuma and Netdata and adds ECHO diagnostic presets. ### Proxmox Operations Pack Installs Proxmox reader integration, node agent support, workflows and dashboard widgets. ### Company/Internal Pack A company can host an internal pack that installs only approved internal plugins, workflows and templates. --- ## Security / Governance Requirements - packs must declare all included plugins and permissions - install-time permission summary - trusted/verified pack badges - support for internal/company plugin stores - compatibility checks - dependency checks - optional lockfile for reproducible installs - ability to uninstall or disable a pack cleanly --- ## Future Ideas - pack lockfiles - pack templates - one-click install from plugin store - internal pack registry - pack update channels - pack signing - pack compatibility matrix - pack migration scripts --- ## Priority Medium / High Packs would make the Synapse ecosystem much easier to use once plugins, workflows and integrations grow.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
FTMahringer/Synapse#48
No description provided.