From the field to the cluster — petabytes, on time.
Across oil & gas, utilities, and renewables, seismic surveys, sensor arrays, and reservoir and grid models generate petabytes that have to move from remote fields and vessels to processing centers and HPC — often over constrained, shared links. Zettar fills whatever bandwidth is available, from a compact field appliance to the datacenter core, so data arrives in time to act on it.
Petabytes pile up faster than you can move them.
- Seismic and sensor data is petascale and grows every survey.
- Remote fields and vessels have limited, shared links — and ordinary tools waste most of them.
- Data crawls from field → processing center → HPC.
- Reservoir simulation and grid analytics stall waiting on data.
Fill the link you have — edge to core.
Fills the link you have
Zettar runs at line rate, realizing ~90%+ of whatever bandwidth is available, even on a shared or constrained link. On a 100 Gbps link, that’s about a petabyte a day.
Edge to core
The same co-designed mover from a compact field/edge appliance to the datacenter. Linear scale-out, no software ceiling.
Distance-insensitive
Remote field to processing center at line rate, validated over real 5,000- and 12,375-mile transfers.
Feeds HPC, secured
Scale-out file and object movement with no software ceiling, encrypted with TLS and unconditional end-to-end checksums. Turnkey and pretuned.
In one deployment, transparent file-to-object tiering — with no performance penalty — came in at 70% lower upfront cost than the alternatives evaluated.
Backed by the record: 1 PB in 29 hours at 96% link utilization with SLAC & ESnet (U.S. DOE). Read the record →
Put a number on it — and make your case.
Field and seismic data loses value the longer it sits at the edge. Late data means late interpretation — and decisions made on yesterday’s picture.
Common questions
How fast can Zettar move seismic data?
At line rate — it realizes ~90%+ of whatever bandwidth the path can sustain, even on a shared or constrained field link, and scales out with no software ceiling.
Does it work over the limited links at remote field sites?
Yes — that is the point. zx fills nearly all of whatever bandwidth is available, even a shared link, so constrained sites stop wasting the capacity they have.
Can it move data from a vessel or field site to the datacenter?
Yes — the same co-designed mover spans a compact edge appliance to the datacenter core, and is distance-insensitive over real 5,000- and 12,375-mile transfers.
Does it feed HPC processing?
Yes — scale-out file and object movement keeps reservoir simulation and processing clusters fed, encrypted and checksummed end to end.
Is the data secure and verified?
Every transfer is encrypted with TLS and protected by unconditional end-to-end checksums.
Get field data where it belongs — on time.
See the zx Appliance move seismic, sensor, and reservoir data at line rate — about 10× typical movers.
