About Forge¶
Learn about Forge's origins, evolution, and the core principles that guide platform development.
📖 History¶
Forge is the evolution of our platform strategy, born from lessons learned in the CIAM project. What started as an RFP search for integration platforms has grown into a comprehensive developer platform addressing systemic pain points.
Timeline¶
🎯 Platform Principles¶
Decision-making frameworks that guide Forge development:
| Principle | Focus |
|---|---|
| Speed-to-Value | Reduce time-to-first-deployment for every feature |
| Proven Patterns | Secure, tested defaults over flexibility |
| Leverage Over Invention | Build on existing solutions instead of custom code |
| Team Autonomy | Eliminate dependencies on central teams |
| Zero-Trust Architecture | Secure by default without additional configuration |
| Local-First Orchestration | Mirror production architecture through local tooling |
| Platform as a Product | Manage with roadmap, lifecycle, and deprecation policies |
💬 Getting Support¶
Need help with Forge? Here's how to reach the Platform Team:
| Channel | Use For |
|---|---|
| 💬 Teams Channel | Questions, troubleshooting, discussions |
| 🎫 GitHub Issues | Feature requests, bug reports, enhancements |
Before Reaching Out¶
- Check the documentation — Many common questions are answered in the Guides
- Search existing issues — Your question may already be tracked in the backlog
- Include context — Share error messages, Forge version, and relevant configuration