Slipway

Slipway is Meridian's deployment orchestration component. It manages the deployment of infrastructure and application resources across cloud providers and on-premises data centres, with every deployment event recorded immutably. It supports hot-swapping between cloud service providers, resilient multi-environment deployments, and fully air-gapped operation for environments with no external connectivity.

Every deployment Slipway executes is recorded as an auditable event — what was deployed, when, by whom, against which approved architecture, and to which environment. This creates an unbroken chain of evidence from design approval to production state, available for audit on demand without manual evidence assembly.

Slipway is used by DevOps engineers and SREs responsible for deploying and managing infrastructure and application resources across complex, multi-environment estates.

Your team wants governed, immutably recorded multi-cloud deployment — but without rebuilding your compliance programme first. Slipway can be deployed as a standalone deployment pipeline that gates releases against common public architectures and records every deployment event as an auditable artifact. For teams that need to demonstrate provenance and change history to auditors, Slipway provides that record without requiring a full policy or architecture governance programme.

Add Loft when you want deployments to be gated on validated, organisation-specific architecture approval rather than public catalog defaults. Add Chancery when you need the architecture validation itself to be driven by organisation-specific policy.

Slipway is the execution layer — the point at which policy and architecture decisions become real infrastructure. Its immutable deployment record is the primary evidence source for demonstrating that every change was approved, validated, and deployed correctly. That record is available to Admiralty for audit and executive review, and to Patrol as the baseline for ongoing drift detection.