# Platform — VideoDB > One backend. Any source. Six primitives — ingest, index, remember, retrieve, edit, stream — across files, live streams, cameras, and screens. --- ## Hero One backend. Any source. Six primitives: ingest, index, remember, retrieve, edit, stream. Across files, live streams, cameras, and screens. CTAs: [Try VideoDB](https://console.videodb.io/auth) · [Read the docs](https://docs.videodb.io/) --- ## Trust strip Fully Managed · Cross-Cloud · Real-time + Batch · BYO Models · Sovereign-Ready · SOC 2 Type II --- ## Six primitives Six building blocks. One SDK. Any video moment. Static files and live feeds enter one pipeline. Index layers compound into a queryable memory. Retrieval surfaces the right moments. A new stream comes out the other side, on demand. 1. **Ingest** — Any source, any format, normalized on the way in. A single ingestion path with a built-in transcoding engine: any codec, any container. Files and live feeds land in VideoDB’s internal format, ready to be indexed. [See ingest reference](/developers#ingest) 2. **Index** — Stack understanding layers over every frame: scenes, speech, objects, embeddings, brands, people, custom domain events. Indexes are additive and reusable; new questions do not require re-processing the video. [See index reference](/developers#index) 3. **Remember** — Scene-level memory that persists. A 4-hour archive, a 1,000-camera fleet, an agent session all reduce to the same memory model. Scoped per user, agent, workspace, or fleet. Re-indexable forever. [See remember reference](/developers#memory) 4. **Retrieve** — Sub-second retrieval across petabytes. Semantic and structured queries across every video layer. Every hit is a streamable clip URL. Not a timestamp, not a row. Verifiable for users, consumable by agents. [See retrieve reference](/developers#retrieve) 5. **Edit** — Programmable timeline, cuts as code: cut, compose, dub, subtitle, reframe, add branding. All by code, not drag-and-drop. An agent-ready skill for media editing. The output is a clean stream. [See edit reference](/developers#edit) 6. **Stream** — Output fits the consuming system: HLS for players, WebSockets for agents, Webhooks for operations, agent-ready URLs for tools. One feed or a thousand. Every output is a stream URL. [See stream reference](/developers#stream) One pipeline · realtime + batch · same SDK. PB-scale memory · ms-scale retrieval. --- ## How VideoDB works One abstraction for the full video lifecycle. Ingest once, index deeply, retrieve exact moments, and stream results without stitching together storage, transcoding, search, and delivery services. - **You ship indexes.** The platform owns compute and storage — chunking, replication, encoding, GPU scheduling. Your team ships indexes, not infrastructure. - **Information access is managed for AI.** Queries run through segregated indexes scoped by tenant, workload, or domain. Results route automatically: no federation, no glue, no leaks. - **Built-in admin console.** Define who reads what, where keys live, and what data can leave the boundary. One surface, no per-endpoint access logic. - **Modular.** Choose the components you want and plug them into your system. Take search, memory, clips, alerts, or actions piece by piece, or adopt the whole stack. --- ## Why teams choose VideoDB Built differently for the AI video era. VideoDB brings together encoding, indexing, retrieval, editing, and streaming in one purpose-built backend, powered by a media processing engine built over years for AI-native video applications. - **10x** — Lower total cost. One bill replaces 10+ vendors. - **100x** — Faster video retrieval. ~120 ms across PB archives. - **5 min** — To production. pip install, POC same day. - **1 API** — For realtime + files. Same SDK, same mental model. --- ## MP4 stack vs VideoDB abstraction | | MP4 stack | VideoDB abstraction | |---|---|---| | Storage | Files in S3 / GCS; you manage chunking, replication, lifecycle (manual) | Managed by the platform, content-addressed, dedup'd (0 ops) | | Edits | Re-encode on every edit; ffmpeg pipelines to run | Chunk-level slice to a new HLS link, no re-encode | | Indexes | Vector DB + Postgres + metadata store, 3+ sources of truth | Indexes live with the media, one source of truth | | Query | Cross-system join, custom code on the hot path (~12 s p95) | Indexes run retrievals, composed/filtered/scoped at query time (~120 ms p95) | | Output | HLS adapter bolted on as a separate downstream service | HLS is native; every output is a stream URL | --- ## Technical solutions Reference technical solutions, built on the same six primitives. Each has a deeper page with code, architecture, and dataflow. 1. **Personalized streaming** — Pull the right moments from memory, compose them with branding and subtitles, and ship a fresh HLS feed per user. Built on retrieve + edit + stream. [See architecture and code](/platform/personalized-streaming) 2. **Realtime alert** — Attach a camera, define what counts as an event in natural language, and get sub-second alerts with the matching clip attached. Built on stream + index + retrieve. [See architecture and code](/platform/realtime-alert) --- ## What teams say - "Composable indexes are the right abstraction for video AI. VideoDB is the first team I've seen build the data-infrastructure layer instead of yet another model wrapper." — Mira Sundaram, Director of Video AI, Major OTT - "We replaced four pipelines with one platform and shipped a feature in a sprint that was on our roadmap for two quarters. The team owns the indexes, and that's the unlock." — Daniel Park, VP Engineering, AI Infra Startup - "What sold us was the search engine on top: ranking, recall, sub-second latency. Most products give you embeddings and call it search. VideoDB actually retrieves." — Priya Anand, Head of Search, Media Group --- ## Deployment One SDK. Managed or in your cloud. Start managed, move to your own cloud later — no code changes. - **[FULLY MANAGED]** Fastest path — Run on VideoDB Cloud. We manage the compute, storage, and scale; you build with the SDK. Best for media teams, agentic startups, ML product teams. [Build with VideoDB](https://console.videodb.io/auth) - **[BRING YOUR OWN CLOUD]** Sovereign / regulated — Run inside your AWS, GCP, or Azure. Keep videos in your storage, use the same SDK. Best for healthcare, fintech, defense, telco, regulated EU buyers. [Talk to us](/company#contact) --- ## People who back us Investors and advisors who've built this before — search engineers from Apple, computer vision investors from Voxel AI, veteran AI infrastructure VCs. - **Kranti Parisa** — Advisor, Search. Former Search Lead at Apple; has built search systems at planetary scale. - **Vaibhav Viswanathan (Vai)** — Computer Vision Lead at Voxel AI and investor at VideoDB. Deep operating experience across real-time perception and large-scale video pipelines. - **Robin Vasan** — Investor, AI Infrastructure. Three decades backing developer platforms and data systems, from open source to enterprise-scale infra. --- ## Closing Video Intelligence that will transform healthcare, security and media is here. Start with the SDK, or talk to us about an enterprise architecture review. CTAs: [Start building](https://console.videodb.io/auth) · [Talk to us](/company#contact) --- © 2026 VideoDB, Inc. · videodb.io