Vibecode Vimeo

You are building a lean indie version of Vimeo.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Vimeo indie build

## Goal

Build the smallest trustworthy replacement for the core Vimeo workflow for one developer or a tiny team.

## Scope

Transcode an HLS ladder with ffmpeg, sync it to object storage behind a CDN, and serve unlisted embed pages from your own player.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- live streaming, webinars, and events
- auto captions, chapters, and the accessibility tooling around them
- viewer analytics and engagement graphs
- OTT, pay-per-view, and the monetization stack
- a player QA'd against every browser, smart TV, and embed surface
- traffic spikes absorbed by someone else's bandwidth bill

If those capabilities are essential, use PeerTube instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a personal ad-free video host to replace Vimeo. Requirements:

- Node + Express on a small VPS, Cloudflare R2 for the media, Cloudflare in front of
  it. Server-rendered pages, hls.js for playback, no frontend framework.
- I run `pub <file.mov> --title "..."`; ffmpeg builds an HLS ladder at 1080p, 720p,
  and 540p with a master.m3u8 and a poster JPEG, then rclone syncs it to R2.
- Each video gets /v/<slug>: player, title, description, and a copyable embed
  snippet. /e/<slug> is the bare iframe target with no page chrome.
- Privacy is one field per video · public, unlisted (random slug, indexed nowhere),
  or password, checked server side before the manifest URL is handed out.
- Metadata lives in SQLite via better-sqlite3. Media never stays on the VPS disk
  after upload. R2 keys and the Cloudflare zone come from .env.
- A /library page behind basic auth lists every video with duration, size, and this
  month's egress pulled from the Cloudflare GraphQL API, so the bill is never a
  surprise.
- No accounts, no ads, no telemetry, and no tracking pixels in the embed.
- Out of scope: live streaming, monetization, and comments. Do not build a social
  feed or a recommendation surface. Captions can come later from whisper.cpp.
- README: R2 bucket and custom domain setup, why the CDN is not optional, and an
  honest warning that a video going viral is now your invoice, not Vimeo's.

## Required capabilities

- ffmpeg
- object storage (R2, B2, or S3)
- a CDN in front of it
- a small VPS for the pages
- an egress budget you now own

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of Vimeo.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Vimeo indie build

## Goal

Build the smallest trustworthy replacement for the core Vimeo workflow for one developer or a tiny team.

## Scope

Transcode an HLS ladder with ffmpeg, sync it to object storage behind a CDN, and serve unlisted embed pages from your own player.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- live streaming, webinars, and events
- auto captions, chapters, and the accessibility tooling around them
- viewer analytics and engagement graphs
- OTT, pay-per-view, and the monetization stack
- a player QA'd against every browser, smart TV, and embed surface
- traffic spikes absorbed by someone else's bandwidth bill

If those capabilities are essential, use PeerTube instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a personal ad-free video host to replace Vimeo. Requirements:

- Node + Express on a small VPS, Cloudflare R2 for the media, Cloudflare in front of
  it. Server-rendered pages, hls.js for playback, no frontend framework.
- I run `pub <file.mov> --title "..."`; ffmpeg builds an HLS ladder at 1080p, 720p,
  and 540p with a master.m3u8 and a poster JPEG, then rclone syncs it to R2.
- Each video gets /v/<slug>: player, title, description, and a copyable embed
  snippet. /e/<slug> is the bare iframe target with no page chrome.
- Privacy is one field per video · public, unlisted (random slug, indexed nowhere),
  or password, checked server side before the manifest URL is handed out.
- Metadata lives in SQLite via better-sqlite3. Media never stays on the VPS disk
  after upload. R2 keys and the Cloudflare zone come from .env.
- A /library page behind basic auth lists every video with duration, size, and this
  month's egress pulled from the Cloudflare GraphQL API, so the bill is never a
  surprise.
