The single pane of glass

GATEWAY

Find anything. See the waste. Fix without fear.

Gateway puts your entire media estate behind one search bar: cloud, on-prem, even tape. It shows you where storage money leaks, and it fixes stuck pipelines with a preview first and an undo after.

What changes
01

Find anything, anywhere

One search covers everything you store: cloud, on-prem shares, even LTO tape. Every result comes back with checksums and metadata, so you know it is the real file before you touch it.

02

See where the money leaks

Duplicates, cold files, dead weight: Gateway prices them on your own storage rates and shows the savings in dollars. You decide what to reclaim before the next invoice.

03

Ask the catalog a question

Type a question the way you would ask an archivist. Answers stream back from the catalog, limited to what you are cleared to see, with every question logged.

04

Fix pipelines without fear

A stalled ingest is not an emergency. Gateway shows you exactly what a fix will touch, runs it on your confirm, and the biggest operations come with one-click undo.

How it does it

Search built for a studio estate

One surface spans your storage catalogs, tape included, plus enriched companion metadata. Fuzzy matching handles messy names, power users get safe regex, and a duplicates-only filter isolates copies. If the primary index goes down, search degrades gracefully to a secondary index instead of going dark.

Five reports, your cost model

Duplicate-savings grouped by extension, volume or production. Cold-files and dead-weight. Archive ROI. Storage overview with volume breakdown. Extension analytics. All priced on an admin-editable cost model preloaded with 8 storage tiers, from cloud object storage classes to on-prem SAN and LTO tape.

Ask the catalog

Production-scoped chat over the catalog with streamed answers and persistent history. Permissions resolve per question, and every question writes an audit row. Read-only by design: chat can never change your data.

Automations that wait for a human

Auto-ingest rules match on volume, path, pattern, type, size and date, evaluated on schedule. Matches queue as pending decisions for your approval, idempotently, so a rule never lands the same file twice. WRAP archive templates keep folder structure consistent, globally and per production.

Recovery ops with a safety net

Retry, retry-all-failed, DAM re-ingest, hard reset, soft retry, stage refresh and bulk approve, all from the live queue. Hard reset and soft retry default to a dry-run preview with exact counts and are one-click undoable. The rest execute only on operator confirm.

For your engineers

The technical depths.

Counts and limits below are verified against shipping code. The full capability datasheet is available on request.

Gateway specifications
Search surface
One surface across storage catalogs (tape included, via the StorageDNA catalog index) and enriched companion metadata · fuzzy matching · deep result-set pagination · safe power-user regex · duplicates-only filter that fails closed · graceful degrade to the secondary index if the primary is unavailable
Checksums
Surfaced at file and folder level · kept current by continuous folder-checksum maintenance with scheduled reconciliation
Reports
Five report types: duplicate-savings (group by extension, volume or production), cold-files/dead-weight, archive ROI, storage overview with volume breakdown, extension analytics · admin-editable cost model preloaded with 8 storage tiers, cloud object storage classes to on-prem SAN and LTO tape
Ask the catalog
Production-scoped Q&A chat with streamed answers · persistent history · permissions resolved per question · per-question audit row · read-only by design
Automations
Auto-ingest rules (volume, path, pattern, type, size, date) evaluated on schedule; matches queue as pending decisions for human approval, idempotently · WRAP archive templates with structured folder definitions, global and per-production · guided storage-volume onboarding with dry-run-by-default indexer setup and discovery of existing tape-catalog volumes
Batch & metadata ops
CSV/spreadsheet metadata import with column mapping and an approve/publish lifecycle, uploads to 100 MB · ShotGrid version ingest · metadata key/value browser with alias governance and controlled vocabularies · DAM taxonomy-migration toolkit with dry-run and execute · machine stage-update API at 500 events per call with 8-way resolution
Recovery operations
Retry · retry-all-failed · DAM re-ingest · hard reset · soft retry · stage refresh · bulk approve · per-job retry, cancel and log retrieval in the live queue · hard reset and soft retry default to a dry-run preview with exact counts, one-click undoable; the rest execute on operator confirm
Live monitoring
Real-time queue view (processing / completed / failed) · 5-stage per-file tracking with folder rollups · signature-verified inbound job webhooks with replay protection · authenticated, permission-scoped live browser updates
Governance & identity
Roles: admin / coordinator / viewer · per-production access guards · scoped SSO permissions per functional area (OIDC, SAML 2.0) · TOTP MFA · full audit trail with severity mapping and batch export · SOC 2 Type II aligned posture, designed for MPA content-security best practices
Questions
Can Gateway search content stored on LTO tape?

Yes. Gateway presents one search surface across storage catalogs, and that includes StorageDNA-managed LTO tape through its catalog index, alongside S3, Box, NFS and SMB storage. Tape results are as current as the most recent catalog scan, and every result carries checksums and metadata.

How does Gateway show where storage budget is being wasted?

Gateway runs five report types: duplicate-savings, cold-files, archive ROI, storage overview and extension analytics. Each is priced on an admin-editable cost model preloaded with 8 storage tiers, from cloud object storage classes to on-prem SAN and LTO tape, so the savings are stated in your rates, not industry averages.

Is it safe to run Gateway recovery operations on a live pipeline?

Gateway's recovery operations are built for live pipelines. Hard reset and soft retry default to a dry-run preview with exact counts of what would change, and both are one-click undoable. Everything else executes only on operator confirm, and every action is captured in the audit trail.