Built around how people actually operate.
People doing operational work are busy and accountable for outcomes. Software should make the situation easier to understand and the next action easier to take.
Company
We build infrastructure for organizations people depend on.
Municipalities, protective service providers, utilities, contractors, and other operational partners increasingly depend on one another to get important work done. Lorica helps them coordinate across organizational boundaries while preserving the authority, systems, and responsibilities of each participant.
Purpose
Coordination has to keep pace with a more demanding operating environment.
Major incidents, infrastructure disruptions, security requirements, and regional emergencies can bring many independent organizations into the same operation. Each may have its own authority, personnel, systems, and responsibilities.
Most of the organizations, expertise, doctrine, and technology needed to respond are already in place. The harder problem is helping them maintain a current understanding of one another and coordinate efficiently when circumstances change.
A need arises
Coordinate
Support committed
Capability exists
Match
Work assigned
Systems disagree
Reconcile
State clarified
Conditions change
Record
History preserved
Principles
A few durable principles guide how we build Lorica.
Keep control where it belongs.
Organizations should be able to work together without giving up authority over their people, information, or internal systems.
Make relationships durable.
Trusted partners, representatives, agreements, capabilities, and prior working history should remain useful after a particular incident or assignment ends.
Preserve the record.
Important coordination should remain traceable. Organizations should be able to understand what was known, what changed, who acted, and where information came from.
Founders
Built from complementary experience in operations and software.
Lorica was founded around a shared conviction that organizations should be able to work together without first becoming one organization or adopting one internal system.
Ben has spent his career building new operational capabilities and bringing organizations together around difficult problems. As a Marine intelligence officer, he rebuilt intelligence architecture for a new headquarters in Afghanistan and later led a multidisciplinary reconnaissance capability in the Indo-Pacific. He holds a BA from Middlebury College and an MBA from Harvard Business School.
Mitch is a software engineer with more than a decade of experience building production systems across startup and enterprise environments. His work has included cloud infrastructure, automated deployment systems, customer-facing applications, and audit-sensitive financial workflows. At Lorica, he leads platform engineering, security, and enterprise readiness.
Why the name
Lorica is a Latin term for body armor worn by Roman soldiers, including the legions of the Republic.
We chose the name because many of the people and institutions we serve are responsible for protecting others and sustaining the communities around them.
Armor strengthens the person wearing it without replacing their judgment or purpose. Lorica follows the same principle. We build infrastructure that helps independent organizations operate together while leaving authority and responsibility where they belong.
The institutions that protect communities are stronger when the networks around them are stronger.
Trust
Built for information your company needs to control.
Your team controls what is shared, who can access it, and how important activity is recorded.
Platform controls
✓Permissioned information sharing
✓Role-based access controls
✓Encryption in transit and at rest
✓Audit history for important activity and changes
Assurance
Independent penetration testing
Completed
SOC 2 Type I
Audit in progress
Security review
Ongoing
Lorica
See how Lorica fits your operating network.
Lorica works with private security organizations and municipal partners that need to coordinate across organizational boundaries without replacing the systems they already use.