Which Windows Template Again?
The one with SP1? With .NET 4.5? Without IE 11? Your template library has become an unmaintainable nightmare.
Template sprawl is everywhere
Every IT team drowns in template versions
Enterprise IT
127 templates
Nobody knows what's in them
Software Dev
New template weekly
Old ones never deleted
MSP Provider
Template per client
Maintenance nightmare
Education
Semester chaos
Templates for each class
Enterprise IT
127 templates
Nobody knows what's in them
Software Dev
New template weekly
Old ones never deleted
The Pattern
Every organization hits the same wall: Manual VM provisioning doesn't scale. What starts as "just a few VMs" becomes a full-time job, blocking your team from actual work.
Ready to end template chaos?
Transform your VM templates into versionable code
Why template management fails
Monolithic templates can't handle variation elegantly
Combinatorial Explosion
Need Windows + SQL 2019? 2022? With IIS? Without?
→ Dozens of similar templates
Update Nightmares
Security patch? Update 47 templates manually
→ Some always missed
Documentation Black Hole
What's in 'Win2019_Final_v3_FIXED'?
→ Deploy wrong template
No Version History
Who changed what? When? Why?
→ Can't rollback mistakes
Naming Chaos
Everyone's naming convention differs
→ Can't find right template
Storage Explosion
Each template is 30-100GB
→ Terabytes of redundancy
Combinatorial Explosion
Need Windows + SQL 2019? 2022? With IIS? Without?
→ Dozens of similar templates
VM-as-Code enables version control
Transform binary templates into versionable YAML configurations
Binary Template Hell
- ✗50GB binary VM templates
- ✗Can't diff or version
- ✗Manual GUI-based updates
- ✗No change tracking possible
- ✗Documentation separate from template
- ✗Massive storage duplication
Infrastructure as Code
- Small YAML configuration files
- Store in Git like any code
- Declarative specifications
- Full commit history & diffs
- Config is the documentation
- Inherit from base genes
Binary Template Hell
- ✗50GB binary VM templates
- ✗Can't diff or version
- ✗Manual GUI-based updates
- ✗No change tracking possible
- ✗Documentation separate from template
- ✗Massive storage duplication
Infrastructure as Code
- Small YAML configuration files
- Store in Git like any code
- Declarative specifications
- Full commit history & diffs
- Config is the documentation
- Inherit from base genes
How the gene system works
1. Start with a gene
Choose a proven template from the genepool or create your own
2. Add what's different
Inherit base configs, customize only what you need
3. Deploy in minutes
Your improvements become new genes others can inherit
Real example: Deploy an Ubuntu web server from YAML
# Deploy Ubuntu web server from YAML:
# Perfect for dev, test, and staging workloads
$webServer = @"
name: web-server-01
parent: dbosoft/ubuntu-2204/latest
# Configure web server stack
fodder:
- source: gene:myorg/ubuntu-nginx-base
variables:
- name: site_name
value: myapp.local
"@
# Deploy it
New-Catlet -Config $webServer | Start-Catlet
# Done! Ubuntu web server ready in minutes.
Template management transformed
From template sprawl to elegant version control
Ready to End Template Chaos?
Transform your template sprawl into elegant, versioned genes.