Skip to content

Deploy OpenLatch

This section takes you from nothing to a working deployment: create the organization, connect your identity provider, deploy the client to every machine that runs an agent, and set the console up for the people who will use it. It is written so that you can do the work without a call.

You want toRead
Understand what OpenLatch is and what runs whereIntroduction · Architecture
Prepare: what to have on hand, and the one outbound destination to allowPrerequisites · Network requirements
Install: the organization, the client on each machine, verification and rolloutConfigure the organization · Deploy the client · Verify and roll out
Keep it runningOperate
Answer a security review, and the questions that follow itData handling and security · Deployment FAQ
Look something upTerms and egress

Read it in order the first time. The introduction and the architecture page explain what OpenLatch is and what runs where; they are enough to answer a first review before anything is installed. The prerequisites and the network requirements are what you prepare in advance: the values to have on hand, and the one outbound destination to allow. The next three pages are the installation itself, from the first sign-in to a verified rollout, and Operate covers what comes after it.

Data handling and security sets out what OpenLatch handles, stores and never collects. It is the page to hand to a security review. The Deployment FAQ answers the questions that follow, and Terms and egress holds the terms and the egress table.

Every page in this section prints on its own, without the site’s navigation, so you can attach it to a change request or a review.

Send corrections and gaps to hello@openlatch.ai, naming the page. Security reports take a separate route: send them to security@openlatch.ai. OpenLatch acknowledges a security report within two business days.