Record the whole session.
Store it without the storage-server bill.
A custom direct-to-object-storage recording architecture for online meeting platforms with video calls, shared PDFs, interactive whiteboards, synchronized media, annotations, presentations and custom in-session tools.
Capture what your users actually experienced.
Traditional call recordings often preserve only participant audio/video. SessionVault is designed around browser-level composition so the final recording can include the application experience around the call.
Composite Session Capture
Render the meeting room as a controlled browser scene and capture camera tiles, screen share, interactive PDF pages, whiteboards, overlays and synchronized UI states into one timeline.
Direct R2 Ingestion
Encode and transfer recording segments through an S3-compatible multipart pipeline. Large files can be uploaded in resumable parts rather than building a growing permanent archive on your application server.
Session-to-Object Mapping
Store each recording using deterministic object keys and session metadata so your application can associate meetings, users, timestamps, duration, status and recording assets reliably.
Private Playback Gateway
Keep buckets private and deliver authorized access using short-lived signed requests or an application-controlled access gateway. Avoid exposing permanent public recording URLs.
Security-First Storage
Use Cloudflare R2 encryption at rest, TLS in transit, scoped API tokens, origin-restricted CORS, content-type validation and least-privilege application credentials.
Retention Automation
Define lifecycle rules around your business policy: preserve recordings, archive older content where appropriate, or automatically remove expired sessions without manual server cleanup jobs.
Separate capture compute from long-term video storage.
The application server should not become an ever-growing video disk. SessionVault uses an ephemeral capture/encoding layer and moves completed media into object storage.
Designed for large video objects where failed parts can be retried without restarting the entire transfer.
The architecture is designed to move finalized media to the customer’s R2 bucket; transient processing/buffering may still be required during capture and encoding.
Recording access can follow your own user roles, enrollment rules, meeting ownership and business permissions before media is served.
Recording start/stop events, status callbacks, object keys and playback state can be connected to your existing application database and workflow.
Integration is adapted to the capabilities of your existing meeting stack. API and browser restrictions are verified during the technical assessment.
Pay for stored data—not an oversized recording disk.
Cloudflare R2 Standard currently includes 10 GB-month storage, 1 million Class A operations and 10 million Class B operations each month, then charges by usage. R2 Internet egress is currently free.
Using Cloudflare’s $0.015 per GB-month public rate. Actual bills depend on average storage, operation counts and any additional Cloudflare services you choose.
Example: 1,000 GB continuously stored for a month uses 1,000 GB-month. After the 10 GB Standard free tier, storage is approximately $14.85 before any billable request operations.
Estimate monthly R2 Standard cost
Enter average stored video and estimated monthly API operations. The calculator applies the current Standard free tier.
$0
Estimate only. Uses decimal 1 TB = 1,000 GB, Standard storage, and current public R2 pricing. Excludes capture compute, Workers, transcoding, meeting-provider fees and any third-party services.
Your recording pipeline. Your application. Your R2 account.
We engineer the recording and storage workflow around your existing online meeting product rather than forcing your users into a separate recording platform.
Built for technical buyers who ask the right questions.
Does Cloudflare R2 itself record the meeting?
No. R2 is the object-storage layer. SessionVault provides the capture, composition, encoding, upload and application integration that delivers the recording into R2.
Can the recording include whiteboards, PDFs and shared video?
Yes, when those tools can be rendered inside the controlled meeting browser scene. SessionVault is specifically designed for full-session composition rather than only recording isolated participant media tracks. DRM-protected or browser-restricted cross-origin content may require a different integration approach.
Do I still need a large VPS?
You still need application and capture compute appropriate to your workload, but you do not need to keep scaling expensive VPS disk just to hold a growing video archive. Long-term recording storage is moved to R2.
Can recordings be private and viewable only inside my website?
Yes. The preferred design keeps the R2 bucket private and makes playback dependent on your application’s authorization rules using short-lived signed access or an authenticated delivery gateway.
Can users be allowed to watch but not download?
The application can hide download controls and use short-lived authenticated playback URLs. As with any video that a browser is permitted to play, absolute prevention of copying or screen recording cannot be guaranteed; the goal is controlled access rather than a false promise of impossible DRM.
What happens if an upload is interrupted?
Large recordings can use multipart upload so failed parts are retried instead of retransmitting the entire object. The integration can also record upload state, completion callbacks and recovery status in your application.
Turn meeting recordings into scalable application infrastructure.
Keep your online meeting experience exactly where it belongs—inside your product—while moving long-term video storage to a modern pay-as-you-go object-storage architecture.
Discuss your integration →