Do we need to expose new endpoints?

Typically no — our SIS integrations consume your existing Ethos, IB, or CWS endpoints via least-privilege service accounts.

Is there a SOC 2 report available?

Yes — we can share our SOC 2 documentation and security posture under NDA during procurement.

Built for · IT Directors

Parcel lockers for university IT directors and CIOs

Your job is to say 'yes' to operations without taking on identity sprawl or risk. Our integration footprint is small, our identity story is standard, and our data posture is documented.

Get benchmark report See case studies →

What hurts today

×Operational vendors with one-off identity stacks add risk
×SIS integrations done badly become a multi-year support burden
×FERPA exposure from poorly governed vendor data
×Yet-another-vendor for InfoSec to review

What changes with lockers

→Standard SAML/OIDC/CAS — no parallel identity system
→SIS integration via Ethos, RaaS, IB, or CWS — your team's existing patterns
→FERPA-aligned data handling with auditable logs
→SOC 2-aligned hosting documentation available during procurement

Your KPIs

What we move on your scoreboard

Standard

Identity model

Yours

SIS patterns

Documented

FERPA posture

Pre-built

InfoSec review

Frequently asked questions

The benchmark report

University Mailroom Benchmarks 2026 — package volume, staffing, cost per package, and adoption data across enrollment tiers.

Get the report →

Campus case studies

Filterable case studies by enrollment size and deployment type.

Browse case studies →