Pillar gives post facilities early warning of storage latency, scrub conflicts, and capacity risk across Linux, TrueNAS, and Unraid.
Native Support for Creative Storage Arrays & White-Box Hardware
In this example, Pillar identifies a 148ms disk outlier while showing pool capacity normal and no host-side interface saturation or packet loss observed.
Isolates single 148ms mean read await outlier during 24fps/60fps playback
While total pool throughput remains normal at 840 MB/s, Drive 6 in VDEV 2 is pinned in an internal ECC sector retry loop. Host NIC drops normal; no host-side interface saturation or packet loss observed—isolated in 15 seconds.
Standard alerts often arrive after a failure. Pillar is built to surface the early signals that matter during active work.
Enterprise drives accumulate uncorrectable read errors (UREs) and bad sectors over weeks. Too often, the first time a controller flags them is during a grueling rebuild—when a secondary drive drops offline and corrupts the entire pool.
Server rack ambient temperatures surge when finishing suites kick off overnight render queues. Generic monitoring tools either wake sleeping platters 50+ times a day or miss nocturnal 50°C+ heat spikes completely—accelerating drive degradation.
I/O stalls close to master delivery can be costly. An uncoordinated ZFS scrub or drive resilver may compete for pool resources during a live review; Pillar helps teams spot and coordinate those maintenance conditions.
Pinpoint the cause, protect maintenance windows, plan capacity, and account for storage without adding another dashboard of noise.
See whether a playback stall is caused by a single disk, the storage pool, or something outside the array—before teams lose time chasing the wrong layer.
Compare scrub progress with scheduled edit hours so your team can adjust maintenance before it overlaps a client session.
Track recent ingest velocity and capacity runway so teams can make room before an incoming project creates performance risk.
Attribute storage to client projects while polling drive health in a way that preserves standby disks.
The difference is context: Pillar relates storage health to active edit sessions, maintenance windows, and capacity plans.
-n standby to preserve sleeping disks without waking platters.Tell a single-drive outlier apart from pool-wide or host-NIC problems.
Spot scrub conflicts before they overlap a scheduled session.
Use recent ingest velocity to see when a pool needs attention.
Built with read-only, outbound-only telemetry controls to support facility security reviews. Validate the deployment against your organization's specific TPN and MPA requirements.
docker run -d --name pillar-agent \ --restart unless-stopped \ --read-only \ --cap-drop=ALL \ --cap-add=SYS_RAWIO \ --tmpfs /tmp:rw,noexec,nosuid,nodev,size=64m \ -v /dev:/dev:ro \ -v /proc/diskstats:/proc/diskstats:ro \ -v /sys/block:/sys/block:ro \ -v /sys/class/block:/sys/class/block:ro \ -v /sys/class/enclosure:/sys/class/enclosure:ro \ -v pillar-agent-data:/etc/pillar \ -e PILLAR_API_KEY=<YOUR_STUDIO_API_KEY> \ ghcr.io/pillarinteractive/pillar-agent@sha256:<verified-release-digest>
In post-production, capacity can grow quickly with 6K/8K RAW ingest. The plans shown do not meter usage by terabyte. Plan limits, availability, and the applicable Order Form apply.
Evaluation eligibility, pricing, and included services are confirmed at signup. The founding plan includes the features and onboarding scope described in the applicable Order Form.
For multi-suite post houses & boutique finishing facilities
Billed monthly • Up to 3 storage heads included
For high-throughput facilities, broadcast groups & studio campuses
Billed monthly • Up to 10 storage heads included
Additional monitored storage heads may be available at +$99/month per host, subject to the selected plan and Order Form. Capacity usage is not separately metered by terabyte on the plans shown.
Prices, plan availability, included services, and renewal terms are subject to the applicable Order Form and Terms of Service.
Need SSO (SAML/OIDC)? Available on custom plans — contact us.
/dev/sd*, /dev/nvme*n*)./proc/diskstats and /sys/block. On Unraid, paste the 1-line Docker command into the web terminal or use the Unraid Community Apps container template. For step-by-step guides, systemd unit files, and persistent init scripts, see our Platform Deployment Guides.docker stop pillar-agent && docker rm pillar-agent. A complete removal may also require removing the signed updater, its systemd timer, configuration, and named volumes. See Troubleshooting & Lifecycle for de-provisioning details.Start on a secondary or ingest array, validate the signals with your team, then decide whether to expand. Evaluation eligibility and checkout requirements are shown at signup.