Syno Package Land

FAQ

Honest boundaries — what this platform is and what we deliberately did not build.

  • Is this Docker Hub?

    No. Images still live in registries you choose. Syno Package Land packages Compose plus App Contract into a thin SPK for Package Center, with DSM identity and controlled NAS capabilities through SynoPkgLandService.

  • Is this LazyCat or LPK?

    No. We borrow the inner-loop teaching order — deploy to my device first, publish later — not LPK schema, subdomain hosting, request inject, official registry, or client-native/BLE mechanics.

  • Is this SynoCommunity native packages?

    We reuse the Package Center Package Source UX that SynoCommunity popularized, but Apps here are Docker Compose based with a generated SPK envelope and SynoPkgLandService integration — not traditional binary SPK builds you compile by hand.

  • Does the website install Apps on my NAS?

    No. The website explains Apps and lets Administrators copy the Package Source URL. Install, update, and remove happen in Package Center. Developers use synopkgland deploy for Inner Loop on their own NAS — that is not a website button.

  • Do I need a public domain?

    No for v1 default entry. Zero-Configuration Entry uses the DSM URL you already have open. No DDNS, DNS, or port-forwarding requirement for the standard Web App path.

  • What if the website is down?

    NAS units that already added the Curated Package Source continue to receive index updates and SPK downloads from the separate packages. host. The website is not on the install path.

  • Where is the authoritative specification?

    App Contract JSON Schema, Developer Kit analyzer error codes, and conformance tests in the platform repository. This documentation is the map; those artifacts are the contract.