Outlet-level
Attribution
Per-outlet metering rolled up through site, room, row, rack, and PDU. Post-order tree attribution means utilisation aggregates automatically at every level — the basis for tenant chargeback, not just a site total.
PowerLens
PowerLens meters to the outlet and rolls it up through your whole site hierarchy — so you can attribute draw to a rack, a tenant, or an experiment, not just a building.
PowerLens
Outlet-level
Per-outlet metering rolled up through site, room, row, rack, and PDU. Post-order tree attribution means utilisation aggregates automatically at every level — the basis for tenant chargeback, not just a site total.
Planning
Power and cooling budgets modelled across N, N+1, 2N, or custom redundancy at all five hierarchy levels. Runway forecasting uses OLS regression with confidence bands, so you see when capacity runs out and how certain that estimate is.
Day to day
Live alerts without page refresh. Time-of-use reporting across day, night, and weekend bands. Comparison-to-previous-period, timezone-aware ranges, CSV export, saved report templates. Offline-gap handling keeps charts intact when a PDU drops.
How it works
Every level of the hierarchy gets its own number, derived from the same readings — not estimated from a building meter.
Five hierarchy levels. The outlet is where the reading is taken; every level above it is a rollup of the levels below.
01
SNMP polling reads each outlet on the PDU directly, so a reading exists for the smallest unit you might want to bill or investigate.
02
Readings land in PostgreSQL on TimescaleDB hypertables. Offline-gap handling keeps series intact when a PDU stops answering.
03
Post-order tree attribution aggregates each node from its children, so site, room, row, rack, and PDU totals stay consistent with the outlets underneath them.
Stack
Python / FastAPI · React / TypeScript · PostgreSQL with TimescaleDB hypertables for time-series · SNMP polling
Stage
PowerLens is a working product, not a concept. Reports, capacity planning, and the operations console are complete and running against internal PDUs.
We’re looking for design partners — R&D labs, datacenters, colocation providers, and MSPs who want outlet-level visibility and are willing to shape the product while it’s still being shaped.
PowerLens has not been deployed to a client. There are no customer logos, no adoption metrics, and no testimonials on this page — because there aren’t any to report yet.
The credibility below is delivered services work. We’d rather you judge us on that than on numbers we don’t have.
Amperique services
Alongside PowerLens, Amperique takes on the compliance and operations work that comes from the same background.
HIPAA and SOC 2 preparation — controls designed, implemented, and evidenced. HIPAA readiness delivered for a healthcare client. SOC 2 Type I and II readiness available. Attestation is issued by a licensed CPA firm; we prepare the environment.
Support and sales operations built to scale — process design first, then automation where it earns its place. Case specialist, sales assist, and support triage agents grounded in your own data, with defined escalation paths.
Engagement / Healthcare / HIPAA
Trinity Medical Coding engaged us to bring their cloud environment and remote workforce in line with the HIPAA Security Rule. The work covered secure infrastructure design, access and identity controls, endpoint hardening, and documented operational procedures — each mapped to the safeguard it satisfies.
About
Amperique was founded on datacenter and lab infrastructure experience — multi-cloud operations across AWS, GCP, and Azure, enterprise support, identity and access engineering, and change control at scale.
PowerLens exists because the attribution problem it solves is one we ran into directly.
Contact
Tell us what you’re running — site size, PDU count, what you’re trying to attribute. Or ask about compliance and operations work.
info@amperique.com