Launch Timeline
Three dates matter. Early Access is open now, general availability lands in September 2026, and the current platform is supported until September 2027. Everything below sets out what to expect at each stage.
| Date | Stage | What it means |
|---|---|---|
| 3 August 2026 | Early Access | 2.0 is on by default. Explore, test, and start building |
| 29 September 2026 | General availability | Full launch at HANDS-ON. 2.0 becomes the default platform |
| 27 September 2027 | Legacy sunset | End of support for the current platform |
Early Access, from 3 August 2026
Section titled “Early Access, from 3 August 2026”Early Access is a beta. It is open to build in, and it is not a finished product.
- 2.0 is enabled by default
- Your current labs keep working exactly as they do today. Nothing about them changes
- Current and 2.0 content run side by side. There is no switchover moment
- Not every feature is here yet. See what’s new in 2.0 for what is live at this stage and what follows
- Migration tooling is not fully available yet
- This is the stage where feedback shapes what ships next, so tell us what is missing
General availability, 29 September 2026
Section titled “General availability, 29 September 2026”Announced live at HANDS-ON. From this date 2.0 is the default platform.
- 2.0 becomes primary, though moving your existing content will take time, and both platforms continue to run alongside each other while it does
- 2.0 reaches close to feature parity with the current platform, with a small number of named exceptions. See what’s new in 2.0 for exactly which
- Modules and the module registry arrive
- The feature set keeps growing after this date. GA is not a finish line
Legacy sunset, 27 September 2027
Section titled “Legacy sunset, 27 September 2027”The current platform is supported until 27 September 2027.
- You migrate at your own pace. There is no forced date before then
- The timeline you have already been given stands
- If that date creates a problem for your program, raise it with your Instruqt contact early rather than late
What to expect while both platforms run
Section titled “What to expect while both platforms run”- Nothing in your existing content is touched, at any stage
- You can build in 2.0 and keep running current labs at the same time
- What is possible inside a 2.0 lab differs from a current lab, but there is no hard wall between them
- New development goes into 2.0. The current platform stays stable and supported until sunset
- Migration is worth treating as a chance to restructure rather than a like for like port. Finding your common patterns and building them once as modules is where the benefit is