Parallel by default
Ingest scales with the hardware you gave it. Multi-core transcode and GPU-accelerated encode/decode mean a full shoot day clears in the window you actually have, not overnight.
1303 Systems / Custom software
Get footage into your MAM without babysitting it.
IngestR automates the path from card, watch folder, or delivery drive into Iconik and your archive — transcode, proxy, metadata, registration, and verification — on your hardware, on your schedule.
Running in production at Division I athletics and post facilities. Deploys on-prem or in your VM environment.
The problem
The ingest gap nobody budgets for
You bought the MAM. You bought the storage. What sits between them is usually a folder of shell scripts written by whoever had time, held together by one person who knows why it breaks.
- Editors waiting on proxies while someone re-runs a transcode by hand
- Assets in Iconik with no usable metadata, because the wire format was close but not correct
- Half-finished jobs that have to start over from the top when a network share drops
- Archive copies nobody verified, discovered months later when a restore fails
- One person who understands the ingest workflow, and no documentation if they leave
IngestR replaces that layer with something specified, repeatable, and supportable.
How it works
Four stages, no manual steps
01
Watch
Point IngestR at a watch folder, mounted card, or delivery path. It detects new media, waits for writes to settle, and queues the job. Preflight checks validate configuration and connectivity before anything moves — you find out about a bad credential at startup, not three hours into an ingest.
02
Process
FFmpeg orchestration handles transcodes, proxy generation, and keyframe extraction against profiles you define. Jobs run in parallel across available cores and GPUs, so a card of camera-original files isn't processed one at a time.
03
Register
Assets land in Iconik with correct format components, proxy and keyframe associations, spritesheet keyframe maps, and the metadata you mapped — populated at ingest, not backfilled later.
04
Verify
Webhook-driven validation confirms each asset landed complete and playable, tracked in a local job database. Interrupted runs resume where they stopped instead of restarting. Every job leaves an auditable record.
Built for the failure modes
The boring parts are the product.
IngestR turns the operational details that usually live in someone's head into a workflow the whole team can trust.
Resume, don't restart
Network share drops. Storage goes offline. A run gets killed. IngestR picks up from the last completed step — the work already done stays done.
Preflight validation
Configuration, credentials, mount points, and target availability are checked before the first file moves. Failures surface at launch with a specific cause.
Verified, not assumed
Auto-validation confirms assets registered correctly and proxies play. Job state is persisted, queryable, and exportable — so "did that ingest actually finish?" has an answer.
Archive-aware
IngestR treats archive as part of ingest, not a separate chore. Native support for StorNext Storage Manager policy targets, with Archiware P5 integration shipping soon through the same backend abstraction.
Configuration, not code
Workflows are defined in configuration files under version control. New show, new season, new client — copy a profile and adjust it. No forked scripts.
Integrations
Fits the stack you already run.
Asset management
Iconik (native REST integration — format components, proxies, keyframes, metadata mapping)
Primary storage
Quantum StorNext, standard SMB/NFS shares
Archive
StorNext Storage Manager (LTO and object), Quantum ActiveScale, Archiware P5 (shipping soon)
Media
FFmpeg-based transcode and proxy generation across broadcast and camera-original formats
Deployment
Linux on bare metal or hypervisor; GPU passthrough supported for hardware encode/decode
Don't see your stack? IngestR's backend abstraction is built to be extended — talk to us about your environment.
Who it's for
When every camera brings a deadline.
University athletics production
Practice, games, and press flow in from multiple cameras on the same day, every day, in season. IngestR gets all of it tagged, proxied, and searchable in Iconik before your editors sit down — and pushed to archive without a separate workflow.
Broadcast and live production
High-volume, deadline-bound, no room for a manual step. Parallel processing and resume behavior are built for the days when everything arrives at once.
Post-production
Client deliveries in every format and naming convention. Define the profile once; every job after that lands consistent.
Corporate and enterprise video
A small team producing a lot of content. IngestR is the ingest headcount you don't have to hire.
Proof
Built in production, not in a lab
IngestR came out of real deployments — designed by the systems integrator who was already building and supporting these environments, refined against the failure modes that actually occur in high-volume media operations.
"Before IngestR, our archive was storage we paid for and couldn't search. Now it's a library. Everything we shoot goes in automatically, and the back catalog we never had the staff to process is in there with it."
100s
of thousands of assets ingested in weeks
90%
fewer manual touchpoints
Pricing / licensing
One deployment. One accountable partner.
Licensed per deployment. Includes installation, workflow configuration for your environment, and support. Annual maintenance covers updates and new integrations as they ship.
We scope every deployment against your actual storage, MAM, and archive topology before quoting. No seat counts, no per-asset metering.
Request a quote ↗FAQ
The useful answers, upfront.
Does IngestR replace our MAM?+
No. IngestR feeds your MAM. It's the automation layer between acquisition and Iconik, and between Iconik and archive.
Where does it run?+
On your infrastructure — bare metal or virtualized. Your media never leaves your environment.
What if our workflow is unusual?+
Most are. IngestR is configured per deployment, and the storage and archive backends are abstracted specifically so new targets can be added. Bring us the workflow you have.
Do we need GPUs?+
Not required, but they help. IngestR uses hardware encode/decode when available and falls back to CPU when it isn't.
What happens when something fails mid-ingest?+
The job stops, the failure is logged with cause, and the run resumes from the last completed step when you restart it. Nothing silently half-finishes.
Who supports it?+
1303 Systems — the same team that built it and deploys the storage and MAM infrastructure around it.
Next step
Stop paying an editor to be an ingest operator
Tell us what your current ingest path looks like. We'll show you what it looks like automated.
Schedule a walkthrough ↗[Download the IngestR technical overview (PDF) — coming soon]