Instant set offload
Local staging onto an integrated NVMe cache (2 or 4 TB protected, by tier), at whatever rate the card will read. Two drives, every file written twice. The card is clear before the next setup is lit.
MVRK Systems presents
DailiesDrop™
CARD IN. CLOUD OUT. AT CARD SPEED.
An automated data wrangler. It takes the card as fast as the card will read, slices encrypted chunks across every route it can reach (a house Ethernet line, two cellular carriers, a satellite dish) and delivers verified footage straight into the editor's timeline. Whatever the location gives it, the data lands. No screen. No menu. No app.
Power
Ingest
Network
Ready
Error
Idle
Card → cache
0 %
Cache
—
ETH
—
LTE A
—
LTE B
—
SAT
—
Standby · Card reader idle · awaiting media
01 · What it does
Three jobs, done without a menu.
Four-route bonded uplink
Slices RAW and proxy files across 2.5 GbE Ethernet, dual cellular and satellite concurrently. All four routes are on every unit. A studio wall port and a mountainside are the same problem to it.
Zero-UI simplicity
Automatic checksum validation and zero set setup, reported entirely through a high-visibility LED status plate.
Studio or backlot
A house Ethernet line exists. The box takes it, pins RAW to the wired route, and spends nothing on cellular.
Location, good coverage
No cable. Two carriers bond into one queue, proxies first, RAW behind them.
Remote, no bars
Cellular is dead. Satellite carries the run alone, slower but uninterrupted.
Moving vehicle
Routes drop and recover constantly. Stalled links re-probe and rejoin; the queue never blocks on one of them.
What makes it zero-UI
The box has no settings because the software has opinions.
MVRK's AI orchestration layer runs on the appliance itself. It models each link continuously, re-decides the transfer mode every five seconds, and re-routes around a failing path without anyone on set noticing; which is the only reason a device this capable can ship with five LEDs and no menu.
>800MB/s
Ingest target, CFexpress
2–4TB
Protected cache, by tier
Up to 4routes
Bonded uplink
16GB
DDR5 memory
02 · Industrial engineering
An industrial x86 platform
An industrial x86 platform
in a sealed aluminium tub.
Eight cores, sixteen threads and 16 GB of DDR5; a full workstation-class x86 machine, not an embedded controller, because checksumming and encrypting terabytes at line rate is real work. Precision-milled aluminium, sealed against weather and set dust. It is capital equipment: it has to look like it will survive the truck, because it has to survive the truck.
Exploded view
Seven layers in a sealed aluminium tub. The MIMO antennas sit directly beneath the composite window (the only RF-transparent part of the shell), which is the reason nothing has to stick out of the box.
- LED status plate
- Composite RF window
- 5G MIMO antennas
- 2× NVMe SSD · PCIe 4.0 ×4
- 8-core x86-64 · 16 GB DDR5
- 2× 5G modems, bonded
- Milled 6061-T6 shell
~30 W under sustained load
The enclosure is being drawn around the x86 board; the published envelope follows once the thermal model is confirmed on hardware. Small enough for a camera cart, a case cut-out, or a shelf tray.
Set by the card, not the appliance
Every offload is limited by the card and the reader in front of it. Most appliances add a second bottleneck behind that one: a thin bus, a shallow cache, a hash pass that waits for the copy to finish. This one does not. Ingest runs over a 40 Gbps host port into NVMe, and hashing runs on the stream, so the only thing setting your offload time is the card you shot on. Bring a faster card and the box keeps up.
Precision-milled 6061-T6 aluminium
The board is thermally bonded to the shell, so the whole chassis works as the heatsink. Airflow is internal and filtered; the case stays sealed against set dust and rain.
8-core / 16-thread x86-64 · 16 GB DDR5
A full industrial x86 platform, not an embedded controller. The board is thermal-coupled to the aluminium walls, so the whole chassis is the heatsink.
Internal omnidirectional 5G MIMO
Antennas are embedded beneath a top composite window; no external whips to snap off in transit.
1/4"–20 · 3/8"–16 · 9–36 V DC
Threaded mounting points on two faces take a standard cine accessory. Power is a recessed locking connector that cannot be kicked out.
DailiesDrop™ · Technical specifications
- Ingest
- At card speed. The card is the ceiling, not the appliance.
- Ingest path
- USB4 host, 40 Gbps · cache writes at PCIe 4.0 ×4
- Sustained, CFexpress Type B
- >800 MB/s · design target, pending measurement
- Sustained, SD UHS-II
- 312 MB/s · standard ceiling
- Compute
- 8-core / 16-thread x86-64, thermal-coupled
- Memory
- 16 GB DDR5
- Cache
- 2 or 4 TB protected · 2× TLC NVMe, PCIe 4.0 ×4
- Cache redundancy
- Every file written twice, always; no single-copy state
- Cache eviction
- Only once a copy is verified off the box; never to make room
- Cache headroom
- GB free, in the web interface; the chassis signals with the error LED
- External mirror
- Optional, background, append-only; the appliance never deletes or formats it
- Wired
- 2.5 GbE, RJ45
- Cellular
- 2× 5G modems, bonded
- Satellite
- Standard on every unit · bring your own dish
- Bonded routes
- Up to 4, concurrent
- Antennas
- Internal omnidirectional 5G MIMO
- Chunk size
- 64 MB, encrypted, per-chunk SHA-256
- Power input
- 9–36 V DC, recessed locking
- Mounting
- 1/4"–20 and 3/8"–16 threaded
- Verification
- SHA-256 against source manifest
- Interface
- 5 LEDs. No screen. No app.
- Housing
- Milled 6061-T6 aluminium
- Cooling
- Chassis-coupled heatsink, ~30 W sustained
- Delivery targets
- S3-compatible and NLE webhook targets
MVRK SYSTEMS · MVRK.SYSTEMS · DOC MVRK-DD-SPEC-01
03 · The run
Four steps, none of them yours.
The operator does one thing: plug in the card reader. Everything after that is the box's problem.
Card in
Card reader connected to the reinforced USB-C port. Ingest begins on detect; there is nothing to confirm.
Sliced across routes
The edge-slicing engine distributes encrypted 64 MB chunks over dual 5G networks and the satellite path, weighted by which link the scheduler predicts will run dry soonest.
Stitched and checked
The MVRK Cloud Node receives, stitches, and verifies SHA-256 against the source manifest before anything is released downstream.
Straight to post
Automated webhooks push proxy and RAW assets directly into Frame.io and Air.ink targets.
Two hashes, two jobs
Every chunk carries a SHA-256, and the reassembled file is checked against the source manifest before the webhook fires. SHA-256 rather than MD5 because a checksum that can be forged proves the file arrived intact, not that it is the file that was shot; and because the x86 platform hashes it in hardware, so it runs on the stream and costs the offload nothing.
An xxHash64 sidecar rides along
Post houses already run ShotPut Pro, Hedge and Silverstack, and those speak xxHash64 through ASC MHL. So the delivery carries one too. The receiving end verifies with the tool already on the cart; nobody has to install anything to trust what landed.
The second copy can move. It cannot go away.
Every file is written twice and stays written twice; what changes is where the second copy lives. Once a file is verified at the destination it already has a copy off the box, so the internal mirror is released and that space comes back on its own. With a drive attached, the second copy can live there instead, which roughly doubles what the cache holds before the queue has drained.
Nothing clears the cache until it has landed somewhere else, over the network or onto a drive. No connection for a week, with no drive attached, means a week of footage still on the box, untouched and still mirrored. Space is only ever freed after the surviving copy is hashed and verified, never before. There is no mode in which the box keeps one copy of your footage, and none in which it makes room by dropping something you have not delivered. The status plate says which you have: pulsing green for one verified copy, safe to eject; solid green for two independent copies, safe to format.
The box writes to it. It never deletes from it.
The mirror is written in the background and never inline, so a slow shuttle disk cannot hold up a card release. Only the internal cache evicts. The external drive is append-only: nothing on it is removed, aged out or formatted by the appliance, on a project release or ever. Because it is usually the larger of the two it carries the whole shoot rather than the overflow, so the drive that leaves set is complete and verified rather than a partial spill. Unplug it and the box goes back to writing both copies internally, which costs headroom and never costs a copy.
04 · Tiers
One chassis. Two tiers,
One chassis. Two tiers,
by how much you shoot in a day.
The only difference between tiers is cache depth. Every unit puts up all four routes, runs the same scheduler, carries ShuttleCheck™ Pro and coordinates with every other unit on the production. There is no crippled entry model.
Pro
Most productions
Single-unit days, features, commercials.
€3,900 €229 / mo per active device 2 TB protected/4 TB raw- 2× NVMe, every file written twice
- Cache zoned by the box: reserve, in-flight, retention
- All four routes: 2.5 GbE, 2× 5G, satellite
- SHA-256 verification on arrival
- Webhook delivery to post
- ShuttleCheck™ Pro included
- Multi-unit coordination, at any unit count
Fleet
High-volume days, multi-camera, long-form.
€4,700 €229 / mo per active device 4 TB protected/8 TB raw- 2× NVMe, every file written twice
- Cache zoned by the box: reserve, in-flight, retention
- All four routes: 2.5 GbE, 2× 5G, satellite
- SHA-256 verification on arrival
- Webhook delivery to post
- ShuttleCheck™ Pro included
- Multi-unit coordination, at any unit count
| Specification | Pro | Fleet |
|---|---|---|
| Unit price | €3,900 | €4,700 |
| Orchestration | €229 / mo | €229 / mo |
| Protected cache | 2 TB | 4 TB |
| Raw capacity | 4 TB | 8 TB |
| Cache redundancy | 2× NVMe, every file twice | 2× NVMe, every file twice |
| Wired | 2.5 GbE | 2.5 GbE |
| Cellular routes | 2× 5G | 2× 5G |
| Satellite | Standard | Standard |
| Max bonded routes | 4 | 4 |
| Multi-unit coordination | Included, any unit count | Included, any unit count |
| ShuttleCheck™ Pro | Included | Included |
Bring your own carrier
MVRK does not resell cellular data. The unit takes your SIMs and your dish, and bonds whatever the production already has. Broadcasters with existing carrier agreements keep them; on a house Ethernet line the data cost is zero regardless. No reseller margin, no territory restrictions, no packs to run down mid-shoot.
One flat monthly, per active device
€229 a month on both tiers, billed per device-month while the unit is live on a project, and charged to that project rather than against the hardware. An idle unit between shoots bills nothing. One price covers the scheduler, the verification relay, region-pinned reassembly, ShuttleCheck™ Pro, convention distribution, ASC MHL sealing, enrolment and release, and coordination across every unit on the job. There is no second fee at any unit count: twelve units cost twelve device-months, and nothing changes about what they do.
Two roles, often the same company.
Owning a unit and running a project are separate roles, not necessarily separate businesses. A rental house buys units and puts them out on other people's shoots. An owner-operator buys one and runs it on their own work. Both behave identically: units belong to whoever bought them, the project belongs to whoever is shooting, and device-months are billed to the project. When those are the same company it is simply the same invoice, and nothing about the setup changes. Return is an explicit release that clears the internal cache, the naming convention and the project binding; it never touches an external drive, which is yours and leaves with you.
The card always comes back.
Offload, hashing, verification, card release, the external mirror and conformance against the cached convention never expire, and not one of them needs a connection. Enrolled and offline adds queueing. Online adds upload, the ledger and sealing. What is finite is the cache, not the function: with nothing draining it fills at the rate you shoot. The web interface reports what is left in GB, so it reads as how many more cards will fit; on the chassis it is the error LED that tells you to go and look. When it is full the box stops taking cards. It does not make room by deleting work you have not delivered. A box that refuses a card because it cannot reach the internet is a box nobody trusts twice; a box that quietly deletes to keep going is worse.
An unpaid project is the same promise. It suspends upload on all four routes and nothing else; offload, hashing, verification and card release are never withheld over an invoice. Media already staged stays readable and the card is released on schedule. We will chase a debt through the account, never through your footage.
PRICING INDICATIVE, EUR IS THE LIST CURRENCY · NO UNIT SHIPS WITH A DISH OR A SIM; BRING YOUR OWN CARRIER AND YOUR OWN DESTINATION · CACHE FIGURES LEAD WITH PROTECTED CAPACITY, EVERY FILE WRITTEN TWICE · THE MONTHLY IS BILLED TO THE PROJECT PER ACTIVE DEVICE-MONTH, WHOEVER OWNS THE UNIT · DEALER, RENTAL-HOUSE AND VOLUME TERMS ON APPLICATION
Pilot programme
Put one on a truck.
Tell us the shoot, the territory, and the delivery target. We will tell you whether the box is the right tool for it.