Latch Vector
Regulated software engineering

We build systems where the boundary has to hold.

Multi-tenant identity infrastructure for software that handles regulated data, and the senior engineers who build the systems around it. Healthcare, fintech, and the platforms underneath them.

Any depth, any branch, including one provisioned by the root but walled off from it too. → See how isolation works
Identity platform

Multi-tenant SSO and authorization, as a service

Single sign-on, hierarchical tenancy, and granular permissions through one REST API and SDKs for PHP, Python, Node, and Java. Tenant isolation enforced in three independent layers, encryption with searchable blind indexes, MFA, and an append-only audit trail.

Building this in-house costs quarters of senior engineering and ships no revenue on its own.

Engineering services

Senior engineers for regulated systems

We build and maintain the software DME and HME providers bill, document, and get paid with: documentation intake, clean-claim rules, denial and appeal logic, remittance and reconciliation. The same engineering carries into fintech and enterprise platforms.

One team, end to end, and it stays after launch.

Why both

One came out of the other.

Every regulated platform we worked on needed the same thing: tenants that can't see each other, permissions that match a real company hierarchy, and an audit trail an auditor will accept. We rebuilt it enough times to stop rebuilding it.

So you can use the platform, hire the team, or both. Either way you're talking to the people who wrote the code.

115 Isolation tests against a real database
9,700 rps Sustained, verified against 1,000,000 organizations
4 Official SDKs: PHP, Python, Node, Java
BAA Signed on request, on the Regulated plan
Contact

Start a conversation.

Response time

Within one business day