Inspiration
Community management is broken. Today, managers are drowning in noise—thousands of threads, endless comments, and disconnected users. Traditional analytics tools only tell you WHAT happened ("Activity is up 10%"), but they never explain WHY ("Users are angry about the new pricing").
We wanted to build something that doesn't just count posts, but actually understands them. We were inspired by the challenge of taking the raw, headless data from Foru.ms and transforming it into a "Command Center" that gives managers a single, AI-generated Health Score.
Our goal was simple: Turn 4 hours of manual moderation into 4 seconds of AI insight.
What it does
Pulse is an AI-powered community intelligence dashboard that sits on top of any Foru.ms community.
- Real-Time Health Score: Instead of generic charts, Pulse calculates a 0-100 "Health Score" based on sentiment velocity, engagement ratios, and unanswered support threads.
- Crisis Detection: It automatically flags specific "hotspots." In our demo, it successfully detected a Community Health Score of 40, pinpointing "Pricing Complaints" and "File Upload Failures" as the root causes.
- AI Analyst : Users can chat directly with their data. You can ask "Why is the community angry?" or "What features are requested most?", and the AI reads the actual thread context to give cited, strategic advice.
- Smart Analytics: Visualizes sentiment trends over time, proving whether recent changes (like a UI update) actually improved user happiness.
How we built it
We prioritized a production-ready, modern stack to ensure speed and scalability:
- Frontend: Built with Next.js 14 (App Router) and TypeScript. We used Tailwind CSS and Shadcn UI for the "Glassmorphism" dark-mode aesthetic, and Recharts for the data visualization.
- The Data Pipeline: We integrated the Foru.ms API to fetch live thread, user, and post data.
- The AI Engine: We utilized PULSE' ultra-fast inference API (running Llama 3 70b) to analyze thread content in real-time without the latency typical of other LLMs.
- Authentication & Security: Implemented secure API key management to ensure community data remains private.
Challenges we ran into
The biggest technical hurdle was CORS (Cross-Origin Resource Sharing). Because the Foru.ms API is secure, it blocks direct requests from a web browser. At first, our dashboard wouldn't load any data.
The Solution: We engineered a custom Next.js API Proxy (/api/proxy/threads). Instead of the browser hitting the API directly, our frontend requests our own Next.js server, which securely fetches the data from Foru.ms server-side (where CORS isn't an issue) and pipes it back to the UI. This architecture not only fixed the bug but made our app more secure by hiding our API keys from the client.
Accomplishments that we're proud of
- Solving the CORS nightmare: Building a robust proxy architecture that allows us to connect to any headless API securely.
- The "Crisis Detection" Logic: We are proud that our algorithm correctly identified a low health score (40/100) from the test data, distinguishing between "healthy discussion" and "toxic frustration."
- Speed: Optimizing the AI chat to respond in milliseconds using AI, making the experience feel conversational rather than transactional.
- Visual Design: Achieving a professional, SaaS-quality UI that looks like a finished product, not just a hackathon prototype.
What we learned
- Headless is Powerful: Separating the "Data" (Foru.ms) from the "Experience" (Pulse) allows for incredibly creative use cases—like building an analytics tool instead of just another forum frontend.
- Context is King: AI needs good data to give good answers. We learned how to structure forum threads into concise JSON payloads so the LLM could "read" the room accurately without hitting context limits.
- Quantitative vs. Qualitative: Numbers (views) lie; words (sentiment) don't. Combining the two is where the real value lives.
What's next for Pulse: AI Community Intelligence
- Automated Action Plans: Instead of just suggesting a reply, Pulse will draft the perfect apology or announcement for the manager to approve.
- Multi-Platform Integration: Extending our proxy to pull data from Discord and Slack, creating a "Unified Community Health" score across all platforms.
- Predictive Churn: Using historical data to predict which power users are at risk of leaving the community before they actually quit.
Built With
- ai
- cors
- javascript
- next.js
- tailwind
Log in or sign up for Devpost to join the conversation.