Built a free alternative to Loom/BugHerd for customer bug reports
Hey IH đź‘‹
I built Drefly's Record widget because I was tired of asking customers to describe bugs in text. "It's broken" isn't a bug report. A 30 second recording is.
What it does
- Drop in one script tag, your users can record their screen and hand it to you instantly
- No signup for them, no account creation, no friction
- Recordings go straight to your own S3/R2/Backblaze/Spaces/Wasabi/GCS/MinIO bucket, never our servers
- Your branding on every screen, not ours
- PIN protected share links, analytics, and comments on every recording
- AI summarizer coming soon
Why self hosted storage
Didn't want to be another company holding customer data hostage on a server they can't see. If it's your bucket, it's your data, full stop, and you're not paying us per seat or per recording.
It's completely free right now. Setup guide walks through connecting a bucket, CORS, and going live in about 5 minutes: https://developer.drefly.pro
Also built a standalone version if you just want a recorder without integrating anything: https://recordings.drefly.pro/
Would love feedback, especially from anyone who's dealt with the "bucket permissions are a pain" problem before, curious if the CORS setup step is the sticking point for people.
The “it’s broken” bug report problem is painfully real. The self-hosted storage approach is interesting too, especially for teams that already have their own bucket setup.
Curious how many people actually get stuck on the CORS/bucket configuration versus just not wanting to touch infrastructure at all.
Thanks Aryan, appreciate you digging into that. Honestly it's a bit of both from what we've seen. Some people get through the bucket setup fine but trip up on the CORS config specifically, others just don't want to deal with any infrastructure at all. We don't host anything ourselves though, we just support and guide people through doing it on their own bucket.
On CORS specifically, it's just about allowing whichever domains you want to record from, so it's more of a one time config step than anything ongoing.
We just added a blog post called "How to Integrate Drefly Into Your Company" that walks through the integration with every possible step, so hopefully that clears up the CORS confusion for anyone stuck there. Also put together a full YouTube walkthrough if that's easier to follow, linked right in the post.
Worth mentioning too, the self hosted approach is really about privacy and data ownership at its core. We don't want to be another company sitting on customer data we can't be trusted with. Our privacy policy on the site spells this out clearly, we don't own any of it, it's entirely yours.
If you or anyone else runs into issues setting it up, our support email on the site is always open, happy to help debug directly.
That makes the distinction clearer. The fact that some users avoid infrastructure entirely while others are fine with it seems worth watching. I’d be interested to hear what you learn as more teams try Drefly.