Marketplace
Capabilities that compose.
The Synoros app, media, network, and platform all ship as first-party plugins on the same runtime. Swap them, extend them, or ask Claude to build new ones.
Launch scope
The marketplace ships with Synoros-authored plugins only. Third-party publishing opens later, gated on six months of first-party production data, zero P0 security incidents, signing/revocation dry-run, and ToS + tax infrastructure.
synoros/media
in developmentIPTV, EPG, and multiview as a plugin.
Ships on every Foundry tier. Pipes M3U sources through an on-box stream proxy, builds an EPG from XMLTV, and surfaces multi-screen playback to web and Android TV clients. The foundry-iptv codebase refactored as a first-party plugin on the Foundry runtime.
synoros/network
in developmentVPN, AdGuard, and routing as a plugin.
The Foundry Household stack exposed as a plugin surface: WireGuard tunnel management, AdGuard Home DNS, per-device routing policies, and a dashboard that shows what's going through what. Install-time consent gates the capability-scoped network permissions.
synoros/platform
in developmentMulti-tenant AI platform, local on your box.
The Synoros SaaS refactored to run on a GPU-tier Foundry Server as a first-party plugin. Document search, compliance guardrails, audit logging. All traffic stays on your hardware; BYO Anthropic key routes frontier calls through your account, not ours.
Frequently asked
Why is the marketplace first-party-only at launch?
Trust calibration. The plugin runtime enforces sandboxed workers and capability-scoped permissions, but neither is battle-tested against adversarial code yet. At launch, the marketplace lists only Synoros-authored plugins so any issue traces to us. Third-party publishing opens after six months of first-party production data with zero P0 incidents, a signing/revocation playbook dry-run, and Stripe Tax infrastructure.
What's a plugin, technically?
A signed bundle running in a sandboxed worker on your Foundry Server. Workers talk to the Tasks API (LLM completion, service control, scoped storage, scheduling, network, hardware, inter-plugin events) with capability-scoped permissions you grant at install time. Rust service supervises the workers; manifest is YAML; SDKs will ship for TypeScript and Python.
Can I run a plugin on Foundry Lite / Household?
Some, not all. Entry tiers boot a restricted runtime that only runs media and network-class plugins. Anything that needs the GPU (local LLM, document search, agent loops) requires a Foundry GPU Server. Each plugin's detail page lists which tiers it's compatible with.
How does installation work?
From the marketplace page or the Synoros Desktop App: click Install, review the capability-scoped permissions the plugin requests (network, storage, hardware, other plugins), grant or deny, and the bundle is verified against the Synoros release key and spun up as a new worker. Uninstall cleanly reverses state.
Can I build a plugin now?
Internally, yes: `sxp init / build / publish` tooling is in development. Publishing to the marketplace is first-party-only at launch; the waitlist form below captures interest from early third-party builders for when we open it up.
Publisher waitlist
Want to publish a plugin?
Drop your name and we'll reach out before third-party publishing opens. Early publishers help shape the Tasks API surface and the signing playbook.