ELTS From TYPO3 V13 Onwards: What’s Changing

Which of your TYPO3 installations are actually covered by ELTS? From January 1, 2028, ELTS for TYPO3 v13 will be delivered only via download and Composer, secured by one token per instance. Frank Nägler explains what’s changing, why GitHub access is ending, and how to prepare your projects.
Key points at a glance
- From January 1, 2028, ELTS v13 will only be available via download and Composer, without GitHub access.
- One token per instance instead of per user: each ELTS subscription is clearly assigned to a single installation.
- This is our response to the use of individual subscriptions across multiple installations, which we informed you about in August.
- Tokens run for the duration of the subscription (1–3 years) and are renewed with every prolongation.
- Nothing changes for ELTS versions prior to v13.
With TYPO3 v13, we are changing how Extended Long Term Support (ELTS) is delivered: from January 1, 2028, ELTS packages will only be available via download and Composer, secured by per-instance tokens. The previous access to the GitHub repositories will be discontinued. Nothing changes for ELTS versions prior to v13.
In August 2026, we informed ELTS customers that some ELTS subscriptions were being used for multiple installations, contrary to the terms of use. The new token model is our response: we want to make ELTS simpler, clearer and more closely aligned with actual usage. One token per project makes it transparent which installation is covered, for you and for us. In this article, we explain exactly what is changing and what you should prepare for.
Delivery via download and Composer only
From ELTS v13 onwards, you can obtain the secured TYPO3 versions in two ways: as a download package in ZIP or TAR format, or via Composer. We will no longer grant access to the GitHub repositories for v13.
This means direct repository access is discontinued entirely. For most projects, little will change in day-to-day work, as Composer is already the recommended and most commonly used way to install TYPO3 and keep it up to date. If you have previously pulled code directly from the repository or built your own forks on top of it, you should adapt your deployment process in good time.
Instance tokens instead of user tokens
Until now, access was tied to individual users. From v13 onwards, we will generate one token per instance, meaning per secured project.
This has several advantages:
- Clear assignment: Each token belongs to exactly one installation. You can see at a glance which projects are covered.
- Independent of individuals: If a developer changes team or agency, access to the project remains in place.
- Clean deployment: The token belongs in the project’s Composer configuration, not in personal accounts.
If you maintain several TYPO3 installations, you will receive a separate token for each instance.
The change is also intended to prevent misuse. Because each token is clearly assigned to one project and one customer, we will be able to block tokens specifically by project or customer and permanently exclude them in cases of misuse. This protects all customers who use their ELTS subscription fairly.
Duration and renewal
A token’s validity is tied to your subscription: depending on the term you have booked, it is valid for one, two or three years. When the term expires, access via that token also ends.
When you renew, we will issue a new token. You should therefore plan to update the Composer configuration of your projects after each renewal. This ensures that updates and security fixes can be applied without interruption.
Timeline
ELTS for TYPO3 v13 starts on January 1, 2028. From this date, the new rules apply: delivery via download or Composer, instance tokens and a term in line with your subscription. TYPO3 v13 ELTS can be purchased from October 1, 2027.
Nothing changes for ELTS versions prior to v13: the existing system continues to apply unchanged.
What you should do now
There is plenty of time before the launch. These steps will get your projects ready:
- Review your deployment: Switch projects that still work directly from the GitHub repository to Composer.
- Identify your instances: Determine which installations need ELTS v13. A separate token is generated for each instance via My TYPO3.
- Plan the term: Choose a term of 1 to 3 years and note the end date.
- Schedule renewals: Build the token change at renewal into your maintenance processes.
If you have questions about your specific setup, our team will be happy to help by email at support@typo3.com.