StudioPulse AI is an intelligent streaming Quality of Experience (QoE) analysis platform designed to transform complex streaming performance data into clear and actionable insights.

Instead of simply displaying charts and metrics, StudioPulse AI follows an evidence-based investigation workflow:

DATA → SIGNAL DETECTION → EVIDENCE ANALYSIS → INVESTIGATION → NEXT BEST ACTION

The platform analyzes streaming playback performance using real research-based data and metrics such as:

• Subjective Mean Opinion Score (MOS) • Video Quality • Integrated QoE • Stall Events • Stall Duration • Resolution and Bitrate • Viewing Context

In this demo, StudioPulse AI identifies a critical performance signal, compares it against dataset baselines, analyzes supporting evidence, and guides the investigation toward the next best action.

Key Features:

• Streaming QoE Analytics • Rule-Based Anomaly Detection • Evidence-Backed Investigation • AI-Assisted Investigation Workflow • Interactive Analytics Dashboard • Signal and Incident Prioritization • Data Provenance and Transparency • Actionable Recommendations

StudioPulse AI was built with the idea that data should do more than just show what happened.

It should help us understand what needs attention, what the evidence suggests, and what should be investigated next.

StudioPulse AI - From streaming data to actionable intelligence.

StudioPulseAI #Hackathon #AI #StreamingAnalytics #QoE #DataAnalytics #React #TypeScript #ArtificialIntelligence

Built With

  • agentic-ai
  • ai-agents
  • anomaly-detection
  • audience-analytics
  • clickhouse
  • cloud
  • data-analytics
  • decision-intelligence
  • fastapi
  • gemini
  • generative-ai
  • google-cloud
  • google-cloud-agent-builder
  • mcp
  • media-&-entertainment
  • python
  • rest-api
  • sql
Share this project:

Updates

posted an update —

Day 1 of building StudioPulse

We’ve started working on our hackathon project, StudioPulse - an AI-powered system designed to help media teams understand what is happening in their content performance and, more importantly, what they should do next.

Our goal is simple: move from “What happened?” to “What should we do next?”

Today was mainly about defining the problem, exploring the hackathon requirements, and shaping the idea.

Log in or sign up for Devpost to join the conversation.

Submission history