Aeion Cut + Aspera, S3, FTP, Watch Folders
Production studios move terabytes of media daily — from camera cards through DIT carts to editorial bay to post-house to delivery. Aeion's ingest pipeline orchestrates all the major paths: Aspera FASP (10-100× faster than FTP for large files via UDP-based protocol), S3-compatible direct (AWS S3, R2, Backblaze B2, MinIO, etc.), FTP/SFTP fallback, watch folders for auto-ingest from monitored directories, and a Showrunner live ingest server for live show production. Multi-source ingest with auto-proxy + auto-cataloging.
Why High-Speed Ingest Matters
`
Aspera FASP Ingest
```typescript
S3-Compatible Direct Ingest
```typescript
Watch Folders + Showrunner Server
```typescript
Auto-Proxy + Cataloging
```typescript
FAQ
No — Aeion's Aspera support is a client-side integration (the IBM `ascp` CLI, shelled out to under the hood), not a hosted Aspera server. You bring your own Aspera-enabled endpoint (Aspera Node, Faspex, or Shares) and licensing; Aeion pulls from it.
Use S3 direct or HTTP-based upload. For under 50 GB transfers, HTTP is fine. For >100 GB, S3 multi-part upload is reliable. Aspera is for studios moving multi-TB daily.
Card → DIT cart → Aspera/S3 to Aeion is most common. Some cloud-native cameras (Blackmagic Pyxis 6K, ARRI Alexa 35) can push directly to S3 via Wi-Fi/cellular for IDM (instant data management).
Aeion gets read/write access to your bucket via IAM. Aeion processes media (proxy generation, etc.) but stores metadata only. Data sovereignty preserved.
Aeion-managed bucket: included in the $29/mo flat rate up to 500 GB. BYO S3: customer pays cloud provider directly (~$0.015-0.025/GB/mo for S3 Standard). For >500 GB, BYO almost always cheaper.
Yes for BYO S3. Aeion respects lifecycle policies; archived files take 12+ hours to restore. Plan around archive retention for project archives.
Yes. Full-res in your S3 or Aeion-managed; proxies in fast access tier (smaller files, faster IO). Different cost profile.
Aspera uses UDP port 33001 (default). Firewall rules required. For maximum throughput, dedicated 10 Gbps fiber recommended. Studios typically have this infrastructure.
Self-hosted Aeion deployment + NFS/SMB storage. Air-gapped setups supported via a custom enterprise arrangement.
Watch folder for human-workflow integration (editor drops file in, it appears). API upload for automated systems (cloud-rendered file pushed to Aeion automatically).
Aeion calculates and verifies a checksum (MD5/SHA-256/xxHash) on every file at ingest. Catches storage corruption + transfer errors.