
Protect your course and paid videos in WordPress: encrypted streaming, a watermark with the viewer’s name, a device limit, courses and pay per view. No licence key.
Aluleth Video Pro shows and protects your videos in WordPress, for online courses, members’ areas and paid content. Add a video once, choose who may watch, and show it anywhere with a block or a shortcode. The file of a protected video moves to a protected folder and plays through short-lived links made for each viewer: no address in the page, no download button, no playing from another site or from a copied link. Files are protected only once the plugin has checked that the protected folder is closed to the web. For stronger protection, your server cuts the video with ffmpeg into an encrypted HLS stream, or you use Bunny Stream, Cloudflare Stream or Mux with signed playback (the plugin says which videos play from a public address). A moving watermark with the viewer’s name or email, and a limit of devices playing at once, stop shared accounts. Then turn videos into courses, sell access to a video with WooCommerce, Aluleth Commerce or FluentCart, collect emails over the video and see where people stop watching. It is a complete plugin: the free Aluleth Video is included, so nothing else is needed, and no licence key.
INSTALLATION
1. In your WordPress admin, go to Plugins › Add New › Upload Plugin.
2. Choose the aluleth-video-pro-x.y.z-marketplace.zip file as you downloaded it (do not unzip it), click Install Now, then Activate.
3. Before the first protected video: in Aluleth › Video › Settings, click “Check the protected folder”. It must say the folder cannot be opened from the web; on Nginx, add the rule shown there, reload Nginx and check again. Files are protected only once this check passes.
4. In Aluleth › Video › Add a video, choose a file of the media library (or paste a YouTube, Vimeo, video or HLS address), choose who may watch and keep “Protect the file of this video” ticked.
5. Add the “Video player” block to a page, or paste the shortcode shown on the video.
6. For encrypted streaming, tick “Encrypted stream” on a protected video (ffmpeg needed on the server). For Bunny Stream, Cloudflare Stream or Mux, enter the keys in Settings › Streaming services and turn on signed playback in the service, as described there (with a check of the unsigned address for each service).
7. Updates: download the new version from WPBay and upload it the same way. WordPress replaces the current version and keeps your videos, settings and statistics.
PLAYER
– One clean player, the same on every theme: chapters, subtitles in several languages, speeds, picture in picture, full screen, keyboard shortcuts, a small player in the corner while the page scrolls, your colour and your logo.
– Light pages: only a poster and a play button load; YouTube and Vimeo load only after the click, with your own copy of their picture.
– Media library files, YouTube, Vimeo, video addresses and HLS streams; audio files get a compact player with their cover.
– Resume where each person stopped (on every device for logged-in people), a stop time, a quality menu, “Still watching?”, A-B loop, timeline previews and a transcript with search.
PROTECTION
– Protected files: moved to a protected folder once it is checked closed to the web (four test files requested over the web, each must be refused), played through short-lived links tied to one browser; no right-click “Save video as”.
– Encrypted HLS (AES-128) in 1080p, 720p and 480p, made by ffmpeg on your server in the background; the key never leaves the server without a valid link.
– Bunny Stream, Cloudflare Stream and Mux with signed playback: only people allowed to watch get an address, and it stops working after the link time; the plugin checks that the service refuses the unsigned address. Without a signing key, playback is public: the editor says so, and a members-only video needs an explicit tick. YouTube and Vimeo videos stay public where they are hosted.
– A moving watermark with the details you choose (name, email, login, user id, IP address, date, site).
– A limit of devices of one account playing at the same time: refuse the new one, or stop the oldest.
– Embeds only on the sites you allow; every other site is refused by the browser.
WHO MAY WATCH
– Everyone, logged-in people, chosen roles, members of Aluleth Membership levels, or people who bought a product of WooCommerce, Aluleth Commerce or FluentCart, with a Buy access button for the others.
COURSES AND ENGAGEMENT
– Playlists and courses: videos in order beside or under one player, lessons counted (“2 of 6 done”) and opened one after the other.
– Layers at the times you choose: a button with a link, a text, or an email form that can pause the video; emails become contacts with your tag and their consent. On media library files, video and HLS addresses and the streaming services; not on YouTube and Vimeo videos, which play in their own player.
ANALYTICS
– Views, viewers, watch time, views per day and how far people watch, for every video or one. No IP address is kept; views of logged-in people are linked to their account, and administrators see them by name and email; views are deleted after the days you set (365 by default).
– Where people stop watching (a curve for each video) and the logged-in viewers with how far they went, over every view of the period; a CSV export of every view, with the login and email of logged-in viewers.
– Tags and events on the contact of a person who watched a video or finished a course.
Honest limits
– No web player can stop a screen recording: the watermark is there to trace it.
– Encrypted streaming needs ffmpeg and background tasks on the server (most VPS and many managed hosts); otherwise use a streaming service.
Requirements
– WordPress 7.0+ and PHP 7.4+.
– On Nginx: one rule for the protected folder (shown in the settings, with the check).
– For encrypted streaming: ffmpeg on the server; or an account of Bunny Stream, Cloudflare Stream or Mux (optional), with its signing key for protected playback.
– For pay per view: WooCommerce, Aluleth Commerce or FluentCart (optional).
DOCUMENTATION
https://market.alulethmarketing.com/docs/aluleth-video/
LIVE DEMO
https://demos.alulethmarketing.com/video/
Changelog:
Aluleth Video Pro 0.1.5 (includes Aluleth Video 0.1.5)
= 0.1.5 =
* Encrypted HLS and protected files: the check of the protected folder verifies the certificate of the site (Aluleth Video 0.1.5). A stream is made, and a file protected, only once that check found the folder closed.
* Needs Aluleth Video 0.1.5 or later; includes Aluleth Video 0.1.5.
Aluleth Video 0.1.5 (included as free/)
= 0.1.5 =
* Protected folder: the check asks for its test files with the certificate verification of WordPress (it no longer turns it off). Over HTTPS, a certificate that is not valid for the address of the site, not trusted or expired gives no clear answer: the folder is not taken as closed, nothing is moved, and the settings say that the certificate could not be verified, with the addresses to check by hand. Answers got while another plugin or a setting turned the verification off are not trusted either. The stored result says whether the certificate was verified.
* The check no longer follows redirects: an answer must come from the address of the test file itself (a redirect, for example from http to https, gives no clear answer, and the settings say to check the addresses of the site).
* Checks made by 0.1.4 (without the certificate verification) are made again before the next file is protected.
= 0.1.4 =
* Encrypted HLS route identity (includes/class-encrypt.php): Encrypt::route() takes the video and the file from the URL captures only ($request->get_url_params()). A query, body or JSON parameter named id or file is refused with 400 before anything is read. The file must match master.m3u8 or v<n>/index.m3u8 or v<n>/seg<nnnn>.ts (Encrypt::FILE_PATTERN, also the route pattern and the playlist rewrite). The key route takes its id the same way. Free stream route (free/includes/class-stream.php): the same for its id (Stream::route_id()).
* Encrypted HLS containment (Encrypt::path()): before reading, the folder of the job is resolved with realpath() and must be a sub-folder of the real protected folder; the file must resolve, with realpath(), to exactly <job folder>/<file>, be a regular readable file, and neither it, its quality folder nor the job folder may be a symbolic link. Otherwise 404. The real path is what is sent.
* Verified private storage (free/includes/class-storage.php): Storage::prepare() writes .htaccess, web.config and index.php and four test files (check.txt, check.mp4, check/seg0000.ts, check/enc.key) and checks that each one is written with its content (WP_Error aluleth_video_guard otherwise). Storage::check() requests each test file over HTTP: closed only if every answer is 401, 403, 404 or 410 without the file content; open if one is served; unknown for no answer, another status (5xx, 3xx left after the redirects followed, 2xx without the content); guard when a closing file cannot be written. Storage::ready() needs a closed check of this folder younger than 7 days (made again otherwise; a check saved by 0.1.3 is not trusted). Storage::protect() and Encrypt::start() call it first: nothing is moved, no folder, key file or segment is written, and the error says why. Filter aluleth_video/folder_closed only for hosts where the site cannot request itself. The key files written for ffmpeg are checked too.
* Setup order: readme Installation, the empty video list, the edit screen and the settings put the folder check before the first protected video; the settings show the HTTP status of each test file and the addresses to check by hand.
* Lead forms (includes/class-layers.php): Layers::lead() requires Videos::published() (and a source that shows layers) before anything is saved, after the nonce and with the audience, honeypot and rate checks unchanged.
* Pay per view (includes/class-purchases.php): Aluleth Commerce: one query joining orders, order lines and products (email or the account's customer, payment_status paid or partially_refunded, line not fully refunded, product post id), no window. FluentCart: one query per chosen product joining fct_orders, fct_customers and fct_order_items (customer email or user id, successful order statuses, payment paid/partially refunded/empty, item not fully refunded), no window. WooCommerce keeps wc_customer_bought_product() (its own full lookup).
* Analytics (includes/class-analytics.php): Analytics::retention_of() and Analytics::viewers_of() aggregate in SQL over every view of the period (no LIMIT 20000); the viewers list is paged (100 a page) with its total. The CSV is written by Analytics::write_csv() from Analytics::batches(): keyset batches of 1,000 by id below MAX(id)+1 taken at the start, each view once, no limit; a batch that cannot be read, or PHP stopping, ends the file with an ERROR line.
* Statistics wording (free/includes/class-screens.php, class-privacy.php, readmes): what a view keeps (video, page, device kind, seconds watched, furthest point, date, a hash of a random browser id, the user id of logged-in people), that administrators see the views of logged-in people (Pro: name and email in the viewer table and login and email in the CSV), how long views are kept (Settings › Statistics), the privacy export and erase tools. The provider caption: YouTube and Vimeo views count the time their player reports.
* Timed layers (includes/class-layers.php, class-screen.php, assets/pro-admin.js): turned off for YouTube and Vimeo (Layers::unsupported()): no layer in the player options, their forms take no email, and the editor shows why and makes the rows inert, also live while an address is typed. Layers stay on files, video addresses, HLS addresses and Bunny Stream, Cloudflare Stream and Mux (all played in the plugin's own video element). Readme and listing say so.
* Provider playback (includes/class-services.php, class-screen.php): Services::signing() is signed, public or incomplete per service. Incomplete (a key id without its key, a key that openssl cannot read) gives no address at all and refuses saving. A restricted video (access other than everyone) with public playback is saved only with "Play it from a public address anyway" (public_ok). The editor shows the state of the chosen service; the edit card of a saved video shows it and the result of Services::direct_check(): on save with signed playback, the unsigned address (Bunny /<id>/playlist.m3u8, Cloudflare /<uid>/manifest/video.m3u8, Mux /<id>.m3u8) is requested; 401/403 = refused, a playlist = open, anything else = unknown. The settings and the readme give the provider setting (Bunny pull zone Token Authentication, Cloudflare requireSignedURLs with a signing key, Mux signed playback policy with a signing key) and the direct-access check for each. Free: YouTube, Vimeo and addresses of other sites are marked as public playback in the editor.
* Uninstall also removes the _aluleth_video_pro_direct meta and the new test files of the folder.
* Requires Aluleth Video 0.1.4 (included).
= 0.1.3 =
* Uninstall (free/uninstall.php): a protected folder is opened only when it is empty. If a protected file cannot be moved back to the media library, or anything else is still in the folder, the .htaccess, web.config and index.php stay, the option aluleth_video_dir stays (also with "delete the data"), each file keeps its _aluleth_video_was meta (the place it came from), and the option aluleth_video_recovery plus a RECOVERY.txt note in the closed folder list what is left. Installing Aluleth Video again finds the folder: the files play as before and move back when their protection is turned off. When every file is moved back, the folder, its files and these records are removed as before.
* Link renewal (free/assets/player.js): when the links of a stream stop working (HTTP 410 for an expired link of this site, 401/403 at a signed streaming service, 404 when the stream is no longer given, or a fatal network error), the player asks the existing authorized source endpoint once for fresh links and goes on from the same second (hls.js startPosition, same speed, same quality). The endpoint checks again that the video is published and that the viewer may watch it. Bounded: one renewal at a time, the old stream stops loading meanwhile, and another renewal is allowed only after the new links delivered a part of the video or playback moved on. A refusal is shown, the stream stops loading and pauses, and it is never retried. The same renewal serves protected files and the browser's own HLS player.
* Playlists and courses (includes/class-playlists.php, assets/pro.js): one list of available lessons, Playlists::lessons() = the published videos in their order, is used to draw the rows, to answer the AJAX navigation, for the order of a sequential course, for "x of y done" and for the course finished. Rows, links (?alvid_video=<id>) and the AJAX request carry the video id, never a position. A lesson that is a draft, private, in the trash or deleted is left out everywhere: it does not shift the other rows, does not block a sequential course and does not count; it comes back at its place when it is published again.
* Requires Aluleth Video 0.1.3 (included).
= 0.1.2 =
* Unpublished videos: a video that is not published (draft, pending, private) gets no playback link. Nothing comes back from the page, from the public source request (admin-ajax "aluleth_video_source"), from the file route, or from the encrypted HLS playlists and key. That covers Bunny, Cloudflare and Mux addresses too. A link given before the video was unpublished stops working. File and stream delivery also check again that the person the link was made for may still watch the video. There is no preview of unpublished videos, for anyone.
* Statistics off: finished lessons and "start again where you stopped" no longer depend on the statistics. Beats are handled in two separate steps after the same checks (published, may watch, ticket, lesson open in a sequential course): Pro's features always, the statistics only when they are on. With the statistics off, the player still sends its beats for signed-in viewers of course lessons or with resume on, and no statistics row is written.
* YouTube and Vimeo lessons: the player follows these videos through the platforms' own player messages (YouTube with enablejsapi, Vimeo's player messages). It knows where they are and when they end, so a YouTube or Vimeo lesson counts as finished and the next lesson of a sequential course opens.
* Protection turned off: a file that is still in the protected folder keeps playing through the protected, authorized path. Its public address is used only once the file is back in the media library (when the video is saved). If that move fails, the file stays protected and keeps playing.
* Device limit: a browser keeps its place only while the video plays.
- Paused or finished players send no heartbeat: the place frees itself after two minutes, and at once at the end.
- Playing again goes through the limit like a new start.
- A player taken off the page (the next video of a playlist) stops all its timers, including the watermark's, and frees its place.
= 0.1.1 =
* Statistics, courses and analytics: the public beat route (/wp-json/aluleth-video/v1/beat) records a view, a position or a finished lesson, and fires the "Watched" and "Course done" tags and events, only for a published video that the viewer may watch (pay per view bought, members, roles or membership levels). A beat for a draft or for a video the viewer may not open writes nothing and fires no hook.
* Each beat carries a ticket that comes with the player, which is printed only for people who may watch the video; a beat without it is refused.
* Courses that open their lessons one after the other: a lesson counts as finished only once it is open for the viewer.
* Uninstall: the timeline previews (uploads/aluleth-video-previews/ and the _aluleth_video_pro_previews meta) are always deleted, on every site of a network. With "Also delete the data", the playlists and courses (aluleth_vplaylist and their meta) and the finished lessons and positions of the users (_aluleth_video_pro_done, _aluleth_video_pro_pos) are deleted too. Media library files are never touched.
* Privacy: the finished lessons, the positions and the devices of a user are in the WordPress export and erase tools.
= 0.1.0 =
* First release on WPBay: one complete plugin, the free Aluleth Video 0.1.0 is included (nothing else to install, no licence key). If Aluleth Video is already installed as its own plugin, that one is used with its videos and settings.
* A light player for media library files, YouTube and Vimeo (loaded on click), video addresses and HLS, with chapters, subtitles, speeds, picture in picture, a corner player and statistics without personal data.
* Protected files played through short-lived links, who may watch (everyone, logged-in people, roles, membership levels, buyers of a product).
* Encrypted HLS (AES-128) made with ffmpeg on the server, Bunny Stream, Cloudflare Stream and Mux with signed addresses, a watermark with the viewer's details, a limit of devices playing at once and embeds on chosen sites.
* Resume, stop time, quality menu, "Still watching?", A-B loop, timeline previews, a transcript with search, layers (buttons, texts, email forms), playlists and courses, pay per view with WooCommerce, Aluleth Commerce or FluentCart, and analytics with tags and events on contacts.
Only logged in customers who have purchased this product may leave a review.
Support by Aluleth
Aluleth supports this product through WPBay
Questions are handled in WPBay's private ticket system, keeping your purchase details and support conversation together.
After purchase, open this item in My Downloads and choose Get Support.
What support includes
- Answers to product-related questions
- Help with reported bugs and issues
- Guidance for included third-party assets
What support does not include
- Customizations or new features
- Installation or setup services
Maintenance snapshot
See recent updates, compatibility, support, and developer activity.
- Updated today
- Developer active recently
- WPBay support available
- WordPress 7.1 tested
Snapshot updated 16 hours ago
View details Hide details
Maintenance details
This is maintenance data. It does not measure product quality or sales.
- Last update Updated today
- Compatibility WordPress 7.1 tested · PHP 8.3 tested, one version behind · WooCommerce 11 tested
- Releases 6 releases in the 5 days since listing
- Developer activity Developer active recently
- Support No recent support tickets to measure
- Docs and demo Documentation available · Changelog available · Demo available
How this snapshot works
Plugin Health
The score is out of 100 and uses data WPBay can check. Ratings, popularity, and sales are not used.
- Last update 30 points
-
Plugins receive full recency points under 30 days, then step down at 90, 180, 365, and 545 days.
- Compatibility 20 points
-
WordPress, PHP, and WooCommerce (when relevant) are scored separately. The latest two PHP lines count as current. Nearby previous versions keep most of the points.
- Current version 100%
- One version behind 75%
- Two versions behind 50%
- Three versions behind 25%
- Older or not listed 0%
- Releases 15 points
-
One release earns 10, two or three earn 13, and four or more earn 15. Each accepted product ZIP counts once; reprocessing the same upload and listing-only edits do not count.
- Developer activity 15 points
-
Based on WPBay login and dashboard activity. Exact last-login dates are never shown.
- Support 15 points
-
There are no recent WPBay tickets to measure.
- Docs and demo 5 points
-
Documentation: 2. Changelog: 1. Working demo or preview: 2.
Score ranges
- 90–100 Excellent
- 75–89 Healthy
- 60–74 Fair
- 40–59 Needs attention
- 0–39 Limited
Long gaps
WPBay also checks for long gaps between updates, developer activity, support replies, and releases. Buyers do not see this score.
- Time since update 35 points
- Last developer activity 25 points
- WordPress compatibility 15 points
- Support replies 15 points
- Fewer releases 10 points
More by Aluleth
Explore more bestselling products from this creator.

Reviews
There are no reviews yet.