- No accounts, no ads, no telemetry, and no tracking pixels in the embed.
- Out of scope: live streaming, monetization, and comments. Do not build a social
  feed or a recommendation surface. Captions can come later from whisper.cpp.
- README: R2 bucket and custom domain setup, why the CDN is not optional, and an
  honest warning that a video going viral is now your invoice, not Vimeo's.

## Required capabilities

- ffmpeg
- object storage (R2, B2, or S3)
- a CDN in front of it
- a small VPS for the pages
- an egress budget you now own

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of Vimeo.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# Vimeo product brief

## Problem

Hosting your own video stopped being exotic: ffmpeg builds the HLS ladder, object storage holds it, a CDN serves it, and hls.js plays it. For a portfolio or a client reel that is a weekend, and the result has no ads, no upsells, and no platform that can change its mind about your account. What you are actually buying from Vimeo is the delivery layer holding up when 4,000 people open the link at once, plus live streaming, captions, analytics, and a player that has been QA'd against every browser, smart TV, and embed context you will never test. Small library, predictable traffic · build it. Anything with a spike in it · the bandwidth bill is the whole argument.

## Product outcome

Transcode an HLS ladder with ffmpeg, sync it to object storage behind a CDN, and serve unlisted embed pages from your own player.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- ffmpeg
- object storage (R2, B2, or S3)
- a CDN in front of it
- a small VPS for the pages
- an egress budget you now own

## Explicit non-goals for v1

- live streaming, webinars, and events
- auto captions, chapters, and the accessibility tooling around them
- viewer analytics and engagement graphs
- OTT, pay-per-view, and the monetization stack
- a player QA'd against every browser, smart TV, and embed surface
- traffic spikes absorbed by someone else's bandwidth bill

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build me a personal ad-free video host to replace Vimeo. Requirements:

- Node + Express on a small VPS, Cloudflare R2 for the media, Cloudflare in front of
  it. Server-rendered pages, hls.js for playback, no frontend framework.
- I run `pub <file.mov> --title "..."`; ffmpeg builds an HLS ladder at 1080p, 720p,
  and 540p with a master.m3u8 and a poster JPEG, then rclone syncs it to R2.
- Each video gets /v/<slug>: player, title, description, and a copyable embed
  snippet. /e/<slug> is the bare iframe target with no page chrome.
- Privacy is one field per video · public, unlisted (random slug, indexed nowhere),
  or password, checked server side before the manifest URL is handed out.
- Metadata lives in SQLite via better-sqlite3. Media never stays on the VPS disk
  after upload. R2 keys and the Cloudflare zone come from .env.
- A /library page behind basic auth lists every video with duration, size, and this
  month's egress pulled from the Cloudflare GraphQL API, so the bill is never a
  surprise.
- No accounts, no ads, no telemetry, and no tracking pixels in the embed.
- Out of scope: live streaming, monetization, and comments. Do not build a social
  feed or a recommendation surface. Captions can come later from whisper.cpp.
- README: R2 bucket and custom domain setup, why the CDN is not optional, and an
  honest warning that a video going viral is now your invoice, not Vimeo's.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Vimeo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Vimeo indie build

## Goal

Build the smallest trustworthy replacement for the core Vimeo workflow for one developer or a tiny team.

## Scope

Transcode an HLS ladder with ffmpeg, sync it to object storage behind a CDN, and serve unlisted embed pages from your own player.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- live streaming, webinars, and events
- auto captions, chapters, and the accessibility tooling around them
- viewer analytics and engagement graphs
- OTT, pay-per-view, and the monetization stack
- a player QA'd against every browser, smart TV, and embed surface
- traffic spikes absorbed by someone else's bandwidth bill

If those capabilities are essential, use PeerTube instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build me a personal ad-free video host to replace Vimeo. Requirements:

- Node + Express on a small VPS, Cloudflare R2 for the media, Cloudflare in front of
  it. Server-rendered pages, hls.js for playback, no frontend framework.
