Secure Multi-Tenant AI Video Editing, Distribution, and Project Manager Platform

Title: Senior engineer (Claude Code + security) to turn our AI video-editing factory into a secure, multi-client product

About us
We’re a media distribution brand that makes a lot of short vertical video ads for TikTok and Instagram. Over the last few months we built an in-house AI “creative factory” with Claude Code. It does the work of a video editor: it picks up tasks from our project board and edits the raw creator footage into a finished ad. A human reviews and approves, and only then is the final file rendered and delivered.

It works, but it’s a prototype: it runs on one Mac, the keys sit in a .env file, and it’s built for one company. We want an engineer to make it professional, secure and repeatable so it can run for several businesses, each with its own brand, accounts and data.

What exists today

Pipeline: Node 22 server with SQLite. Stations are Intake → Edit → QA → Human review → Render → Delivery. A live “factory floor” web UI shows the jobs moving between stations.
Workers: Python plus ffmpeg. Transcription (ElevenLabs Scribe), an assembly cut (best take of each line, retakes and dead air removed), and an LLM-planned main edit (captions, overlays, product shots, zooms) through OpenRouter (Claude, plus Gemini as a QA judge).
Editor: each ad is an editable timeline project in an open-source web video editor (a customised OpenFilm Studio). The reviewer can open each timeline, change it and approve it.
Integrations: the Asana API (task pickup, custom fields), the Frame.io V4 API (delivery) and Google Drive (footage).
Guardrails: Claude Code hooks, subagents and skills, plus spend caps per day and per job.

What we want built

A cloud deployment. Everything runs on a server: footage never touches a laptop, and nothing is rendered until a human approves.
A desktop workstation app for Mac. It’s a thin client: several jobs open at once, each in its own timeline window, all streamed from the cloud.
Multi-tenancy. Each business gets its own isolated workspace: data, footage, brand kit, API connections, spend limits and users.
Repeatable onboarding. Adding a new business should be config, not code: connect Asana, Drive and Frame.io, upload brand assets, set the rules.
Production quality: CI, tests, monitoring, logs, backups and documentation.

Must-haves

Strong, hands-on Claude Code experience: CLAUDE.md, subagents, skills, hooks, MCP servers, and ideally the Claude Agent SDK and headless runs. Please show real examples.
Cybersecurity, applied. We will test you on:
secrets management and least-privilege service accounts
tenant isolation (one client can never see another client’s footage or keys)
zero-trust access to internal tools (no exposed admin ports)
webhook signature checks
prompt-injection defence: our agents read task text, scripts and comments, which are untrusted input
supply-chain hygiene (pinned dependencies) and audit logs
Node.js and Python in production, Linux servers, ffmpeg or other media-pipeline experience.
Clear written English and async communication.

Nice to have

Swift or desktop-app experience (Tauri or native macOS)
Experience with video at scale (proxies, streaming, GPU or headless rendering)
Hetzner, Modal, AWS, or Cloudflare (Access/Tunnel)
SOC 2-style thinking: access reviews, data retention, incident response

How to apply (answers without these will be skipped)

Start your bid with the word “VSRL”.
Describe a Claude Code hook, subagent or MCP server you’ve built, and what it did.
In 3–5 sentences: how would you stop an AI agent from following instructions hidden in a client’s task description?
How would you isolate tenants’ files and API keys on a shared server?
Links to relevant work (GitHub, case studies).

Budget: $300 / Month (negotiable) · Longterm job - at least for the next 6 months.
We’ll share the full architecture under an NDA after an interview.
Contract under USA cybersecurity and copyright laws.