Keep your tools. Connect your lifecycle.

Development context, without a second system of record.

KaaS ANCHOR maps your Windchill Software Components to their Git repositories, shows branch, build and commit context where your product is governed, and lets you submit a build straight into the existing Windchill release and change process, without ANCHOR becoming a second ALM system alongside Git, CI/CD and Windchill.

Request a walkthrough View all products

Why KaaS ANCHOR

Minimum customisation, maximum standard

Built the MiniMax way: on Windchill's own capabilities, not a bespoke layer bolted on top.

A clear division of responsibility

Git stays Git. CI/CD stays CI/CD. ANCHOR connects them to Windchill without taking over what they already do well.

Governed, not duplicated

Every submitted build becomes part of your existing Windchill release and change process, with no parallel system of record.

How it works

STEP 1

Connect

Map each Windchill Software Component to its Git repository, with branch, tag, commit and build IDs visible in context.

STEP 2

Navigate

Move directly between Windchill, Git, CI/CD and TRACE, and query the product-software relationship in either direction.

STEP 3

Submit

Push a selected build into the existing Windchill release and change process, with nothing new to govern.

What's included

Core capabilities, available from the first release.

Windchill Software Component ↔ Git repository mapping

Product, component and change context in the developer environment

Branch, tag, commit and build ID references

Direct navigation across Windchill, Git, CI/CD and TRACE

Two-way query: product configuration ↔ software configuration

Submission of a build into the existing release & change process

Multiple Windchill environments (PROD, DEV, TEST)

Works with your existing CI/CD pipeline

REST API for automated workflows

Compatible with KaaS TRACE for CRA traceability

Auditability

Standard connectors, minimal customisation