Pricing
On Request
Subscription · Automic V24+
Software · Automic

3C Release Manager — transport, compare & deploy

The 3C Release Manager is a transport, comparison and deployment tool for Automic Automation that revolutionises how configurations move between DEV, TEST, UAT and PROD environments. Snapshot-based change capture, diff analysis, rollback-safe deployments and optional Git synchronisation — all in one web application that integrates directly with Automic V24+.

Licensing
Subscription term-limited
Compatible with
Automic AE V24+
Stack
Java 17 · Tomcat 10 · PG 15
Deployment
On-premise / SaaS
Overview

The 3C Release Manager is Tricise’s release governance solution for Automic Automation. It extends the standard Automic transport case with structured snapshot-based configuration capture, diff analysis between environments and points in time, deployment packages with automatic rollback, user-story-based change grouping, and optional Git synchronisation — turning ad-hoc transports into auditable, repeatable releases.

Most Automic landscapes move changes between DEV, TEST and PROD with manual transport cases, unclear rollback paths and no structured record of what was deployed when or by whom. The 3C Release Manager closes that gap: every deployment creates its own backup and validation snapshot, every change is linked to a user story, and every action lands in the audit log — so you always know what moved, why it moved, and how to roll it back.

Subscription-based licensing. The 3C Release Manager is licensed as a time-limited subscription — not a perpetual license. The term is agreed individually per customer (typically 1, 2 or 3 years) and includes product updates, new feature releases and Tricise technical support for the full duration. When the subscription ends, the license expires and must be renewed to continue operating the 3C Release Manager. Pricing scales with the number of managed Automic environments and is provided on request.

Key benefits

Release governance, not ad-hoc transports
Snapshot baselines, scoped diffs and deployment packages replace manual transport cases with a structured, auditable workflow. Every release is versioned, every change is traceable to a user story, and every deployment leaves a complete audit trail.
Rollback-safe by default
Every deployment automatically creates a backup snapshot before it runs and a validation snapshot after it finishes. If something goes wrong, the Rollback button generates a reverse deployment that restores the exact previous state — no manual recovery, no guessing.
Parallel work without collisions
The Conflict Analysis tab detects when multiple user stories touch the same Automic objects and surfaces them before deployment. Large development groups can work in parallel on the same system without silent overwrites or last-minute surprises.

What’s included

›Snapshot engine
Incremental capture of every Automic configuration object. The first snapshot builds the baseline, subsequent ones only store what actually changed — fast, compact, and repeatable.
›Diff analytics
Compare two snapshots or two environments to surface newly created, deleted, modified and moved objects. XML and tree-view comparison per object, with optional pre-filters for noise suppression.
›Deployment packages
Collect changes into ordered deployment packages sourced from snapshots, diffs or user stories. Create, modify, delete, move and manual steps — all executed in a controlled run log with pause, resume and breakpoint support.
›User stories & conflict analysis
Group configuration changes by business requirement, link to external ticket systems like Jira, and detect conflicts with parallel stories before they reach production.
›Rollback & validation snapshots
Every deployment is wrapped in automatic backup and validation snapshots. A single Rollback button generates a reverse deployment that restores the previous state — no manual recovery required.
›Rule-based mass changes
Apply transformation rules during deployment using the same syntax as the Automic AEDB Change utility. Perfect for host renames, path rewrites and environment-specific adjustments at scale.
›Git synchronisation
Optional per-environment Git sync pushes every successful snapshot to GitHub, Bitbucket or any Git repository. Credentials or SSH key auth, configurable branch per environment.
›Role-based access & 4-eyes principle
Fine-grained roles for environments, snapshots, diffs, deployments and user stories. The optional 4-eyes principle for transport releases supports regulated and change-controlled environments.

What you get

✓ Subscription license
Time-limited term per agreement, scoped by managed environment count
✓ Installation & onboarding
Guided installer plus full documentation, manual path available
✓ Automic V21+ integration
TLS-secured Java API connection to one or many AE instances
✓ Updates throughout the term
All new releases and features included for the full subscription duration
✓ Tricise product support
Direct support from the team that builds the product
✓ Optional training & rollout
Team enablement and release-process design sessions
Ready to govern your releases?
Talk to our experts about licensing, integration, training, or schedule a live demo.
Scroll to Top