Latch Vector

Sandbox access

Thirty days on a real tenant

A temporary organization with the full platform behind it — SSO, orgs, roles, webhooks, audit trail. No card, no production data. How the 30 days work →

Regulated and professional software only — see our Acceptable Use Policy.

Sandbox request received

About

One came out of the other.

Every regulated platform we built needed the same identity layer, so we turned ours into a product. 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.

People you can talk to

Who picks up.

Commercial questions, partner slots and anything to do with how the platform is packaged and priced go to one address and get a reply within a business day. Technical questions skip that queue and go straight to the engineers who wrote the code.

You'll meet the people behind both on your first call. Roles are described below rather than named, and the SDKs they wrote are public, so you can read the work before you meet anyone.

Engineering

Described by what they do.

Backend & Architecture

Senior Engineer

Laravel and Python in production for 7+ years. System design, service boundaries, and the multi-tenant data models regulated platforms are built on.

Healthcare Data & Integration

Senior Engineer

Claims pipelines, documentation intake, and integrations with established DME platforms. Fluent in LCD/NCD verification and payer-specific edits.

Platform & Infrastructure

Senior Engineer

Containerization, CI/CD, and the deployment pipeline behind the hosted platform. Keeps deploys boring and keeps systems handling regulated data scoped, logged and auditable.

Continuity

The question you were about to ask.

You are putting your login path on someone else's infrastructure. Here is what that commits you to, and what it doesn't.

IP ownership
All platform IP is owned by Latch Vector LLC, outright
SLA
Contractual on paid plans; response-time targets from Scale up
Token verification
Local, against JWKS — your request path never calls us
Your data
Exportable over the same REST API you integrate against

Verification is local by design. Your services check each token themselves against a published JWKS endpoint, so the thing standing between your users and your product is a signature check inside your own process. See the integration →

Legal entity

Who you are contracting with.

Entity
Latch Vector LLC
Registered address
75 East 3rd Street, Sheridan, WY 82801, United States
EU hosting
Germany, on Hetzner, by default for EU production
Contact

Start a conversation.

Email [email protected]
Response time

Within one business day

Or

Book a 15-min live demo with an engineer