When NOT to Use FORGE
FORGE fails for dynamic services and live infrastructure.
5 Anti-Patterns
1. Live Services
❌ Real-time data feeds ❌ Monitoring dashboards ❌ Live chat support Why: Requires ongoing infrastructure
2. Managed Infrastructure
❌ Hosting services ❌ Database management ❌ CDN/edge computing Why: Service-based, not product-based
3. Continuous Updates Required
❌ Security patches ❌ Compliance tracking (e.g., GDPR changes) ❌ API integrations (breaking changes) Why: Can't guarantee "works forever"
4. High-Touch Onboarding
❌ Custom implementation per client ❌ Consulting-heavy deployments ❌ Ongoing training required Why: Human dependency doesn't scale
5. Network Effects Critical
❌ Marketplaces ❌ Social platforms ❌ Community-driven features Why: Value comes from other users, not artifact itself
If it requires ongoing service, don't FORGE it—SaaS it. 🪶