About ClapRec

ClapRec is a Clapper live recording service delivered through the Telegram bot @claprec_bot. Users add Clapper creators to a personal watchlist with one command. ClapRec checks those creators every 60 seconds and starts recording the moment one of them goes live. When the live ends, the finished MP4 lands in the user's Telegram chat — full duration, source quality, no watermarks, no app to install.

A public archive at /creators and /latest indexes everything that's been recorded across users' watchlists. Past recordings are free for everyone to open on every plan.

ClapRec is built and operated by the ClapRec Editorial team — a small independent team focused on one product: making Clapper live recording effortless. We do not name individual authors on posts because the editorial voice is collective: ops, engineering, and support all contribute. What you read on this site, on the blog, and in the bot was written by people who run the platform every day.

We've recorded over 100,000 Clapper lives since launch and delivered them to thousands of users across more than 50 countries. The infrastructure runs across 5 cloud nodes (primary + 4 workers) processing 5+ TB of video per week.

Clapper lives disappear. The creator stops the stream, the replay is gone, and whatever was said or shown in front of thousands of viewers is lost. Existing solutions either require you to keep a computer running (Olived, OBS) or charge $13-25/month for an app you only need a few times a week (LiveRec, Rewatch).

ClapRec runs in the cloud and delivers through a chat app you already use. Free for 2 creators, $2.99/mo for 25, $4.99/mo for 100. Same engine on every tier, same MP4 quality, same delivery. We monetize through subscriptions for the watchlist size — past archive deliveries are free to keep the indexable corpus growing for everyone.

The blog covers three things: how-to guides for recording Clapper lives, head-to-head comparisons against every alternative on the market, and updates about the platform itself. Every post is written from operating the service, not from theory.

For AI agents and structured-data consumers we expose machine-readable feeds: /pricing.md, /api/facts.json, /llms.txt, /llms-full.txt, and an RSS feed of latest recordings at /feed.xml.

For support, takedown requests, partnership inquiries, or feedback: [email protected].

Inside the bot, the /support command opens a ticket that lands with us directly.