AI Workflow Automation · Private build · 3 min read
Frameflow
A five-stage video generation application designed around asynchronous provider work and callback-driven progression.
Five-stage UGC-style video generation pipeline
Project overview
A five-stage pipeline for UGC-style video ads
Services: AI Workflow Automation ; AI Agents
Delivery: Video-generation application and AWS orchestration infrastructure. Portfolio alias.
Project Snapshot
| Figure | What it represents |
|---|---|
| 5 creative stages | Scene, image, script, video, and voice/lip-sync |
| 10-second video | Target output in the documented pipeline |
| 12-15 words | Script target in the documented configuration |
| About $1.35 | Historical provider-cost estimate per video, not a current measured all-in cost |
The Problem
Producing one video involved several AI services. An image had to reach the video provider, the script had to reach speech generation, and the finished video and audio had to reach lip-sync.
The providers did not all finish within one request. A video job could remain active after the user left the page. The application needed to retain the job, recognize the callback, and continue from the correct stage.
What We Delivered
The pipeline starts with a reference image and product information. Gemini analyzes the scene and prepares the imagery and script. Kling handles image-to-video generation. Speech generation and Sync.so provide the voice and lip-sync stages.
AWS Step Functions coordinates the sequence. Lambda tasks perform individual actions, DynamoDB stores project and external-job information, and S3 holds media. API Gateway exposes callback routes.
The state machine includes waits for Kling and Sync.so completion, a finalization task, and an error-handling path.
Engineering Decisions
Wait for completion events. The pipeline uses task-token waits for long-running jobs rather than holding an ordinary web request open.
Retain the external job ID. A provider callback needs to resolve to the correct project and stage.
Track failure as part of the workflow. A failed generation must leave a useful project state rather than appearing to run forever.
Keep the cost breakdown visible. Earlier documentation estimates roughly $0.001 for Gemini, $0.50 for Kling, and $0.83 for Sync.so, rounded to about $1.35. Retries, duration, infrastructure, and changing provider rates can alter the actual cost.
Results
The delivered product coordinates the generation stages from input to finalized media. Users do not need to manually move each intermediate output between the providers in that pipeline.
The historical estimate is useful for explaining the original unit-cost design. It is not presented as a current price guarantee or evidence that the videos increased ad conversions.
Technology stack
React, Vite, Amplify; AWS CDK in TypeScript; Step Functions, Lambda, DynamoDB, S3, API Gateway; Gemini, Kling, speech generation, and Sync.so.
Project at a glance
Reference image to a speaking video ad.
Frameflow connects five creative stages through an AWS pipeline with provider callbacks and tracked jobs. The documented configuration targets ten-second videos; its historical provider-cost estimate was about $1.35 per output.
Project summary
We built the pipeline behind the video generator: scene analysis, imagery, script, video, and voice sync. The work included waiting for provider jobs, matching callbacks to projects, and handling failures between stages.
Build a system around your workflow.
Tell us where the work gets stuck. We will map the first release, integrations, cost, and timeline.
Discuss a similar project