Unnamed Portal
Unnamed Portal

The problem
We needed a community management platform — and nothing on the market fit.
Every tool we tried fell into one of two traps: either it was a bloated enterprise suite that needed a six-month implementation, or it was a lightweight widget that broke down the moment you needed role-based access, real-time dashboards, or event coordination. Our communities were growing, and managing them across Slack, Notion, spreadsheets, and three different event tools was unsustainable.
So we decided to build our own.

Our approach
We treated this like a client engagement with ourselves as the product owner. A two-engineer team ran two-week cycles with a dedicated discovery week up front. The brief was intentionally tight: ship a platform that handles member profiles, community dashboards, and event coordination — with an identity layer robust enough to support multi-tenant workspaces down the road.
The architecture leans on AWS-native services end to end. Cognito handles authentication and user pools. DynamoDB backs the data layer — chosen for its single-digit-millisecond reads and zero-ops scaling model. The frontend is a Next.js application deployed on AWS Amplify, with server components handling the heavy data fetching and client-side interactivity kept surgical.
The real engineering challenge was real-time state synchronization. When a community admin updates an event or modifies member permissions, every connected client needs to reflect that change immediately. We built a lightweight WebSocket layer on top of API Gateway that fans out updates to subscribed clients without polling.

The outcome
- Production launch in 12 weeks from first commit
- Zero downtime in the first 120 days of operation
- Sub-200ms p95 latency on all dashboard queries
- The platform now manages multiple active communities with thousands of members

"Building our own tool forced us to confront every assumption we'd been making about community platforms. The result is sharper than anything we could have specced for a client."
— Engineering Lead, Unnamed Corp
Next case study
Olympia Apparel →