28 lines
1.6 KiB
Plaintext
28 lines
1.6 KiB
Plaintext
---
|
|
title: "Enterprise"
|
|
description: "Deploy OpenWork on your own infrastructure"
|
|
---
|
|
|
|
Want to run OpenWork on your own infra? We'll help you get there.
|
|
|
|
OpenWork can be deployed inside your VPC or on-prem, with SSO, audit logs, and controls over which models and tools your team can use. If you're exploring a self-hosted or private-cloud rollout, talk to us.
|
|
|
|
<Card title="Book a call with our team" icon="calendar" href="https://calendar.app.google/86QpCENvhfEzDFLu5">
|
|
Schedule a 30-minute intro at [calendar.app.google/86QpCENvhfEzDFLu5](https://calendar.app.google/86QpCENvhfEzDFLu5) to scope your deployment.
|
|
</Card>
|
|
|
|
## What we'll cover
|
|
|
|
- Your target environment (cloud provider, VPC, on-prem)
|
|
- Identity, access, and audit requirements
|
|
- Model and tool allowlists
|
|
- Rollout plan and support model
|
|
|
|
Prefer email? Reach us at [team@openworklabs.com](mailto:team@openworklabs.com?subject=Enterprise%20deployment).
|
|
|
|
## How desktop deployment works
|
|
|
|
Rolling OpenWork out to a fleet does not involve a custom installer build. You deploy the standard **OpenWork Enterprise binary** — a dedicated distribution that requires sign-in and administrator activation, on its own update channel — and optionally push a single `desktop-bootstrap.json` file through your MDM so every machine targets your Den server on first launch. Certificates come from the OS trust stores you already manage, and desktop policies are delivered by the server after sign-in, so no MDM scripting is needed beyond that one file.
|
|
|
|
See [Enterprise desktop deployment](/start-here/enterprise-desktop-deployment) for the full reference.
|