Unlock your dashboard

No. Recordings made through the widget are captured and encoded in the visitor's browser, then synced straight to the storage bucket you connect, whether that's your own S3 compatible bucket, Google Drive, Dropbox, or OneDrive. Drefly's servers are never in that path.

Both recording modes upload straight from a browser to your bucket rather than through Drefly's servers. In This tab mode, the visitor's browser on your own domain uploads directly. In New page mode, the recording happens on report.drefly.pro and is sent to your bucket from there. Either way, that's a browser on a different origin talking to your bucket, and a bucket's CORS policy is what allows that. Without the right CORS settings, browsers block the upload, playback, download, and share requests needed to make any of this work.

This tab records the current page directly, with no redirect, which works well as long as the customer's flow stays on one page. New page opens a separate tab on report.drefly.pro to record, then sends the finished recording back to your bucket once the customer stops.

This tab recording only survives if the page never navigates away, the widget warns the browser before it leaves while a recording is active. If the customer's flow includes redirects, whether from routing frameworks like React or Angular changing views, or the page reloading, This tab recording can get interrupted or asked to stop. New page avoids that entirely because the recording runs on its own separate page and can capture the whole flow, redirects included.

When New page opens, it carries your company name, brand color, and favicon into the page, so what a customer sees is branded to your company, not Drefly. That's why New page needs report.drefly.pro specifically, it's the page built to render your company's branding while still handling the recording and syncing the result to your bucket, which is also part of why the CORS setup matters there.

In This tab mode, yes, if they try to navigate away while a recording is active, their browser warns them before leaving, since navigating away would end the recording. New page mode avoids this since it records on its own separate page and isn't affected by navigation on your site.

report.drefly.pro is the customer-facing side, the recorder your site's visitors actually use once you embed the widget, whether that's This tab on your own page or New page on its own branded tab. Whenever a recording finishes, it syncs straight to the storage bucket you configured for your company. developer.drefly.pro is where you manage that setup: connect storage, review what your customers recorded, and share, download, convert, or delete their recordings.

Yes. Open Recordings for a company and you can play back what was collected, share it, download it in any supported format, convert it, or delete it, all from developer.drefly.pro.

Any format in the dropdown: MP4, WebM, MOV, MKV, AVI, FLV, or GIF, converted right in your browser. AVI is flagged slower since it takes a bit longer to encode than the others.

No. Sharing converts the recording in your browser and saves the copy back into your widget's storage bucket, giving you a link. If you share via drefly.pro, playback pipelines from your bucket through Drefly's server to the viewer's browser without ever being written to disk there, Drefly is a pass-through, not storage.

Yes. You can edit a company's storage connection, allowed domains, and branding at any time from developer.drefly.pro, and changes apply to the widget immediately.

Yes. Your developer account can hold as many companies as you manage, each with its own domain, branding, and storage bucket.

No. It uses the same passkey you already set up for your Drefly drive, there's no separate key to create.

No. There's no signup fee and no monthly cost.