BUILT FOR COMMERCIAL POST-PRODUCTION

Catch storage problems before they interrupt a client review.

Early warning of slow disks, maintenance conflicts, and capacity risk for post-production teams using Linux, TrueNAS, or Unraid.

Free for 14 days. Eligibility and checkout requirements are shown at signup.

Read-only filesystem · Outbound telemetryNo production dataset mounts in the documented configuration.

Built for your storage stack

45Drives Houston / StorinatorTrueNAS SCALE & COREOpenZFS & Linux MDRAIDUnraid & Debian Server
ONE INCIDENT, ONE CLEAR ANSWER

Find the source of a playback stall

In this example, one disk takes 148ms to respond. Pool capacity is normal, with no host network saturation or packet loss observed.

Pillar
3 Nodes Online
CRITICAL ALERT

Drop-Frame Latency Monitor

One disk shows 148ms mean read await during playback

Suite A Stutter DetectedTarget Budget: 41.7ms (24fps)
Drive 6 (/dev/sde): 148.2ms Mean Read Await Outlier

In this example, pool throughput is 840 MB/s, but Drive 6 in VDEV 2 shows elevated read latency. No host-side interface saturation or packet loss is observed, helping narrow the investigation to the disk.

Drive Queue Await Comparison (41.7ms 24fps Deadline)
/dev/sdc (Edit Pool VDEV 1)3.8ms await (Nominal)
/dev/sdd (Edit Pool VDEV 1)4.1ms await (Nominal)
/dev/sde (Edit Pool VDEV 2)OUTLIER148.2ms await (3.5x over frame budget)
↳ Safe Zone: < 25ms24fps Budget: 41.7msCritical Stall: > 100ms
Try sample incidents, maintenance forecasts, and billing exports:
Explore Live Sandbox
WHAT TO WATCH

Spot risks before the next session

Watch drive health, temperature trends, and maintenance activity together so your team can decide when to act.

Drive errors that go unnoticed

Rising read errors and bad sectors can put a rebuild at risk. Track drive health over time so your team can investigate before another disk fails.

Overnight temperature spikes

Overnight workloads can coincide with rising drive temperatures. Review temperature trends while standby-aware health checks preserve sleeping archive disks.

Maintenance during a review

A scrub or resilver can compete with playback for storage resources. See when maintenance may overlap scheduled edit hours and coordinate it with your team.

BUILT AROUND YOUR SESSIONS

Know what needs attention

Pinpoint the cause, protect maintenance windows, plan capacity, and account for storage without adding another dashboard of noise.

24fps Budget: 41.7ms

Find the disk behind the slowdown

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.

Telemetry: /proc/diskstatsNon-root sampling
Maintenance alerts

Keep maintenance outside edit hours

Compare scrub progress with scheduled edit hours so your team can adjust maintenance before it overlaps a client session.

Schedule: Active Edit HoursConflict warnings
Capacity forecasts

Know when storage needs more room

Track recent ingest velocity and capacity runway so teams can make room before an incoming project creates performance risk.

Runway: Multi-Window (24h/7d/30d)By storage tier
Project chargeback

Track storage by client

Attribute storage usage to client projects and export chargeback data for invoicing.

Billing: CSV / Accounting SyncClient allocation

WHY PILLAR

Storage signals with session context

Your existing tools may collect the metrics. Pillar connects them to edit hours, incoming projects, and the decisions your team needs to make.

Which disk is slowing playback?

Drive health and I/O latency

Compare mean read await across disks; measure p99 latency with Pillar Observer.

Will maintenance overlap a session?

Scrub progress and edit schedules

Estimate remaining scrub time and flag conflicts with scheduled edit hours.

When will a pool need more room?

Capacity and recent ingest rates

Forecast runway against configurable capacity thresholds.

Can archive disks stay asleep?

Drive power state and health checks

Use standby-aware SMART collection to preserve sleeping disks.

SECURITY & ACCESS

Understand exactly what Pillar can access

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.

