Bob Left. Now Nobody Can Build That Dev VM.
Your VM setup knowledge walks out the door every time someone leaves. Dev and test environments become mysteries.
Common knowledge loss scenarios
Teams everywhere face these documentation challenges
Tech Startup
Founder left
Core systems undocumented
Healthcare
20-year veteran retired
VM setup knowledge gone
Financial
Production delay
Couldn't recreate test env
Manufacturing
3-month delay
Lost server configurations
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 preserve your VM knowledge?
Transform tribal knowledge into permanent assets
Where VM knowledge disappears
Critical expertise trapped in people's heads
Undocumented Steps
"Oh, you also need to disable that service..."
→ Builds fail mysteriously
Tribal Rituals
Everyone knows to reboot twice, but why?
→ Cargo cult infrastructure
Setup Sequences
Must install X before Y, configure Z after
→ Wrong order breaks everything
Hidden Dependencies
That registry key nobody documented
→ Hours of debugging
Personal Scripts
PowerShell scripts on someone's desktop
→ Lost when they leave
Version Mysteries
Why exactly .NET 4.5.2, not 4.6?
→ Incompatibility surprises
Turn setup knowledge into reusable patterns
VM configurations become inheritable templates
Knowledge Walks Away
- ✗Expertise in people's heads
- ✗Incomplete documentation
- ✗Personal scripts scattered
- ✗Tribal knowledge rules
- ✗New hires struggle months
- ✗Constant productivity loss
Knowledge Lives Forever
- Expertise encoded in genes
- Self-documenting YAML
- Scripts part of genes
- Explicit configurations
- New hires productive day 1
- Knowledge preserved
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
# Deploy a test environment in 5 minutes
$catlet = @"
name: test-env-01
parent: dbosoft/ubuntu-22.04/latest
# Add your organization's configurations
fodder:
- source: gene:myorg/test-setup
"@
# Deploy with one command
$catlet | New-Catlet | Start-Catlet
# Result: Ubuntu with your test tools ready
# Time saved: 40 minutes per deployment
How eryph preserves knowledge
Transform your expertise into code
Preserve Your VM Knowledge
Transform dev/test setup knowledge into version-controlled, inheritable patterns. No per-VM licensing.