1 comments

  • alexneamtu 8 hours ago ago

    Hey HN, I built SendRec because I kept running into the same problem at EU companies: teams want async video messaging (record screen, share link, done), but every option sends the data through US infrastructure. Loom, Vidyard, CloudApp -- they all route through AWS us-east or GCP. For teams subject to GDPR, Schrems II, or sector-specific regulations (finance, healthcare, public sector), that is a compliance headache that legal departments solve by banning the tool entirely.

    SendRec is a self-hosted async video platform. You record your screen in the browser, the video uploads to your own S3-compatible storage, and you get a shareable link. That is it. No data leaves your infrastructure.

    Tech stack: Go backend (chi router, pgx for PostgreSQL), React + TypeScript frontend compiled into a single binary, S3-compatible storage (tested with MinIO). The whole thing deploys with docker compose up -- PostgreSQL, MinIO, and the app. Takes about five minutes.

    What is in the box right now: screen + mic recording, shareable links with 7-day expiry (extendable), anonymous view counts (IP+UA hashed, no PII stored), server-side thumbnails via ffmpeg, JWT auth, free tier with configurable limits (25 videos/month, 5 min max by default -- set to 0 for unlimited on self-hosted).

    It is live at https://app.sendrec.eu on a Hetzner CX33 in Helsinki. That instance runs the free tier. Licensed AGPLv3.

    I am looking for feedback, particularly from anyone at EU organizations who has dealt with the compliance side of video tools. What is missing? What would make this usable for your team?

    GitHub: https://github.com/sendrec/sendrec

    Live app: https://app.sendrec.eu

    Blog (architecture posts): https://sendrec.eu/blog/