# Build brief — a focused alternative to SocialFaktory

> **Verdict:** Partly, if you narrow it · **Buildability:** 63/100 · **Category:** Social Media
> **Source:** https://www.canitbevibecoded.com/socialfaktory
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from SocialFaktory. Verify current pricing and capabilities before acting.

## Context

**SocialFaktory** — Turns a text brief into a finished short video with AI actors and voices, then posts it to your social channels. It currently costs $49/mo.

The generation half is honest API glue: script writing is an LLM call and the video itself comes from hosted model APIs (fal.ai and friends), so a personal brief-to-video pipeline is very buildable · but you pay those per-generation model invoices yourself either way. The publishing half is the same wall every scheduler hits: TikTok, Instagram, and YouTube OAuth apps are review-gated for weeks, which is why SocialFaktory itself publishes through Postiz. The honest DIY is a generation script feeding a self-hosted Postiz, and what's left over is the tuned prompt pipelines, the QA pass, and someone else eating the platform-review pain.

This brief describes a focused, single-operator replacement for the part of SocialFaktory that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Turn a text brief into a script and a rendered short video via hosted AI model APIs, then queue and publish it through a self-hosted Postiz.

- Draft, queue, and track content for the few networks you actually use.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Always-on box.

### Data and integrations

- Anthropic or OpenAI API key for scripts.
- Video-generation API key (fal.ai or similar).
- Self-hosted Postiz for the platform OAuth and publishing.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a personal AI video factory to replace SocialFaktory. Requirements:

- Node + Express + better-sqlite3; a localhost dashboard with a brief form
  (topic, tone, target duration) and a queue of generated videos.
- Script step: send the brief to the Anthropic API and get back a hook line,
  a spoken script, and a visual prompt; keep the system prompt in
  prompts/script.txt so I can tune it without touching code.
- Video step: submit the visual prompt to fal.ai's queue API for a
  text-to-video model with native audio, poll until done, download the mp4
  into media/ and record the actual dollar cost per generation in the DB.
- Review page: each finished video gets a player plus approve, regenerate,
  and discard buttons; nothing publishes without an explicit approve.
- Publish step: on approve, POST the video and caption to my self-hosted
  Postiz via its public API (POSTIZ_URL and POSTIZ_API_KEY in .env) with a
  scheduled time · Postiz owns the platform OAuth; never call TikTok,
  Instagram, or YouTube APIs directly.
- A node-cron tick retries failed generations 3 times with backoff and marks
  rows before submitting so nothing ever double-bills.
- A running-costs box on the dashboard summing this month's model spend.
- Out of scope: multi-brand workspaces, teams, analytics, auto-QA, and any
  direct platform integrations (say so in the README).
- README: getting the two API keys, pointing at a Postiz instance, and what
  a single video roughly costs to generate.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Pre-approved platform OAuth apps (TikTok/Instagram/YouTube reviews take weeks).
- Prompt pipelines tuned per model, format, and tone.
- An automated QA pass before anything ships.
- Multi-brand workspaces and a scheduling calendar.
- A flat bill · DIY pays every model invoice directly, and video models are not cheap.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No reviewed project implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Postiz](https://github.com/gitroomhq/postiz-app) — Open-source social publishing · the scheduling/OAuth half of this product, self-hostable
- [Mixpost](https://github.com/inovector/mixpost) — Self-hosted social media management, an alternative publishing backbone

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/socialfaktory