WHAT WAS DONE: Added complete RTO (Rent-to-Own) case study and financial analysis to infrastructure manifest, documenting Michael's ownership philosophy and actual infrastructure costs ACTUAL INFRASTRUCTURE COSTS DOCUMENTED: - TX1 Dallas: $80/month (colocation, owned hardware) - NC1 Charlotte: $80/month (colocation, owned hardware) - VPS tier: $37/month (Command Center, Ghost, Billing, Panel) - Other: $20/month (IPs, domain) - **Total current: $217/month** - **After Dev VPS: $227/month** OWNERSHIP STATUS: - TX1 & NC1: RTO completed June 2024 - Owned outright for 22 months (as of March 2026) - Hardware value: $3,300-4,550 (realistic $3,800-4,000) ROI ANALYSIS DOCUMENTED: - Monthly savings: $298/month (rental equivalent $458 - actual cost $160) - 22 months savings: $6,556 - Hardware value: $4,000 - **Total equity position: $10,556** - Break-even: Month 14 (already profitable) LONG-TERM PROJECTION: - Year 3: $14,056 equity - Year 5: $16,804 equity - Annual savings: $3,576/year ongoing RENTAL COMPARISON: - If renting for 22 months: $10,076 spent, $0 owned - Actual position: $3,520 spent, $4,000 owned, $6,556 saved - **Net advantage: $10,556** RTO PHILOSOPHY DOCUMENTED: "Always keeping an eye out for RTO deals with Breeze" - Michael's strategy WHY RTO IS PREFERRED: ✅ Build equity while paying ✅ Massive savings after ownership ✅ Hardware asset remains ✅ Insulation from price increases ✅ Can resell, repurpose, or continue using DECISION MATRIX ADDED: - When to choose RTO (long-term, known workload) - When to choose Rental (short-term, flexibility) - When to choose Purchase (cash flow allows) FUTURE RTO MONITORING CRITERIA: - Breezehost promotions/special offers - End-of-generation hardware deals - Used/refurbished servers (lower payments) - Bundle deals (multiple servers) EVALUATION CRITERIA DOCUMENTED: 1. Monthly payment vs rental equivalent 2. Ownership timeline (24 months preferred max) 3. Hardware specs vs needs 4. Post-ownership colocation cost 5. Total cost of ownership vs 3-year rental WHY THIS MATTERS: This case study proves the financial wisdom of infrastructure ownership. $10,556 better off after 22 months vs renting. Provides framework for future expansion decisions and demonstrates "for children not yet born" philosophy - building assets, not paying expenses. Future Chroniclers now have complete financial analysis when evaluating RTO opportunities or expansion decisions. FILE: docs/core/infrastructure-manifest.md SECTION: 2.6 RTO Philosophy & Financial Analysis Signed-off-by: The Versionist (Chronicler #49) <claude@firefrostgaming.com>
🔥❄️ Firefrost Gaming — Operations Manual
Document ID: FFG-ROOT-001
Version: 2.0
Last Updated: February 12, 2026
Status: 🟢 CURRENT
What This Is
The complete operational repository for Firefrost Gaming — a subscription-based Minecraft server network built on the philosophy of Fire + Frost = Where Passion Meets Precision.
This repository contains infrastructure documentation, deployment guides, planning documents, branding assets, consultant archives, and the relationship context that makes Firefrost more than just servers.
Current Infrastructure
6 Servers — 2 dedicated (Dallas, Charlotte) + 4 VPS (Dallas, Charlotte, Chicago x2)
12 Game Servers — 6 on TX1 (Dallas), 6 on NC1 (Charlotte)
8 Management Services — Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js (Subscribers), Wiki.js (Staff)
Repository Structure
├── docs/core/ — Critical living documents (scope, manifest, tasks)
├── docs/relationship/ — Partnership context, consultants, legacy
├── docs/deployment/ — Service deployment guides
├── docs/planning/ — Strategy, design, roadmap, ideas backlog
├── docs/reference/ — Technical reference, architecture decisions
├── docs/external/ — Provider communications, friend assistance
├── docs/sandbox/ — Brainstorming sessions (Gemini, Claude)
├── docs/archive/ — Historical session logs and completed plans
├── automation/ — Deployment automation system
├── branding/ — Logos, backgrounds, visual assets
├── photos/ — Consultant photo archive (249 photos by year)
└── web/ — Nginx configurations
Key Documents
Start here: SESSION-HANDOFF-PROTOCOL.md → DOCUMENT-INDEX.md
For current server inventory, see docs/core/infrastructure-manifest.md (FFG-CORE-002).
For project scope and roadmap, see docs/core/project-scope.md (FFG-CORE-001).
The Team
- Michael "Frostystyle" Krause — Owner/Operator, Technical Lead (The Wizard)
- Meg "Gingerfury" — Community Manager (The Emissary)
- The Five Consultants — Jack, Oscar, Jasmine, Butter, Noir (They're family, not pets)
Document Standards
All documents follow FFG-STD-001 — the Firefrost Revision Control Standard. See docs/core/revision-control-standard.md.
Maintained By: The Wizard & The Chronicler
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-08 | Michael + Claude | Initial | Basic Phase 0 readme |
| 2.0 | 2026-02-12 | The Chronicler | Rewrite | Complete rewrite reflecting current state (8 services, 6 servers, 12 game servers). Updated repo structure. Applied FFG-STD-001. |