Meridian
Dev tooling orchestrator
Tackle
Orchestrates engineering assistants and security scanners across the development estate. Automatically configures tooling based on active compliance policy so developers work with the right tools, correctly configured, without manual setup.
What it does
Tackle manages the selection, configuration, and deployment of developer tools and security scanners across an engineering organisation. Rather than requiring each team to manually configure their toolchain for compliance, Tackle reads the active policy in Chancery and automatically configures the appropriate tools — selecting scanners, setting enforcement thresholds, and adjusting configurations as policy changes. Every tool installation and usage event is tracked, creating an auditable record of the organisation's tooling posture.
Tackle pulls approved tools and scanners from a governed catalog that filters available tools by active policy. This means developers are not choosing from an unconstrained tool catalog — they are choosing from a set that has already been vetted against what the organisation's compliance posture requires.
Who it's for
Tackle is primarily used by Platform Engineers and DevOps teams responsible for managing the developer tooling estate. It is also relevant to Security Engineers who need confidence that security scanning tooling is consistently configured and enforced across the organisation.
Works best with
-
Chancery
Active Chancery policy drives Tackle's tool selection and configuration. Without Chancery, Tackle operates against the public control catalogs. With Chancery, tool configuration is automatically aligned to your organisation's specific compliance requirements.
-
Slipway
Slipway deployment events feed Tackle, so tools are automatically configured or deployed as new services and environments come online. Tackle stays aware of deployment changes — no manual sync required.
How it fits the platform
Tackle sits at the engineering layer of the compliance loop — between policy definition and runtime monitoring. It is the mechanism by which compliance policy reaches the developer's day-to-day toolchain without requiring developers to understand compliance requirements directly. Policy changes in Chancery propagate automatically to tool configurations in Tackle, keeping the engineering estate in alignment with the organisation's current compliance posture.