Version Schedule & End-of-Life

Overview

This article describes the Journyx JX product lifecycle, including release cadence, support tiers, and end-of-life timelines. Understanding the lifecycle policy helps customers plan upgrades proactively and ensures their Journyx environment remains secure, supported, and fully functional.

Why Upgrades Matter

Journyx JX is a cloud-delivered SaaS platform with tightly integrated mobile applications. In this delivery model, the entire ecosystem — from backend services and APIs to web interfaces and mobile clients — is continuously evolving. Staying current is not simply a best practice; it is essential to maintaining a reliable, secure, and compatible environment.

Specifically, upgrades ensure:

Security Posture Every Journyx JX release includes security updates. Older versions that have reached end-of-life only receive critical security patches as needed, potentially leaving your environment exposed to known vulnerabilities. In cloud and mobile contexts, where applications are externally accessible and user data is transmitted regularly, the risk of running unpatched software is significantly elevated.

API and Integration Compatibility Cloud platforms and third-party integrations evolve over time. Journyx JX versions nearing or past end-of-life may encounter breaking changes with upstream services, operating system dependencies, or browser and mobile OS updates that cannot be supported in older releases.

Mobile Application Compatibility Mobile operating system vendors — Apple iOS and Google Android — release major updates annually, and app store policies can require application updates to maintain availability. JX mobile clients are tested and validated against supported JX server versions. Running an end-of-life server version may result in degraded or unsupported mobile client behavior.

Access to New Features and Performance Improvements Each new feature release includes enhancements developed in response to customer feedback, regulatory requirements, and platform improvements. Customers on older versions may be unable to access new capabilities that are central to Journyx's continued product roadmap.

We Understand That Upgrades Require Planning

Journyx recognizes that upgrading a business-critical time tracking and project account system is not a trivial undertaking. Upgrades require coordination across IT, finance, and end-user teams, and must be scheduled around operational demands. This lifecycle policy is designed to provide customers with meaningful advance notice and a generous support window — giving your team the time needed to plan, test, and execute upgrades without urgency or disruption.

Customers are encouraged to begin evaluating new releases as soon as they are available and to target upgrades well within the Standard Support window.

Release Cadence

Journyx JX follows a predictable, twice-yearly release schedule:

All releases — both feature and maintenance — include security updates.

Support Tiers

Each Journyx JX feature release version progresses through the following support tiers, measured from its original release date:

Standard Support

Duration: Release date through Release date + 2 years

During the Standard Support period, a JX version receives:

• All security updates
• Bug fixes via fully regression-tested maintenance releases
• Full technical support from the Journyx Support team
• Updates to new maintenance releases as they become available

Standard Support represents the recommended operational window for all Journyx JX deployments.

Extended Support

Duration: Release date + 2 years through Release date + 3 years

Extended Support is available for customers who require additional time to complete upgrade planning after Standard Support ends. During this period:

• Critical security updates are provided
• Technical support remains available
• Maintenance releases are no longer issued for anything except critical security issues
• Consultative support for Sev 2+ issues (advice, workarounds)

Customers on Extended Support should treat this period as a firm deadline window and actively plan their upgrade to a currently supported version.

End-of-Life (End of Extended Support)

Milestone: Release date + 3 years

At the End-of-Life milestone, the JX version is fully retired. After this date, paid support is available as follows:

• Patches for severe issues with no regression testing may be available (hourly rates apply)
• Consultative support as outlined above is available (hourly rates may apply)

NOTE: Continued use of an end-of-life version is at the customer's own risk and is strongly discouraged.

End of Paid Support

Milestone: Release date + 4 years

Paid support contracts covering end-of-life versions expire no later than 4 years after the original release date. After this milestone, no support coverage — paid or otherwise — is available for the retired version.

Lifecycle Timeline Summary

The table below illustrates the lifecycle milestones for a hypothetical JX version released on a given date - in this case the release for the first half of 2025. Substitute your version's actual release date to determine your specific milestones.

Recommendations

• Check your current JX version and identify its release date to determine which support tier applies.
• Plan upgrades within the Standard Support window to avoid operating under Extended Support constraints.
• Do not operate end-of-life versions in production environments, particularly those exposed to the internet or integrated with cloud services and mobile clients.
• Contact Journyx Support if you are unsure of your version's lifecycle status or need assistance planning an upgrade path.

Related Articles

• Journyx JX & PX Upgrade Resources

Support Contact

For lifecycle questions, upgrade planning assistance, or to review your support agreement, contact the Journyx Support team at support@journyx.com.

This policy is subject to change. Journyx will provide reasonable advance notice of any modifications to the lifecycle policy. Always refer to the most current version of this article for authoritative lifecycle information.