Titan Cloud Release Management Overview
Learn about our release management process, including key timelines, procedures, and support resources.
Written by Jess Hamilton
Updated at October 31st, 2025
Table of Contents
Introduction
This article provides an overview of Titan Cloud’s release management process, including key timelines, procedures, and support resources to ensure a smooth and transparent experience during product or service updates.
The purpose of this guide is to outline the following critical components:
- Release Windows – Planned timeframes when updates or deployments may occur.
- Rollback Plan – Our strategy for reverting to a previous stable version in the event of unforeseen issues.
- Release Schedule – Specific dates and times for upcoming releases, including regular and ad-hoc deployments.
- Release Communication & Resources – When and how you can expect to be informed about upcoming changes or incidents.
We aim to maintain clear expectations and provide a reliable, coordinated experience throughout the release cycle.
Release Windows
This section defines Titan Cloud’s standard release cadence and maintenance windows to help customers plan around potential system impacts.
Product Area |
Standard Window |
Expected Impact |
|---|---|---|
Supply & Logistics |
Wednesdays, 2:00 AM ET (maintenance window of up to 2 hours) |
Inventory readings will be unavailable during this time. |
Compliance & Fuel Analytics |
Tuesdays, 8:00 PM ET (maintenance window of up to 2 hours) |
Users will not be able to access the software during maintenance; however, ATG data collection and inventory readings will continue. |
ATG Polling |
Scheduled as needed (non-routine) |
ATG data collection for all Titan Cloud products may be temporarily disrupted during this maintenance window. |
Note: Releases are not conducted during major holidays or weekends to minimize disruption.
Rollback Plan
This section outlines the safeguards and recovery procedures Titan Cloud employs to minimize disruption in the event a release must be reverted.
Following the deployment, the Titan Engineering team conducts comprehensive validation of all technical interfaces to ensure full operational integrity. Smoke testing is also performed within the production environment to confirm system stability and functionality.
If critical issues are identified during smoke testing that cannot be resolved promptly, the team will initiate a rollback to the previous version. This process involves a database restoration and code rollback to ensure minimal impact to customer operations.
Rollback decisions are made carefully, prioritizing service continuity and customer experience.
Release Schedule
This section provides an overview of standard release types and schedule frequency of change windows.
Release Communication & Resources
This section outlines how Titan Cloud communicates release details and provides supporting resources to ensure customers are informed and prepared.
Area |
Details |
Timing |
|---|---|---|
Product Pre-Release Notes Email |
Overview of the current release and a preview of what’s next. |
Thursday before Release Day |
Product Training Documentation |
Updated documentation posted to the Help Center. |
Release Day |
Release Notes |
Preview and final versions posted to the Help Center. |
Preview: Thursday before Release Final: Release Day |
Special/Large Feature Launches |
Highlighted in Release Preview email, with dedicated communications, training materials, and videos as applicable. |
As applicable |