LAB-AS-CODE
Version, review, and ship labs as code
Lab-as-code means building hands-on labs the way you build software: version controlled, branched, and reviewed. Every Instruqt lab is version controlled from creation. Branch, tag, and edit in the product, or connect your own GitHub repository and manage lab content alongside your product code.
Trusted by the teams building the future of software
.png)
HOW IT WORKS
Hands-on labs as code, from the first commit
History, branches, and safe editing are on by default, with no repository to configure. Your own Git workflow connects when you want it.
01 · BUILD
Branch and edit without breaking production
Every lab is version controlled from creation, with no GitHub setup and no separate tools. Create a branch to test a new sandbox resource or restructure a chapter. Edit mode separates viewing from editing, so the version learners use stays stable while you work. Save any lab as a template, and package sandbox resources, instructions, and tabs as Modules to reuse across your library.
Version control on every lab, no integration required
Branches that run and share as complete labs
Lab templates and reusable Modules for repeatable builds
See how labs are built
02 · CONNECT
Manage labs in your own GitHub repository
Connect a lab directly to your team's repository, monorepos included, and use native Git for version history and conflict resolution, so labs follow the same GitOps flow as the rest of your code. Sandbox definitions are declared in HCL, so they get the same review your infrastructure code does.
Optional GitHub integration with monorepo support
Native Git history and conflict resolution
HCL sandbox definitions reviewable like infrastructure code
03 · VALIDATE
Validate before a learner ever opens it
The validate command checks a lab's definition, resource references, and task mappings before the lab runs. Logs carry more detail and real controls to filter and slice when something fails. Inline comments on any resource record why it exists, and a usage label shows every place it's referenced across the lab.
Validate checks definitions, references, and task mappings
Logs you can filter and slice
Inline comments and usage tracking on every resource
THE DIFFERENCE
The Instruqt Difference Version control that teams can actually review.
Instruqt does not add another place to manage lab content. It brings lab under the same control as your code.
THE TRADITIONAL APPROACH
One author owns the lab and edits it live; nobody else understands the setup.
Testing a change means changing the lab learners are using today.
Setup logic is hidden in scripts only the original author can read.
Broken references are found by the first learner who hits them.
WITH INSTRUQT LAB-AS-CODE
Every lab carries its history from creation, with comments on resources explaining the setup.
Branches isolate each change as a complete, playable lab while production stays stable.
Sandboxes are declared in HCL and reviewed like infrastructure code.
Validate checks definitions, resource references, and task mappings before the lab runs.
Ready to get started? Book a demo with our team
Get a Demo
USE CASES
See where Lab-as-Code creates value
Teams use versioned labs to ship demos, training and developer content faster — without stepping on each other.
.svg)
Standardize the demo, customize the deal
Every SE starts from the same proven lab and branches it per prospect without touching the original. When the product changes, the update lands once, in one place.
Branch a lab per deal while the team's demo stays untouched
Share a prospect-specific branch as a complete, playable lab
Maintain one demo lab instead of scattered copies
Learn more
Keep course content current as the product changes
Version control turns curriculum updates into tracked changes instead of rewrites. Templates and Modules keep new courses consistent with the ones you already run.
Version history shows what changed in a lesson, and when
Version tags help track content as the subject it teaches changes
Resource comments document why each setup step exists
Learn more
Open lab authoring to the whole team
Technical and non-technical contributors work on the same lab at the same time without overwriting each other. Engineers stay in GitHub; everyone else stays in the product.
Connect labs to your own GitHub repository, monorepos included
Edit mode keeps the published lab stable during changes
Branches give each contributor a complete working version
Learn more
Ship POC labs that work the first time
Validate the lab before a prospect opens it, and trace failures quickly if one appears. A broken reference gets caught in review, not in the meeting.
Run validate to catch missing references and mismapped tasks
Use filterable logs when a sandbox fails mid-POC
Predictable, slug-based lab IDs instead of random strings
Learn more
TESTIMONIALS
What our clients say
Teams shipping hands-on content every week — and the impact it has on their product and their customers.
Keith Manville
Customer Engineer, Google Cloud Security
Read story →
“The things that stood out about Instruqt that were very attractive to us was its fundamental flexibility.”
Dean Andrews
Head of Developer Relations, InterSystems
“In less than a year on Instruqt we’ve gone from one workshop to over 25 labs, with the same small team of sales engineers. Instead of ten workshops at 25 attendees each, we run one and reach 400 customers at a time.”
Brandi Coleman
Director, Americas Enterprise Sales Engineering, BMC
Nigel Douglas
Head of DevRel, Cloudsmith
Nick Drost
GVP Solutions Architecture, Elastic
Tim Koopmans
ScyllaDB
Alex Rosenkranz
Engineering Manager, Datadog
Joe Titra
Global Head of Technical Enablement, Wiz
Keith Manville
Customer Engineer, Google Cloud Security
Read story →
“The things that stood out about Instruqt that were very attractive to us was its fundamental flexibility.”
Dean Andrews
Head of Developer Relations, InterSystems
Jeff Price
Field CTO, SUSE North America
“In less than a year on Instruqt we’ve gone from one workshop to over 25 labs, with the same small team of sales engineers. Instead of ten workshops at 25 attendees each, we run one and reach 400 customers at a time.”
Brandi Coleman
Director, Americas Enterprise Sales Engineering, BMC
Nigel Douglas
Head of DevRel, Cloudsmith
Nick Drost
GVP Solutions Architecture, Elastic
Tim Koopmans
ScyllaDB
Alex Rosenkranz
Engineering Manager, Datadog
Joe Titra
Global Head of Technical Enablement, Wiz
FAQ
Frequently asked questions
Do I need GitHub to get version control?
No. Every lab is version controlled from the moment it's created, with no GitHub setup and no separate tools. The GitHub integration is optional, for teams that want lab content in their own repository, and it supports monorepos. Without a connected repository you still get branches, version tags, edit mode, and inline comments on resources. Connecting one later is an option, not a migration.
Will my existing V1 tracks break in 2.0?
No. Existing labs are unaffected, legacy and 2.0 run side by side during the transition, and there is no forced migration. Legacy is supported until 27 September 2027. Migration tooling launches with GA on 29 September 2026.
How can teams test changes before publishing a lab?
Create a branch. It is a complete working version of the lab that can be played and shared on its own, so you can run the change end to end while the version learners use stays untouched. Run validate to check the lab's definition, resource references, and task mappings before it runs. Edit mode keeps viewing and editing separate throughout, and version tags mark what is current.