Qencode + Wasabi

Transcode and store video on Wasabi — S3-compatible hot storage with no egress fees and no API call fees.

Overview

What This Integration Does

Qencode integrates with Wasabi hot cloud storage as both a source and destination for video transcoding jobs. Wasabi provides an S3-compatible API with predictable pricing: no egress fees, no API call fees, and no tiers to manage. Pull source video from any Wasabi bucket, transcode it, and write the output back automatically. For video workflows that need hot storage at a fraction of AWS S3 pricing, Wasabi delivers the simplest cost model available.

Architecture

How the Integration Works

Source

Wasabi bucket or URL

Qencode pulls your source video from a Wasabi bucket (or any URL).

Process

Transcode & package

Qencode transcodes, encrypts, and packages the video per your job configuration.

Deliver

Destination bucket

Encoded files are written directly to your destination Wasabi bucket.

Serve

Via CDN of choice

Serve via a CDN of your choice (Cloudflare, Fastly, CloudFront), or any HTTP endpoint.

Getting Started

Setup Steps

  1. Create your Wasabi bucket

    In the Wasabi Console go to Buckets → Create bucket, select bucket name and preferred region. All storage is hot by default — no tier selection required.

    This step is completed in the Wasabi Console — see Wasabi documentation

  2. Generate access keys

    In the Wasabi Console, go to Access Keys → Create Access Key and create a new access key and secret key. Scope permissions using Wasabi IAM policies if you want granular control.

    Store your access key and secret as environment variables. Never commit credentials to source control.

  3. Add credentials to Qencode

    In Transcode Media, go to Third-Party Storage, then choose Wasabi. Enter your Bucket Name, Region name, Access Key ID, and Secret Access Key. Enable Public permissions only if needed.

  4. Set destination in your transcode job

    In your API request, set the destination parameter to your Wasabi bucket URL with the desired output path. Use the S3-compatible endpoint format.

  5. Verify the output

    After the job completes, check your Wasabi bucket for the encoded files. Qencode sends a webhook notification when writing is complete.

Implementation

Code Example

Request Example

MP4 output to Wasabi

{
  "query": {
    "source": "https://s3.[region].wasabisys.com/my-source-bucket/folder/input.mov",
    "format": [
      {
        "output": "mp4",
        "destination": {
          "url": "s3://s3.[region].wasabisys.com/my-bucket/folder/output.mp4",
          "key": "YOUR_ACCOUNT_KEY",
          "secret": "YOUR_ACCOUNT_SECRET",
          "permissions": "public-read"
        }
      }
    ]
  }
}

Replace placeholder credentials with your actual Wasabi access key and secret. Use environment variables in production.

For a step-by-step walkthrough, see Tutorial: Wasabi Integration

Pricing

Cost Context

Storage costs at Wasabi

  • Hot cloud storage runs approximately $0.0059/GB/month with no egress fees, no API call fees, and no minimum storage duration on the pay-as-you-go plan.
  • All storage is hot — no tiers to manage.
See Wasabi pricingfor current rates.

Estimated total cost per hour of 1080p video

Qencode transcoding (HLS, H.264)

~$1.80


Wasabi storage (1 GB encoded output)

~$0.006/mo


Egress (100 viewers × 1 GB)

$0.00 (no egress fees)

Estimates based on standard configurations. Actual costs vary with codec, resolution, and encoding features. See Qencode pricing

We love creating powerful solutions that are aligned with the needs of your business.

Please send us a message if you have a question or Schedule a call for a demo to discuss your integration.

Let's talk

First Name
Last Name
Company
Email
Your Message

Contact us with any questions. We'd love to help.

Los Angeles, CA - (HQ)

San Francisco, CA

New York, NY