Skip to main content
Architects who need a long camera take, not a 3-second burst

The Veo walkthrough stack

Make runs the job, Gemini writes the camera path, Veo 3 is the long take. Not Kling, not Luma, not a second video model.

Who owns what

  1. Make

    The job — webhook in, Vertex poll, MP4 out. Not the camera math.

    Try Make (opens in a new tab)
  2. Google Gemini

    The path — pan, tilt, light. Not the diffusion and not storage.

    Try Google Gemini (opens in a new tab)
  3. Veo 3

    The take — long HD, spatial continuity, native ambisonics. Not BIM parse.

    Try Veo 3 (opens in a new tab)

How to use this stack

  1. Floor-plan metadata hits Make. Do not start in a social video tool.
  2. Gemini writes trajectory and light. One writer.
  3. Veo 3 on Vertex renders the walkthrough. Do not also run Kling, Luma, or Sora.
  4. Make archives the MP4. This is not cinematic-vfx (Flux stills + Luma interpolate). Not the creator stack.