Cutline/Status

All systems operational

Last checked Fri, 10 Jul 2026 14:03:21 UTC

Components

5 services

Queue (Redis)

Operational

BullMQ job queue + rate limiting

PONG1164ms

Database (Postgres)

Operational

User accounts, anonymous sessions, job ownership

DATABASE_URL configured

Language models (OpenRouter)

Operational

Script, narrative, intent, and image-prompt generation

API key configured

Text-to-speech (ElevenLabs)

Operational

Voiceover generation for every shot

ElevenLabs key configured

Image sourcing

Operational

Stock photos and AI image generation per shot

Active providers: Unsplash, Pexels, DALL·E 3

Pipeline architecture

Cutline runs every video through a 12-stage pipeline orchestrated by BullMQ workers. Each stage checks a Redis cancellation flag before executing, and transient failures (429 / 5xx) retry up to three times with exponential backoff.

  1. 1 Intent
  2. 2 Narrative
  3. 3 Shots
  4. 4 Script
  5. 5 Subtitles (draft)
  6. 6 TTS (voice)
  7. 7 Subtitle refine
  8. 8 Motion
  9. 9 Asset analysis
  10. 10 Visuals
  11. 11 Image sourcing
  12. 12 Remotion render

Health endpoint

/api/health

Liveness probe

/api/health/live

Readiness probe

/api/health/ready

Metrics

/api/metrics

Status is computed live on each request. Component checks include a real Redis ping, environment configuration, and database availability.