Data Flow & Isolation Architecture
01. Studio Storage Host
TrueNAS / ZFS / Linux
/proc/diskstats :ro
/sys/block :ro
/mnt/tank (ZERO ACCESS)
Outbound Only (Port 443)
Encrypted Telemetry Push
No TCP/UDP listeners by design
No inbound port-forward configuration required
HTTPS Metric Heartbeat
02. Pillar Cloud
Real-Time Fleet Dashboard
Tail Frame Spikes (p99 w/ Observer)
Scrub Window Alerts
80% Ingest Forecasts
Inspect deployment settings and sample telemetry
🛡️ZERO FOOTAGE ACCESS

Security & Telemetry Inspector

Target Platform:
# Non-root, capability-stripped container command. Zero media dataset paths mounted.
docker run -d \
  --name pillar-agent \
  --restart unless-stopped \
  --read-only \
  --cap-drop=ALL \
  --cap-add=SYS_RAWIO \
  --security-opt no-new-privileges:true \
  --pids-limit 128 \
  --memory 256m \
  --device-cgroup-rule 'b *:* r' \
  --log-driver json-file \
  --log-opt max-size=10m \
  --log-opt max-file=3 \
  --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 \
  -v pillar-run:/run/pillar \
  -e PILLAR_API_KEY=<YOUR_STUDIO_API_KEY> \
  ghcr.io/pillarinteractive/pillar-agent@sha256:<verified-release-digest>
✓ Read-Only RootSub-35MB RAMNo TCP/UDP listeners by designNo production dataset mounts in documented configuration
PRICING

Pay by appliance, not by terabyte

Choose a plan for the number of storage appliances you monitor. No per-terabyte metering on the plans shown.

MonthlyAnnualSave ~17%
Limited founding offer

Founding plan: $299/month

For qualifying facilities: up to 3 appliances, 10 team members, and onboarding support. This limited offer is separate from the standard plans below. Availability, pilot eligibility, and plan terms are confirmed at signup and in the Order Form.

Start a 14-Day PilotFounding subscription: $299/month

Standard plans

For commercial facilities

Studio Fleet

For multi-suite post houses & boutique finishing facilities

3 appliances
$349/ mo

Billed monthly • Up to 3 appliances

View Studio Fleet features
  • • Storage-side latency indicators and scrub-window alerts
  • • Capacity runway, chargeback, and cold-disk-safe monitoring
  • • 90-day telemetry retention and up to 10 team seats

Facility Enterprise

For high-throughput facilities, broadcast groups & studio campuses

10 appliances
$799/ mo

Billed monthly • Up to 10 appliances

View Facility Enterprise features
  • • Security brief and architecture review to support facility assessments
  • • Dedicated integration support and plan-specified team seats
  • • Custom multi-pool and cross-chassis alert routing
GROW WITH YOUR FACILITY

Add more storage appliances

Additional appliances 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.

+$99/ host / month

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.

FREQUENTLY ASKED QUESTIONS

Before you get started

Does Pillar support SAS controllers and JBOD expansion chassis?

Yes. Pillar natively supports direct SATA, SAS, and NVMe block devices across LSI, Broadcom, and Microsemi Host Bus Adapters (HBAs) flashed to IT mode (Initiator Target). In JBOD topographies, our collector tracks both physical enclosure slots and OS device identifiers (/dev/sd*, /dev/nvme*n*).

How do I deploy Pillar on TrueNAS SCALE or Unraid?

Pillar is packaged as a standard, multi-architecture OCI Docker container image. On TrueNAS SCALE, deploy it via the “Custom App” interface with read-only host path volume mounts for /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.

How do I cleanly uninstall the agent if we decide not to proceed?

Stopping and removing the agent container ends monitoring: 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.

How is storage usage billed?

Pillar pricing is based on the selected plan and monitored storage appliances rather than measured terabyte consumption. Capacity usage is not separately metered on the plans shown here; plan limits and the applicable Order Form still apply.

Can Pillar execute commands or modify my active storage pools?

Pillar can perform only explicitly authorized, allowlisted actions, such as pausing or resuming an active scrub and controlling a verified enclosure LED. It does not autonomously change pool configuration, kill processes, or issue arbitrary commands. The deployment uses a read-only filesystem and dropped capabilities; administrators should review the documented deployment controls for their environment. Read our Security & Network Whitepaper for details.

Start with one array

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.