Frequently asked questions
Answers for evaluating and operating the free JetEncode AWS edition.
What does JetEncode cost?
The software charge is $0. Your selected cloud provider bills infrastructure and services separately.
Which AWS charges should I expect?
Common categories include EC2 runtime, EBS, S3 storage and requests, snapshots, data transfer, public IPv4 addresses, and monitoring.
Which instances should I use?
Start with a current-generation compute-optimized instance with at least 4 vCPUs, then benchmark representative jobs and scale for concurrency.
Which clouds are supported?
AWS is the current launch target. Google Cloud, DigitalOcean, and Akamai Cloud images are coming soon.
Does JetEncode require a license key?
No. The free AWS edition requires no JetEncode license, account registration, or email activation.
How does JetEncode access Amazon S3?
Attach a least-privilege IAM instance role to EC2. JetEncode must use the AWS default credential provider chain; do not place AWS access keys in a job payload.
Is support available 24/7?
No. Email support targets an initial response within two business days; this is not a 24/7 SLA.
Does JetEncode receive my video?
JetEncode runs in your cloud account. Each job connects to the source and destination services you configure.
How is this different from a managed transcoding service?
JetEncode runs on compute you operate, so you control the cloud account, network boundary, storage path, and capacity.
How is this different from FFmpeg?
FFmpeg is a media toolkit. JetEncode is a packaged transcoding workflow with an HTTP API, durable queues, parallel workers, and output recipes.
How do upgrades work?
Launch and test the new Marketplace AMI version separately, then move integrations to it. Retain the prior version for rollback.
Can I restore JetEncode state?
JetEncode currently has no supported restore procedure for bundled PostgreSQL state. Keep durable media in object storage and rebuild from a known AMI version.
How fast is it?
No benchmark should be published without a reproducible workload, version, instance, Region, storage path, and settings.
What should I send support?
Send version, Region, instance, time, job ID, error, steps, and redacted logs—never secrets or private media.