The Goalixa Journey
The complete story of building Goalixa - from idea to production, through challenges and lessons learned.
This is the narrative story of how Goalixa evolved from a concept to a production-ready productivity platform. Each chapter represents a phase of the journey, with personal reflections and technical details.
The Beginning
Why I Started Goalixa
The journey began with a simple problem: I needed a better way to manage my goals, projects, and daily tasks. Existing tools didn't quite fit the way I think about productivity - I wanted something that could bridge the gap between high-level goals and daily action items.
Lessons Learned
- Start with a clear problem statement
- Build what you would use yourself
- Keep the vision simple but ambitious
Learning in Wartime
Building Under Crisis Conditions
Building a startup is hard. Building a startup during wartime in Iran with severe internet restrictions is exponentially harder. In March 2026, I found myself in exactly this situation - intermittent internet access, VPN services as the only connection method, and servers located outside the country.
Despite these challenges, I used the downtime to study deeply and plan the infrastructure upgrades that Goalixa would need.
Lessons Learned
- Adaptability is everything when circumstances change
- Use downtime productively - study and plan
- Infrastructure resilience matters more than I thought
- Remote access patterns become critical in crisis
First Deployments & Early Architecture
From Monolith to Microservices
The early architecture of Goalixa was straightforward: three main services (app, auth, landing), each with its own subdomain and frontend. While this worked initially, it created problems with complex redirect flows, cookie consistency, fragmented UI ownership, and high blast radius during incidents.
Lessons Learned
- Microservices require unified frontend experience
- API Gateway is essential for true microservices
- Fragmented UIs slow down product iteration
- Single points of failure create operational nightmares
The PWA Transformation
Unifying the Frontend Experience
The biggest milestone in Goalixa's early life was the successful migration to a Progressive Web App (PWA) architecture combined with an API Gateway. This transformed Goalixa from multiple fragmented UIs into a single, cohesive user experience.
Lessons Learned
- One UI is better than many
- BFF pattern keeps both frontend and backend clean
- API Gateway enables true service independence
- Migration is worth the effort
Key Milestones
Initial Concept
Early 2026
PWA + Gateway Launch
February 20, 2026
GitOps with ArgoCD
February 2026
Staging Environment
March 2026 - In Progress
Production Launch
Planned
Technology Choices
Frontend
Progressive Web App (PWA)
API Gateway
Nginx-based gateway
Backend
Python (Flask/FastAPI) microservices
Orchestration
Kubernetes
GitOps
ArgoCD + Harbor
Monitoring
Prometheus, Grafana, Alertmanager
Personal Growth
Building Goalixa has been an incredible learning journey. From understanding microservices architecture to implementing GitOps, from handling production incidents to building during wartime - every challenge has taught valuable lessons about engineering, resilience, and product development.
The most important lesson: Great engineering is not just about writing code - it's about building systems that stay fast, reliable, and understandable under real conditions.