← Live-стрічка

Build a Turnkey AI Series Production Engine: n8n, AI Video & Story Memory

Бюджет: $300.0 FIXED / ⭐ 0.00 (0) Netherlands

api-integration, python, artificial-intelligence, automation, postgresql

Preferred qualifications

  • Experience: Expert
Bilding an original episodic fiction project and looking for one senior AI automation engineer, full-stack builder, or small technical agency who can take ownership of the technical side. I already have the original story, world and creative direction. What I need is the machine that turns that story into a repeatable series. The goal is to build a turnkey, cloud-hosted production engine that can progressively automate: Story / Season Plan → Story & Character Memory → Script → Scenes → Consistent Visual References → Images → AI Video → Character Voices → Music/SFX → Subtitles → Final Vertical Episode → Scheduling → Publishing → Next Episode The important part is not simply generating AI videos. Continuity is the product. Characters should remain recognisable between episodes. Voices, locations, relationships, important events and narrative state should persist. The system should reuse references rather than recreate the world from scratch every time. I’m open to the best technical approach. A likely stack could include n8n or equivalent orchestration, PostgreSQL/Supabase, AI APIs, FLUX or equivalent image models, Kling/Veo or equivalent video models, ElevenLabs or equivalent voice technology, FFmpeg and cloud infrastructure. I would particularly value someone who already has working automation components that can be adapted rather than rebuilding everything from zero. Phase 1 This job is the first paid build phase, not the final consumer platform. The objective is to create the strongest practical Version 1 of the reusable production engine, prove it with a real end-to-end episode, and leave a foundation that can continue producing future episodes without rebuilding the workflow. Version 1 should prioritise: Persistent Story Bible, Character Bible and episode state Reusable character/location references Automated script and scene generation Image, image-to-video and persistent voice generation Automated subtitles and episode assembly Ability to regenerate individual failed scenes Organised storage of source assets and generated outputs Basic API cost tracking Cloud execution without relying on my personal computer Error handling/retries Scheduling and automated publishing where official platform APIs allow it I’m comfortable keeping one simple human approval checkpoint initially if that materially improves quality and prevents expensive bad generations. The architecture should make increased automation possible later. I’m Looking for One Technical Owner I do not want to coordinate multiple freelancers or manually operate a complicated production workflow. I want to provide the story and creative direction, while you take responsibility for designing, building, configuring and testing the technical system. If you are a small agency, that is completely fine — I simply want one accountable point of contact. Full Handover Is Essential I want to own the resulting system. All critical infrastructure should ultimately operate under accounts I control, and the handover should include the applicable n8n workflows, source code, Git repository, database/schema, prompts, deployment/configuration, generated assets, documentation and a walkthrough. The system must not depend on private infrastructure that only the contractor can access. Another competent developer should be able to continue the project later if necessary. Where This Can Go If Phase 1 works, my intention is not to stop after one episode. I want to progressively reinvest in the system and ideally continue with the same technical partner. Later phases can include stronger automation, production at scale and eventually our own web/iOS/Android subscription platform with series, seasons, episodes, vertical playback, user accounts, free/premium content, subscriptions, notifications and analytics. So I’m particularly interested in someone who sees this as a small first build with the potential to become a much larger product, rather than a one-off video job. In your proposal, please be realistic about what you would build in Phase 1, what you would automate now, what you would postpone, and which existing components you would reuse to maximise quality while keeping costs low. If you have already built an n8n/AI-video automation pipeline, AI content engine, generative media system or similar product, I would very much like to see it.
Відкрити замовлення

AI-чернетка відгуку

Короткий текст відгуку для копіювання в офер: інтерес + готовність працювати.

Увійдіть, щоб згенерувати AI-чернетку.

Увійти