My own product, Islamabad
Frameo — AI video studio
Turns a spreadsheet of prompts into many AI videos rendering at once, with nothing lost in a crash.
What was going wrong
Video generation was tied to one rendering service with one global limit, and adding another service meant rewriting the core. Big batches had to be created one job at a time, a crash mid-render could lose jobs, and there was no way to see how a batch was going.
What I built
A Windows app that runs every video job through a queue saved to disk. A scheduler hands work to each connected account up to its allowed limit and never over it, with no AI guessing in the loop. Any rendering service plugs in as a single class. Each job moves through eight clear states, gets up to three attempts with a short wait between them, and goes back in the queue automatically after a crash. Account keys are encrypted with Windows DPAPI and never stored in the database, and a live dashboard shows progress with pause, resume and cancel.
What changed
- A CSV of prompts becomes one job per line, spread across several accounts and rendered at the same time
- Tested end to end: 10 jobs on 3 accounts (limit 2 each) peaked at 6 at once and never went over
- Every job was recovered and finished after a simulated crash
- A new rendering service is added in one file, with no scheduler changes
Built with
- C# / .NET 8
- WPF
- SQLite
- Windows DPAPI
Want something like this? Tell me what is not working.