Seedance 2.0 Comes to Aveiro — With Video Uploads and Bunny.net Under the Hood
Aveiro's AI video generation now runs on ByteDance's Seedance 2.0, released alongside native video uploads and Bunny.net-powered storage and delivery. Here's what the new model supports and how the pieces fit together.
Aveiro's AI video generation now runs on ByteDance's Seedance 2.0 model. It shipped alongside two infrastructure upgrades: native video uploads (up to 200 MB, straight from the editor and dashboard) and Bunny.net storage and CDN delivery for every video on the platform.
Seedance 2.0 powers Quasar video generation
When we launched AI video generation, clips were generated by the first-generation Seedance models from ByteDance. With this release, the Quasar Lite video tier moves to Seedance 2.0 — ByteDance's latest video generation model, which we run through BytePlus ModelArk.What the Seedance 2.0 integration supports in Aveiro today:
Text-to-video — describe the clip in the video picker and generate, no footage needed
Reference images — optionally attach an image to guide the first frame, so clips match your site's look or an existing visual
Synced audio generation — clips can come with generated audio, not silent loops
5 or 10 second clips at 720p, 16:9 — sized for hero sections, covers, and social loops
Async background jobs — generation runs while you keep editing; the picker shows a pending tile until the clip lands in your media library
Per-second credit metering — a clip costs its duration times the tier's rate, from the same AI credit pool as images and chat
The Quasar Max tier (Seedance Pro) is unchanged: higher-quality cinematic motion and audio sync for plans with Max access. Two tiers keep cost a conscious choice — a draft social loop doesn't need launch-video spend.
Native video uploads
Generation is only half the story — plenty of you already have footage. This release adds direct video uploads everywhere media lives in Aveiro:
Upload files up to
MP4, WebM, or MOV
200 MB
Available in the site editor's video picker and the org-level media library, so one upload is reusable across sites
Uploads go directly from your browser to storage via a prepare-and-confirm flow — they never squeeze through an application server's request-size limits
Registered video URLs used in social posts get the same treatment: Aveiro ingests a copy into your org's video storage, so a scheduled post still publishes even if the original URL disappears before dispatch. Re-registering the same URL converges on the same stored copy instead of piling up duplicates.
Bunny.net for storage and delivery
All of this sits on Bunny.net, which now handles video storage and CDN delivery for Aveiro:
Regional storage — uploads land in a storage zone close to you, with region-aware endpoints from Falkenstein to Sydney
Global CDN — every video is served from Bunny's edge network, so a clip on your homepage loads fast whether your visitor is in Lisbon or Singapore
One pipeline — uploaded footage, ingested social video, and Seedance-generated clips all flow into the same storage and get the same delivery
0:00 / 0:00
0:00 / 0:00
0:00 / 0:00
0:00 / 0:00
The infrastructure behind it
A note on the services we're scaling on, because we think it's worth being transparent about the stack:
ByteDance — the Seedance model family (via BytePlus ModelArk) is our video generation backbone. Running inference on their managed platform means we scale generation capacity without operating GPU fleets ourselves.
Bunny.net — storage zones and a global CDN give us regional upload targets and edge delivery at a price that lets us offer generous video limits.
Aveiro's job is the publishing pipeline — editor, media library, credits, review flows. For the heavy lifting underneath, we'd rather integrate the best infrastructure than rebuild it.
Try it
Open a page in the site editor and add or edit a Video element.
Upload a file (MP4, WebM, or MOV up to 200 MB) — or switch to Generate and describe a clip.
For generation, pick Quasar Lite (Seedance 2.0) or Quasar Max, optionally attach a reference image, and keep editing while the job runs.
Place the finished video like any other media — it's already on the CDN.
