The numbers are clean. $2 million pre-seed, then $10 million seed six months later. General Partnership, then Sequoia. The velocity is not unusual for AI infrastructure plays, but the product category is: a central control panel for AI video generation. Preview has raised $12 million total, and according to Sequoia, it is the "video version of Cursor." Over 100 studios already onboard, 3,000 more on a waitlist. The pitch is that AI video production lacks a unified workspace — a place to manage scripts, storyboards, shot lists, generation, review, and feedback. Preview solves that. But the detail that caught my attention is buried in the metadata: each frame records who generated it, what model was used, and the parameters applied. That is where the real story lies.
Context: AI video generation is exploding, but the professional film production pipeline is still fragmented. You have text-to-video models like Runway, Pika, and Sora, each with their own APIs, parameters, and output formats. Teams of artists, directors, and editors move between tools, often losing track of which version came from which model, under what seed, with what prompt. The result is a chaotic workflow that scales poorly. Preview positions itself as the orchestration layer, bringing all models into one workspace while maintaining a per-frame audit trail. That audit trail is what makes it interesting from a cryptographic perspective.
Core: The metadata is the proof. Every frame in Preview carries a signature of its origin: model ID, parameters, timestamp, and user. This is not a blockchain — it is a centralized database. But the structure is identical to what you would need for a verifiable provenance system. In my work auditing ZK-rollup state transitions, I have seen this pattern before. The question is not whether the metadata exists, but whether it can be trusted. Right now, Preview controls the servers. If a studio wants to prove that a particular frame was generated by a specific model on a specific date, they must trust Preview’s backend. There is no cryptographic immutability, no public verification. The metadata is there, but it is not verifiable by a third party. This is a failure mode waiting to be exploited. Imagine a dispute over copyright or authenticity. The studio would have to subpoena Preview’s logs. That is not a trustless system.
From my experience benchmarking NFT metadata standards — specifically the gas inefficiencies of off-chain vs on-chain ERC-721 storage — I can tell you that the same trade-offs apply here. Off-chain metadata is cheap but fragile. On-chain metadata is expensive but immutable. Preview’s current approach is the off-chain equivalent: fast, scalable, but ultimately a single point of trust. For a platform that aims to be the backbone of professional film production, this is a vulnerability. The 3,000 studios on the waitlist should be asking: how do you prove that a frame was not tampered with after generation? The answer, today, is that you cannot.
Proofs don’t lie. But they require a verifier. Preview does not yet have one. The metadata is recorded, but it is not hashed into a public ledger. The model parameters are stored, but they are not committed to a Merkle tree. The generation timestamp is logged, but it is not anchored to a blockchain timestamp. This is not a criticism of Preview’s product — it is a feature request. The infrastructure is already in place. The only missing piece is a cryptographic commitment at the point of generation. If Preview were to emit a hash of each frame’s metadata into a public chain (Ethereum, Solana, or even a data availability layer like Celestia), they would create an immutable provenance trail. The cost would be minimal, the benefit enormous.
Contrarian: The common narrative is that AI video needs a "Cursor for video" — a unified editor. But that is a surface-level problem. The deeper issue is trust. In traditional film, authenticity is established through physical negatives and chain of custody documents. In AI-generated video, there is no physical negative. The only evidence is the metadata. If that metadata is mutable, the entire production is vulnerable to forgery. Silence in the code speaks louder than hype. The hype is about workflow efficiency. The silence is about verifiability. Preview’s metadata recording is a step in the right direction, but it is incomplete. The industry does not need just a central control panel; it needs a cryptographic foundation for provenance. Without it, AI-generated video will face the same trust crisis that NFTs faced in 2021 — widespread forgery, disputes over ownership, and a collapse of confidence.
Verification is the only trustless truth. I have seen this movie before. In 2021, I analyzed the gas costs of on-chain vs off-chain NFT metadata. The market ignored the analysis, and we saw millions of dollars lost to metadata manipulation and rug pulls. The same pattern is repeating in AI video. The studios adopting Preview now are building workflows on top of a centralized trust model. They will eventually need to migrate to a verifiable layer. The question is whether Preview will build that layer or whether a competitor will. The 3,000 studios on the waitlist represent a massive opportunity for a blockchain-based provenance solution. I would not be surprised to see a ZK-based proof system for AI video generation within the next 12 months.
Takeaway: Preview has built a clean product that solves a real fragmentation problem. But the metadata recording feature is a Trojan horse for something bigger. If Preview can add cryptographic commitments to each frame — a hash on-chain, a ZK proof of model execution — they will become the de facto standard for trusted AI video production. If they do not, someone else will. The 3,000 studios waiting should demand verifiability, not just convenience. The future of AI video is not just about generating better pixels; it is about proving where those pixels came from. I trust the null set, not the influencer. The market will eventually choose the platform that offers both efficiency and cryptographic integrity. Preview has the first part. The second part is up for grabs.


