Zion ReleaseStation turns your NAS into a deployment control center: connect Git, discover sites from Web Station, run pipelines, verify release health, and quickly roll back to a previous version.
Instead of SSH sessions, memorized commands, and manual uploads, every deployment becomes repeatable, traceable, and verifiable — with the same steps every time.
Turn sequences of manual commands into a reusable, visible pipeline.
See the branch, commit, trigger, and outcome of every run in one place.
Health checks and explicit statuses reduce the chance of leaving a broken release active.
Keep release history and a clear path back when production does not behave as expected.
Choose a site discovered in Web Station or configure the project root manually.
Repository, branch, and an Ed25519 deploy key without storing plaintext passwords.
Composer, npm, migrations, cache, custom steps, and deployment.yml.
Live logs, exit codes, timeouts, and HTTP health checks.
Atomic switching where available, with controlled rollback when needed.
ReleaseStation is built for the DSM ecosystem: it detects Web Station, reads hosted applications through a dedicated adapter, and helps identify the document root, project root, and framework before the first deployment.
GitHub, GitLab, or a generic Git repository can trigger the same pipeline you run manually. ReleaseStation preserves context, serializes deployments per site, and prevents concurrent executions.
Visual pipeline, read-only live terminal, release timeline, command palette, and a deployment.yml editor. Critical information stays visible without hiding technical details.
ReleaseStation is not limited to Laravel. The application runtime remains Go, while project tools are resolved explicitly through the Tool Registry.
Define deployment steps in a versioned file, but treat pipeline changes as sensitive code: a changed configuration must be reviewed before it can control automated deployments.
schema: zion.releasestation/v1 deployment: strategy: atomic retain_releases: 5 pipeline: - name: Composer install command: composer args: - install - --no-dev - name: Build frontend command: npm args: [run, build] health: url: https://example.com/up retries: 5
ReleaseStation starts from explicit boundaries: a non-root package user, direct process execution, encrypted secrets, and strict validation of paths and Git hosts.
Pipelines use command + args and are executed as direct processes. Project roots are canonicalized, symlink escapes are rejected, and repositories cannot arbitrarily inject absolute executables.
After saving, the interface shows only that the secret exists and provides an option to replace it.
Two releases never modify the same project root at the same time.
A health check can roll back to the previous release without pretending to automatically reverse database migrations.
No essential features scattered across artificial tiers. The license controls the number of managed sites, and capacity can be expanded with additional packs.
Git automation, Web Station discovery, pipelines, release history, health checks, rollback, and security features in one edition.
Increase the limit without changing the product or unlocking separate feature tiers.
No. Web Station remains responsible for hosting. ReleaseStation manages the Git workflow, deployments, releases, logs, checks, and integration with hosted sites.
No. The architecture includes detectors for Laravel, WordPress, Symfony, Flarum, and generic PHP/Node projects. The pipeline remains configurable.
No. The recommended flow uses Ed25519 deploy keys and known_hosts verification. The private key stays on the NAS and is protected by the application.
Execution stops, the failed step is highlighted, and the log remains available. With the atomic strategy, the new release does not go live until activation; a failed post-activation health check can trigger a rollback to the previous release.
No. The product is designed for the DSM 7 package-user model, with explicit access only to project directories that the administrator prepares for deployment.
Yes. Zion ReleaseStation Pro starts with 5 managed sites and can add capacity packs without changing edition or feature set.
Connect your repository, define the pipeline, and let ReleaseStation turn every release into a visible, repeatable, and verifiable process.
