Syno Package Land

Architecture

Syno Package Land is Package Center first. Compose is runtime truth. SynoPkgLandService is a small trusted control plane — not Docker, not an app store.

  • Website Explains the platform and copies the Package Source URL. It does not install Apps. If the website is down, NAS units that already added the source still update from the separate packages. host.
  • Package Center The installer. Discovery, install, update, remove, and Open stay here. The website only helps Administrators add the Curated Package Source once.
  • Compose Runtime truth for images, services, networks, volumes, and healthchecks. Container Manager runs the Project. SynoPkgLandService does not translate topology into a second runtime model.
  • SynoPkgLandService Lightweight control plane on the NAS: verify attestation, initialize the Project at install/update, issue User Context, and enforce File Gateway with DSM ACL on every call. Not a catalog, not daily start/stop/logs, not a reverse proxy for all traffic.
  • Thin SPK Generated envelope the user sees in Package Center. Developer Kit and Curated CI produce INFO, wizard, Web Station ingress, and Broker glue — you maintain Compose and App Contract only.
  • Attestation Local Attestation — NAS Administrator authorized Inner Loop Deploy; valid only on that NAS. App Package Attestation — platform CI signed Curated release; required for Broker trust from Package Source install. Same SDK contract either way.

Developer Kit vs Broker

Most complexity sits off the NAS: schema, analyzer, SPK generator, Skill Pack, and Curated CI. SynoPkgLandService keeps only what must run in a trusted NAS environment. Building images, publishing to Community Repository, and serving the human website are not Broker jobs.