Product

Clepora

Create once. Reach everywhere.

Pre-launch — YouTube and TikTok approved, Meta pendingclepora.com ↗

clepora / by the numbers

  • 3,466automated tests, run green — 2,704 backend and 762 frontend across 217 files
  • 9platform publishers, each with its own format, limit and rate-limit rules
  • 43versioned schema migrations — the schema is a reviewed artifact
Clepora's landing page: the headline 'Create once. Reach everywhere.', a start-publishing button, and the nine platforms it posts to.

One upload becomes nine platform-native posts, scheduled and published from a single workflow.

The challenge

A creator or a small marketing team makes one good video and then loses an afternoon to it — recutting for aspect ratio, rewriting the caption for each platform’s voice and character limit, working out hashtags, and posting nine times by hand at nine different good moments. The work that multiplies is not the creative work. It is the clerical work after it, and it scales linearly with however many audiences you are trying to reach.

What we built

A FastAPI backend and Next.js dashboard over Postgres, Redis and S3-compatible object storage, with background workers doing the publishing.

The core is a publisher dispatcher with one adapter per destination — YouTube, TikTok, Instagram, Facebook, Threads, LinkedIn, Pinterest, Telegram and Discord. Each adapter owns its platform’s real constraints: media format rules, caption limits, the difference between a Short and a video, privacy status, and per-platform rate limits. First-comment posting, caption generation and hashtag strategy are separate concerns layered over the dispatch, so a change to how captions are written does not touch nine integrations.

Publishing is the spine, not the whole product. One upload can also become a set of scored clips cut from a long video, an audiogram, or a podcast episode — Clepora hosts the RSS feed, generates chapters, embeds ID3 tags for Apple, separates speakers, and counts downloads following the IAB podcast measurement guidelines (it is not IAB-certified). A broadcast can go out live from the browser over WHIP and be simulcast to several platforms at once, and anything recorded in the in-browser recorder runs the same caption-and-publish path as an upload.

Around that sits the operational apparatus a real SaaS needs and prototypes skip: Stripe billing (integrated, in test mode until launch), TOTP multi-factor auth with email and SMS channels and single-use recovery codes, role-based access control with a staff/department model, an audit log, media retention policy, copyright scanning, GDPR data export and deletion, and a 31-article help centre wired to the errors it explains. The dashboard is built to target WCAG 2.2 AA, not yet independently audited — real dialogs with focus management, an announcer for live changes, and a contrast token enforced by its own test.

Where it stands

Clepora is feature-complete for its launch scope and in the platform app-review stage. YouTube approved production access in August 2026, and TikTok’s Content Posting API audit cleared the same month — both verified against the live APIs rather than taken from an approval email. Meta is the one gate still closed: its production access needs business verification against the legal entity, so the remaining work is a company filing rather than engineering.

The evidence packages for those reviews are part of the project, and so are the replies — the YouTube policy correspondence, the screencast evidence and the compliance audits are kept beside the code they describe, and can be shown on request.

Capabilities this demonstrates