Thinkbox Deadline 10, the long-standing render-farm management software from AWS Thinkbox, will enter maintenance mode on 7 November 2025. In this state, the software remains operational, but AWS will limit future development to security updates and critical fixes. All feature development and innovation are being redirected toward Deadline Cloud.
The AWS product page reinforces the transition, stating:
“Notice: On November 7, 2025, AWS Thinkbox Deadline 10 will enter maintenance mode. We recommend exploring AWS Deadline Cloud for render management.”
AWS specifies in its documentation that existing installations will continue to work “exactly as they do today,” assuring studios that their current workflows, scripts, and configurations remain unaffected. The software will continue to be available for download from the Thinkbox product page, although new features will not be added after the transition.
What “maintenance mode” means for studios
According to the official FAQ, studios can keep using Deadline 10 as they do now, including adding render nodes and managing render tasks through AWS Portal, the Spot Event Plugin, and the Render Farm Deployment Kit (RFDK). The documentation confirms that “your existing Deadline 10 implementation, including all your current workflows, scripts, and configurations, will continue to function exactly as they do today.” AWS also notes that its Usage-Based Licensing (UBL) remains available for Deadline 10 customers through Deadline Cloud UBL.
Why this matters for post-production and VFX pipelines
For pipeline engineers, TDs, render supervisors, and system administrators, the change signals the end of active feature development for Deadline 10. While the software continues to operate, AWS will now concentrate its efforts on Deadline Cloud. This means that new integrations, optimisations, and performance enhancements will appear only in the cloud-based version.
Migration considerations
Studios managing in-house render-farms or hybrid setups should begin testing Deadline Cloud alongside their existing Deadline 10 installation to compare workflows, performance, and cost implications. Migration will likely require reviewing custom scripts, integrations, and plugins to ensure compatibility with the newer system.
Since Deadline 10’s UBL system is now linked to Deadline Cloud UBL, pipeline engineers will need to verify how their licence usage transitions under the new framework. Although no immediate migration deadline has been announced, relying indefinitely on a tool in maintenance mode could increase operational risk if future integrations or dependencies demand newer features. Planning a gradual migration, complete with staff training and pipeline validation, will make the transition smoother.
What’s not changing (for now)
Deadline 10 is not being discontinued YET. It will remain available and fully functional after entering maintenance mode, with ongoing support for security patches and critical updates. AWS has not announced any end-of-life date beyond the shift to maintenance mode.
Teams are advised to begin testing Deadline Cloud or alternatives early, document their workflows, and ensure that custom automation scripts port correctly. As with any production software change, test thoroughly before adopting new infrastructure in live projects.
