Bring the video you have.
Upload directly or import a video from connected storage.
Upload videos directly or import them from your storage. VEXOR handles transcoding, secure playback, and delivery through one API.
One clear path from the video you already have to secure playback inside your product.
Upload directly or import a video from connected storage.
VEXOR transcodes your source into adaptive HLS renditions so playback can match the viewer’s network.
Serve AES-128 encrypted HLS with short-lived playback tokens, and use signed webhooks to react when assets are ready.
Keep originals in your storage or upload directly. VEXOR processes, protects, and delivers adaptive playback through one API.
Upload, playback, and usage tracking work together in one video pipeline.
Adaptive renditions help videos start smoothly and adjust quality as a viewer’s connection changes.
Encrypted HLS and signed, short-lived playback access help you control who can watch.
Top up by card and track your VEXOR balance and usage in one place.
Use the Node.js / TypeScript or Python SDK on your server, then add the React player or WordPress plugin. Your API key stays server-side.
Server uploads, S3 imports, playback tokens, and signed webhook verification.
Server uploads, asset status, playback token authorization, and webhook verification.
Adaptive HLS playback, accessible controls, dynamic watermark, and token auto-refresh.
Connect your Vexor account in wp-admin, pick an asset, and embed it in posts or lessons.
Automate video transcoding, cloud storage imports, and PR player previews in CI/CD.
What VEXOR does, where your originals stay, and how playback reaches your product.
VEXOR is developer-first video infrastructure for modern product teams. Instead of configuring custom FFmpeg servers, storage adapters, player licensing, and manual token distribution, VEXOR provides a single unified REST API. It ingests source videos, transcodes an adaptive HLS rendition ladder, enforces AES-128 segment encryption, and delivers smooth playback across global edge networks.
No. VEXOR supports direct imports from your existing cloud storage—including Amazon S3, Google Cloud Storage, Azure Blob Storage, Cloudflare R2, Oracle Cloud, and Quat. Simply pass the bucket name and object key; VEXOR reads the source file for transcoding, while your original file remains securely in your own storage bucket.
Yes. In addition to VEXOR’s managed edge origin, you can connect your own S3-compatible storage buckets and configure custom CNAME domain routing to satisfy enterprise data sovereignty, compliance, and corporate branding requirements.
Every video is segmented into single-file byte-range HLS and encrypted using AES-128 CBC with rotating segment initialization vectors. Decryption keys are served through an authenticated key server that requires an Ed25519-signed JWT with a 5-minute expiration window. Without an active authorized session from your backend, video segments cannot be decoded or stitched into playable files.
Your backend remains the sole authority for viewer permissions. When an authenticated user opens a video in your app, your server checks their status (subscription, purchase, or role), calls VEXOR to mint a short-lived playback token, and hands that token to the frontend player. The player requests decryption keys with that token, ensuring direct stream URLs cannot be shared or stolen.
Direct manifest and segment URLs cannot be played in isolation. Because manifest chunks and decryption keys are guarded by time-limited, signed JWT tokens tied to your configured playback policy, shared or intercepted URLs expire within minutes and refuse unauthorized requests.
VEXOR implements the open tus protocol over HTTP for video ingest. If a user’s internet connection drops midway through a 4GB upload, the client automatically pauses and resumes from the exact byte offset when connectivity returns, avoiding timeout failures and wasted bandwidth.
VEXOR automatically transcodes uploaded videos into an optimized 6-step single-file byte-range HLS ladder: audio-only (64 kbps), 240p, 360p, 480p, 720p, and 1080p. Single-file byte-range HLS drastically reduces storage inode overhead and allows edge CDNs to cache and serve byte ranges with near-instant seek times.
VEXOR emits signed HTTP webhooks (such as video.upload.completed and video.asset.ready) with HMAC-SHA256 signatures and timestamp replay protection. If your webhook receiver is temporarily down, VEXOR automatically retries delivery with exponential backoff through a persistent dead-letter queue.
VEXOR uses a transparent pay-as-you-go model with no monthly recurring minimums. Wallets track balances in integer minor units (ETB santim or USD cents). Processing charges are deducted only after transcoding succeeds, and uploads are pre-validated against your available balance. Balances can be topped up via Telebirr (ETB) and Polar card packs (USD).
We provide official server SDKs for Node.js / TypeScript (@vexor-video/sdk) and Python (vexor), an embeddable React & Vanilla HLS Player SDK with automatic bitrate switching, an official WordPress plugin with shortcode support, an official GitHub Action (vexor-video/action@v1) for CI/CD test previews, and a Model Context Protocol (MCP) server for AI agents.
Explore the documentation, inspect code examples, test the MCP server, or review our player SDK.
Create your developer account and bring your first video into the pipeline.
Get started with Vexor