- I run `pub <file.mov> --title "..."`; ffmpeg builds an HLS ladder at 1080p, 720p,
  and 540p with a master.m3u8 and a poster JPEG, then rclone syncs it to R2.
- Each video gets /v/<slug>: player, title, description, and a copyable embed
  snippet. /e/<slug> is the bare iframe target with no page chrome.
- Privacy is one field per video · public, unlisted (random slug, indexed nowhere),
  or password, checked server side before the manifest URL is handed out.
- Metadata lives in SQLite via better-sqlite3. Media never stays on the VPS disk
  after upload. R2 keys and the Cloudflare zone come from .env.
- A /library page behind basic auth lists every video with duration, size, and this
  month's egress pulled from the Cloudflare GraphQL API, so the bill is never a
  surprise.
- No accounts, no ads, no telemetry, and no tracking pixels in the embed.
- Out of scope: live streaming, monetization, and comments. Do not build a social
  feed or a recommendation surface. Captions can come later from whisper.cpp.
- README: R2 bucket and custom domain setup, why the CDN is not optional, and an
  honest warning that a video going viral is now your invoice, not Vimeo's.

## Required capabilities

- ffmpeg
- object storage (R2, B2, or S3)
- a CDN in front of it
- a small VPS for the pages
- an egress budget you now own

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# Vimeo product brief

## Problem

Hosting your own video stopped being exotic: ffmpeg builds the HLS ladder, object storage holds it, a CDN serves it, and hls.js plays it. For a portfolio or a client reel that is a weekend, and the result has no ads, no upsells, and no platform that can change its mind about your account. What you are actually buying from Vimeo is the delivery layer holding up when 4,000 people open the link at once, plus live streaming, captions, analytics, and a player that has been QA'd against every browser, smart TV, and embed context you will never test. Small library, predictable traffic · build it. Anything with a spike in it · the bandwidth bill is the whole argument.

## Product outcome

Transcode an HLS ladder with ffmpeg, sync it to object storage behind a CDN, and serve unlisted embed pages from your own player.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- ffmpeg
- object storage (R2, B2, or S3)
- a CDN in front of it
- a small VPS for the pages
- an egress budget you now own

## Explicit non-goals for v1

- live streaming, webinars, and events
- auto captions, chapters, and the accessibility tooling around them
- viewer analytics and engagement graphs
- OTT, pay-per-view, and the monetization stack
- a player QA'd against every browser, smart TV, and embed surface
- traffic spikes absorbed by someone else's bandwidth bill

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build me a personal ad-free video host to replace Vimeo. Requirements:

- Node + Express on a small VPS, Cloudflare R2 for the media, Cloudflare in front of
  it. Server-rendered pages, hls.js for playback, no frontend framework.
- I run `pub <file.mov> --title "..."`; ffmpeg builds an HLS ladder at 1080p, 720p,
  and 540p with a master.m3u8 and a poster JPEG, then rclone syncs it to R2.
- Each video gets /v/<slug>: player, title, description, and a copyable embed
  snippet. /e/<slug> is the bare iframe target with no page chrome.
- Privacy is one field per video · public, unlisted (random slug, indexed nowhere),
  or password, checked server side before the manifest URL is handed out.
- Metadata lives in SQLite via better-sqlite3. Media never stays on the VPS disk
  after upload. R2 keys and the Cloudflare zone come from .env.
- A /library page behind basic auth lists every video with duration, size, and this
  month's egress pulled from the Cloudflare GraphQL API, so the bill is never a
  surprise.
- No accounts, no ads, no telemetry, and no tracking pixels in the embed.
- Out of scope: live streaming, monetization, and comments. Do not build a social
  feed or a recommendation surface. Captions can come later from whisper.cpp.
- README: R2 bucket and custom domain setup, why the CDN is not optional, and an
  honest warning that a video going viral is now your invoice, not Vimeo's.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Vimeo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent