Inspiration
Our company relied on EPop, a legacy desktop-only messaging app, to communicate internally. It was limited in features, hard to maintain, and unavailable on mobile. We wanted a modern, self-hosted collaboration platform that fits how our teams work across multiple sites.
What it does
iPop is an internal collaboration platform for PT Santos Jaya Abadi (SJA) that replaces EPop. It offers real-time messaging and team collaboration on web and Android, integrated with our existing employee data.
How we built it
- Backend & UI: .NET 10 and Blazor Server, styled with Tailwind CSS
- Data: PostgreSQL and Redis
- Infrastructure: self-hosted on RKE2 (Kubernetes) running on Nutanix HCI, with Synology NAS storage at both sites
- Security: Argon2id password hashing, and employee data synced from our legacy HR system
- Development was assisted by AI tools.
Challenges we ran into
- Replacing a legacy system while keeping employee data and daily operations intact
- Designing a production-grade, self-hosted infrastructure with a very small team
- Keeping the scope realistic: delivering core features first, then expanding
Accomplishments that we're proud of
- Beta testing started on 1 October 2026, and the pilot has grown to about 175 active users
- Android app released alongside the web version
- A fully self-hosted platform, so company data stays in-house
What we learned
- Early user feedback matters more than feature count
- Good architecture and documentation reduce risk, especially for a small team
- AI-assisted development speeds up delivery, but design and review still need human judgment
What's next for iPop
- iOS app
- High-availability hardening (Redis, database connection pooling)
- Company-wide go-live across all SJA sites in April 2027
Built With
- .net
- android
- blazor
- c#
- kubernetes
- nutanix
- postgresql
- redis
- rke2
- tailwindcss