One policy. Every site.

Built for the way a portfolio actually runs.

• Logistics & 3PL networks, standardize gate access across every DC, yard, and cross-dock.
• Industrial & commercial real-estate portfolios, one way to manage entry across every property, with control at each one.
• National retail, manufacturing & energy, a consistent entry policy across sites, shifts, and contractors.
• Corporate & campus security, central oversight, with per-person permissions for local teams.

Enterprise-grade where it counts.

The comparison isn’t us against another vendor. It’s one standard against however each site does it today.

That’s the portfolio today. The rest of this page is the standard that replaces it — site by site.

Run a portfolio of gates like one system.

The actual product, on a fifty-site demo company, centralized where it should be, per-site where it matters.

Onboard a whole fleet in one paste.

Drop a CSV or paste a plate column from your spreadsheet and every vehicle is authorized in a single step.

Onboard your whole team in one paste.

Drop a CSV or paste an email column from your spreadsheet and everyone gets access in a single step. Pick their group, and they’re in.

Push one list to every site.

Build a list once (its own days, hours, and gates) then roll it out across the sites that need it in a single step.

Does it support single sign-on and per-person permissions?

Per-person permissions are built in: admin and user roles scoped per company and site, with a full audit trail on every action. Company-wide single sign-on (SSO) is on the enterprise roadmap; today, enterprise deployments use per-person logins with role-based permissions. Tell us your login system and we'll plan SSO with you.

How do we roll it out across dozens of sites?

Site by site, on the gates you already have, about half a day per gate, no rebuilds. Most portfolios pilot a few sites, lock a standard policy, then roll the rest out on that template, with remote support at every commissioning.

Will it pass our security review?

It's built for it: AES-256 at rest and TLS 1.2+ in transit, an NDAA-compliant camera, per-person logins with role-based permissions, and plate-reading that runs at the gate, so recognition and gate decisions never depend on the cloud. Access events sync to your dashboard over TLS 1.2+. We support your vendor security and compliance review with documentation and audit-ready exports.

What happens at a site that loses internet?

Gates keep opening on the cached local access list — a site can run fully disconnected for up to 30 days — and every event syncs automatically when the connection returns. Recognition and gate control run on-site, not in the cloud — a network blip never strands a gate.

How does it fit the systems we already run?

It connects to your other software two ways: a full developer interface (API) for custom links, and a ready-made Shiptify connector and spreadsheet imports (more connectors in progress), so access stays in step with operations, with nothing entered twice. We share the full API reference during evaluation.

Who manages it, and how is access governed?

Your operations or security team, from one dashboard, central policy with per-site overrides, every change attributed and logged. No technical expertise required, and nothing happens at a gate that your rules didn't allow.

From your site list to a standardized fleet.

1. 01
   Send your site list

   Locations, gate types, and how access works today. We scope the portfolio and come back with a plan, usually within 48 hours.

2. 02
   Pilot a few sites

   Commission a handful of gates on the barriers you already have, prove the policy and the integrations, and set your standard.

3. 03
   Standardize the policy

   Lock one access template (lists, schedules, roles, overrides) that every new site inherits on day one.

4. 04
   Roll out the fleet

   Bring the rest of the portfolio online on that template, with remote support per site and one dashboard over all of it.