Nexus is the router between your vendors and the systems you already run. Deliveries arrive, get verified, assemble into complete assets, and land in each DAM with the right metadata, tracked file by file.
A shot is thousands of frames arriving one at a time. Nexus assembles them and releases one complete asset, so your library shows the whole shot or flags the delivery for a human, never something in between.
Each file reports its own status back to the sender, from received to landed. When a vendor asks where a delivery stands, the answer is on screen, not buried in an email thread.
Files are checksum verified on arrival. A mismatch is retried, then set aside for review. It is never silently stored, so what is in your library is what was actually sent.
Nexus writes each DAM the record it expects: folder tags, source paths, parent-child links. Your DAMs stay the creative front door, and they stay authoritative.
Frames arriving individually register idempotently, and the sequence releases exactly once as a single, complete asset behind a lock. A completion marker prevents re-accumulation. Sequences that stall past a 4-hour sliding inactivity window are flagged for operator investigation instead of landing partial.
Every file that arrives with a digest is verified with md5 or sha-256. Mismatches are retried, then dead-lettered, never silently stored. Duplicate skip is opt-in and keyed on the preserved source path, and checksum-level duplicate detection lives in the Gateway catalog.
A lifecycle event stream flows back to the sending system for every file: 10 event types, from received through retry-scheduled. The console tracks 5 stages live with order-guarded updates, and per-stage timings and transfer-rate history persist. Operators can pause, resume, and tune concurrency mid-run without a restart.
Per-message routing runs against a managed multi-DAM endpoint registry. Each record is tailored to its destination: folder tags, source-path preservation, parent-child associations, and sync or async AI enrichment selected by file type, confirmed by signed, idempotent completion webhooks. Unknown destinations fail terminal rather than land in the wrong place.
Cross-system metadata sync with managed credentials, field mapping through a transformation and validation engine, and AI-suggested mappings with confidence scores that your team applies. Change detection republishes only deltas. Timezone-aware cron scheduling runs it all with concurrency limits and failure notifications.
Counts and limits below are verified against shipping code. The full capability datasheet is available on request.
Nexus assembles frames that arrive individually and releases them as one complete, atomic asset. Frames that arrive individually are assembled and released as one complete, atomic asset. Registration is idempotent, release is lock-protected and exactly-once, and a completion marker prevents re-accumulation. A sequence that stalls past a 4-hour inactivity window is flagged for an operator, so your DAM receives one whole asset, not a trickle of frames.
No. Nexus is the routing layer between intake and the systems you already run. It writes each destination a tailored record with folder tags, source paths, and parent-child associations, and your destination systems stay authoritative.
Every file that arrives with a digest is verified with md5 or sha-256. A mismatch is retried, then dead-lettered, never silently stored. A per-file event stream with 10 event types reports each file's status back to the sending system, from received through retry-scheduled.