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 9th, 2026
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 Communication & Resources – When and how you can expect to be informed about upcoming changes.
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 Family |
Standard Window |
Expected Impact |
|---|---|---|
| Compliance & Fuel Analytics | Every other Wednesday, 4:00 AM - 6:00 AM (EST) | Users will not be able to access Titan Cloud Edge software during maintenance; however, ATG data collection and inventory readings will continue. |
Supply & Logistics |
Every other Wednesday, 4:00 AM - 6:00 AM (EST) |
Inventory readings will be unavailable in the Titan Logistics platform during this time. |
| Maintenance & EV | Scheduled as needed (non-routine) | Users will not be able to access the Titan Maintenance platform during this time. |
Data & Connectivity |
Scheduled as needed (non-routine) |
Data ingest for all or some Titan Cloud products may be temporarily disrupted during maintenance windows.
Whenever possible, Data & Connectivity releases will be scheduled to deploy within the standard window for the impacted platform(s). |
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 Communication & Resources
This section outlines how Titan Cloud communicates release details and provides supporting resources to ensure customers are informed and prepared.
Routine Communication
Product Family |
Pre-Release Communication |
Post-Release Communication |
|---|---|---|
| Compliance & Fuel Analytics |
Thursday before release day:
An in-app banner notifies users of upcoming downtime. |
Release Notes are updated in the Help Center if needed and a confirmation is shared in the “Product Announcements” section of the in-app Resource Center in Titan Cloud Edge. |
Supply & Logistics |
Thursday before release day:
|
Release Notes are updated in the Help Center if needed. |
| Maintenance & EV |
Two weeks before release day:
|
Release Notes are updated in the Help Center if needed. |
Non-Routine Communication
Non-routine deployments including but not limited to new feature launches, large scale enhancements, and Data & Connectivity releases will be communicated using a combination of email and in-app tools as applicable. Specialized resources including training, Help Center documentation, and in-app walkthroughs will be provided when appropriate.