Skip to main content

The Platform Loop


See (Ingest)

Get video and audio from anywhere into VideoDB.

Process

Understanding configuration converts raw media into reusable, processable artifacts before indexing.
  • Scene segmentation - Time-based or shot-based
  • Frame sampling - Control which frames to analyze
  • Audio chunking - Word, sentence, or time-based segments
This is where cost control happens - sampling policies trade compute for recall.

Understand (Indexes)

Indexes are programmable interpretation layers. You define what to extract with prompts.
  • Prompt-driven - Natural language instructions
  • Model-orchestrated - LLMs and VLMs do the work
  • Additive - Multiple indexes on same media
  • Multimodal - Visual and spoken

Remember

Indexes are stored as episodic memory. This is automatic by default. What gets stored:
  • Transcripts and embeddings
  • Scene descriptions and tags
  • Structured metadata
  • Retrieval structures
For a live stream, set store=True when you plan to index its continuous VLM output:

Search across indexed content with natural language. Results include playable evidence.
Results include:
  • Timestamps - Exact start/end times
  • Text - What was detected
  • Score - Relevance ranking
  • Stream URL - Playable link

Act

Go from understanding to automation and outputs.

Event Detection

Continuously understand and index the live VLM output before adding an alert:

Programmable Editing

Compose outputs using the 4-layer editor architecture:

Architecture Patterns

The loop applies to different use cases:

Next Steps

Data Model

Collections, Videos, RTStreams, and other core objects

Indexes

Turn media into searchable knowledge

Search & Retrieval

How search returns playable evidence

Events & Alerts

Real-time detection and automation