Inspiration

Managing a film production studio involves juggling massive amounts of fragmented data—from scene-by-scene budget breakdowns to VFX costs and live box office tracking. The inspiration for Studio-in-a-Box came from the need to build a centralized command center that brings these moving parts together. We wanted to empower directors and producers with real-time analytics, AI-driven insights, and live financial simulations, all within a single, unified dashboard rather than scattered spreadsheets.

What it does

Studio-in-a-Box is a full-stack film production and analytics platform. It provides a comprehensive command center for studios to track, compare, and simulate movie data[cite: 1]. Key features include:

  • Live Box Office Simulator: Real-time streaming of simulated box office performance data[cite: 1].
  • Advanced Analytics: In-depth breakdowns of budget vs. box office, VFX budget tracking, and scene-cost benchmarking[cite: 1].
  • AI Agent Integration: A built-in chat widget and live agent activity tracking to assist with production intelligence and reporting[cite: 1].
  • Executive Dashboard: A responsive UI featuring a Director Hero view, Production KPIs, and Execution Trace Drawers for deep-dive analysis[cite: 1].

How we built it

We engineered Studio-in-a-Box using a robust, containerized microservices architecture to handle high-frequency data and analytical workloads[cite: 1]:

  • Frontend: Built with React and TypeScript using Vite, and styled with Tailwind CSS for a sleek, highly responsive executive dashboard[cite: 1].
  • Backend Core: Developed in C# .NET, utilizing REST APIs and SignalR Hubs to stream real-time financial and production data to the client[cite: 1].
  • Analytics Engine: Powered by ClickHouse to handle heavy, fast analytical queries regarding movie comparisons and scene costs without bottle-necking the primary application[cite: 1].
  • Live Box Office Simulator: To generate realistic real-time financial data, we implemented a stochastic model in the backend to simulate weekend box office drops and viral spikes[cite: 1]. The projected revenue $R$ at time $t$ is calculated using a modified exponential decay function that incorporates a time-dependent social sentiment multiplier $S(t)$: $$ R(t) = R_0 e^{-\lambda t} + \alpha \int_{0}^{t} S(\tau) e^{-\beta(t-\tau)} d\tau $$ This mathematical foundation allowed our C# service to push highly realistic, fluctuating revenue streams through SignalR[cite: 1].
  • AI Agent: A standalone Node.js service that interfaces with the main platform to provide live agent activity tracking and production intelligence reporting[cite: 1].
  • Infrastructure: The entire stack, including the SQL data seeding and database engines, is orchestrated using Docker Compose[cite: 1].

Challenges we ran into

One of the most significant technical hurdles was establishing seamless, real-time communication across a multi-language microservices architecture[cite: 1]. Bridging the fast analytical queries from ClickHouse to the .NET backend, and then pushing that live data efficiently to the React frontend via WebSockets, required careful memory management and architectural planning[cite: 1]. Additionally, coordinating the separate Node.js AI agent with the C# backend system meant we had to maintain strict API contracts and manage state across entirely different runtime environments[cite: 1].

Accomplishments that we're proud of

We are incredibly proud of successfully integrating ClickHouse for high-performance data analytics alongside real-time WebSocket streaming. Building a complex, multi-tiered architecture (Node.js agent, .NET backend, React frontend) that successfully runs in a unified Docker environment is a massive win. The resulting dashboard is not only data-rich but also highly responsive and visually polished.

What we learned

This project was a deep dive into high-performance system design and data orchestration. We gained hands-on experience optimizing columnar analytical queries with ClickHouse, managing real-time state with SignalR, and structuring a scalable, strictly-typed frontend with React and TypeScript[cite: 1]. Navigating the deployment of multi-language microservices using Docker also taught us invaluable lessons in container networking and system reliability[cite: 1].

Built With

Share this project:

Updates

Submission history