Backed by mandō
Canopy gives engineering teams deep, human-readable insight into storage consumption — from a single file to an entire fleet of directories. See what's taking up space, set depth limits, exclude noise, and ship leaner infrastructure.
Features
Powered by -h. Translates raw byte counts into human-readable units — K, M, G — so
your team can reason about storage at a glance instead of counting zeroes.
Powered by -s. Distill an entire directory tree into a single number. No noise, no
sub-paths — just the total you need to make decisions fast.
Powered by -c. Scan multiple paths and get a unified grand total across all of them.
Full audit trail, one command.
Powered by -a. Surface every single file — not just directories. See exactly where
your bytes are hiding across the entire hierarchy.
Powered by --max-depth. Set a precision radius. Go two levels deep, three, or zero.
You decide how granular the report gets.
Powered by --exclude. Pattern-matched exclusion at scale. Skip build artifacts,
vendor folders, or anything matching your custom pattern.
Powered by --apparent-size. See what your files actually consume — accounting for
sparse files, internal fragmentation, and indirect blocks.
Powered by --time. Attach modification timestamps to every directory in your report.
Know not just how big, but how recent.
How It Works
Specify any file, directory, or set of paths. Canopy recursively traverses every level, aggregating device usage as it goes.
Set depth limits, apply exclusion patterns, toggle between apparent size and device usage, choose your block size — make the report yours.
Get a clean, human-readable breakdown or a machine-parseable NUL-terminated stream. Pipe into your CI, dashboards, or alerting stack.
Interactive Demo
Case Study
NovaBuild, a 200-person infrastructure company, was haemorrhaging cloud spend on bloated container images and orphaned build artifacts. Their ops team spent hours each week manually auditing storage across dozens of microservices — with no unified view of what was actually consuming space.
"We were flying blind. Every sprint review, someone would ask 'why is our storage bill up 15%?' and nobody could answer in under an hour."
— Priya Mehta, VP of Platform Engineering, NovaBuild
After deploying Canopy's --max-depth and --exclude features across
their CI pipelines, NovaBuild surfaced 120GB of redundant vendor directories and stale cache
layers. The Deep Scan (-a) mode identified thousands of orphaned test fixtures that
had accumulated over multiple release cycles.
Within one quarter, NovaBuild reduced their aggregate storage footprint by 40%. The Grand Ledger
(-c) feature now runs nightly across all production paths, piping totals into their
cost-monitoring dashboard. Storage surprises are a thing of the past.
Integrations
What People Are Saying
"Canopy's HumanScale mode is a game-changer. We went from parsing raw byte counts in spreadsheets to shipping storage reports our CFO actually reads. This is a 10x unlock for infra visibility."
"We pipe Canopy into every CI run with --exclude and --max-depth. It catches bloat before it ships. Best-in-class storage hygiene with zero overhead."
"I'm a solo dev shipping three products. Canopy's summary mode gives me the one number I need in under a second. Iterate fast, ship lean. That's the Canopy way."
"The Grand Ledger feature replaced a 400-line bash script we'd been maintaining for three years. Canopy scans 50 paths, sums the total, and gives me one number. Mission-critical simplicity."
What's New
Track inode usage instead of block usage with the new --inodes flag. Ideal for
filesystems with millions of small files where inode exhaustion is the real bottleneck.
-B now supports binary prefixes (KiB, MiB, GiB) alongside SI units. Scale your
reports in whatever denomination your team standardises on.
Feed Canopy a NUL-terminated list of paths and scan them all in one pass. Pairs perfectly with your existing pipeline tooling for zero-friction batch analysis.
Pricing
Start free. Scale when you're ready.
-s)-h)-a, -s, -c)--exclude)--apparent-size)--time)-x)-L)--inodes)--files0-from)-0)-S)-B)FAQ
Device usage reflects the actual disk blocks allocated, including overhead from the
filesystem. Apparent size is the logical byte count of the file contents. Sparse files,
fragmentation, and indirect blocks can cause these to diverge. Canopy's TrueSize™ mode
(--apparent-size) lets you see both perspectives.
Absolutely. Canopy recursively traverses any hierarchy, no matter the scale. For extremely
large trees, use --max-depth to limit report granularity, or
--exclude to skip known-noisy directories. The NUL-terminated output
(-0) mode is optimised for pipeline consumption at any volume.
Canopy operates entirely within your local filesystem. No data leaves your machine. We never phone home, store telemetry, or exfiltrate path information. Enterprise customers get SOC 2 Type II documentation and on-prem deployment options.
Yes. Canopy runs entirely on your local machine with no network dependency. An active licence is validated once per billing cycle, after which the tool operates fully offline.
By default, Canopy reports in 1024-byte blocks. Use -h for human-readable units
(K, M, G), -B to set a custom block size (e.g., -BM for
mebibytes), or --si for powers of 1000.
Join 14,000+ teams who've made storage visibility their competitive advantage.
Get Started Free