---
sidebar_position: 0
title: Myop for Enterprise
sidebar_label: Overview
description: What Myop offers enterprise teams — automation from your own systems, on-premises and air-gapped deployment, isolation of untrusted UI, controlled rollout, a full audit trail, and access control with scoped keys.
keywords: [myop enterprise, enterprise ui platform, on-premises, air-gapped, component management api, ui governance, audit trail, scoped api keys, self-hosted components, regulated industries]
---
# Myop for Enterprise

Myop lets product, marketing and operations teams change what users see without a release. Enterprise
teams need that to fit how they already work: driven by their **own systems**, running on **their own
infrastructure**, with **control and a record** of every change. This section covers each of them.

## Run it where you need it

### On-premises and air-gapped

All of Myop as one Docker image on your own hardware, delivered offline into a closed network, with no
internet access and no outbound traffic at runtime. Built for banks, government and other regulated
environments.

[On-premises & air-gapped →](/docs/enterprise/on-premises)

### Serve components from your own infrastructure

Keep managing components in the Myop cloud, but serve them from your own CDN or bucket (S3, CloudFront,
Azure Blob Storage, GCS), with no runtime dependency on Myop servers. Releases reach your CDN through
GitHub Actions or a webhook to your own pipeline.

[Self-hosting →](/docs/self-hosting)

## Automate and integrate

### Automate components from your backend

Create, clone, publish and update components and flows from your own backend, CMS or internal tools with
an organization API key. A campaign tool can clone a banner with a new URL, add it to a page and publish
it, all in one script.

[Automate from your backend →](/docs/enterprise/automate-components)

### Git integration

Connect a flow to a GitHub repository and every publish opens a pull request with the resolved
configuration, so UI changes go through the review process your engineers already use.

## Control what runs and who sees it

### Isolate untrusted components

Decide per component how much of your page it can reach, up to a sandboxed cross-origin iframe with no
access to your DOM, cookies or storage. Code from outside your organization never has to run on your page.

[Component isolation →](/docs/enterprise/isolation)

### Get components built outside your organization

Let agencies, freelancers and partners build a component for you without any access to your
organization. Share one component through a private link, review what they submit, and take only the
version you choose.

[Marketplace →](/docs/enterprise/marketplace)

### Environments and controlled rollout

Release through your own environments, see drift from production on one board, and target versions to
user segments with A/B splits, without deploying your application.

[Environments & rollout →](/docs/enterprise/environments-and-rollout)

## Know what happened

### Audit and version history

Every change is a new version, never overwritten. See who changed and who released what, compare any two
versions, and attribute automated changes to the key that made them.

[Audit & version history →](/docs/enterprise/audit-and-history)

### Usage analytics

See how often each component loads, in which environment and on which domains, so you know what is live
and where before you change it.

## Security and access control

- **Scoped API keys.** Each key can do only what its scopes allow. New keys can export components and
  nothing else; the ability to change components and flows is granted per key.
- **Admins manage keys.** Only organization admins can create, list or revoke API keys and change
  self-hosting settings, in the dashboard and on the server.
- **Instant revoke.** A revoked key stops working on its next request.
- **Organization isolation.** A key acts only inside the organization that created it.
- **Team roles.** Members are admins or members; an organization always keeps at least one admin.

[API keys reference →](/docs/self-hosting/api-keys-webhooks)

## Fast for your users

Resolve component configuration on your server and render with no extra network round trip on the
client, for React and Next.js applications.

[SSR & server-side config →](/docs/learnMyop/ReactHostSSR)

## Built for your environment

Single sign-on, custom roles, data residency, audit export to your SIEM, private networking,
integrations with your own tools and contractual service terms are built for your organization as part
of your enterprise agreement.

[Custom integrations →](/docs/enterprise/custom-integrations)

## Talk to us

Enterprise features are enabled per organization. To turn them on, or to see how they fit your setup,
[book a technical intro](https://calendly.com/hadar-myop/myop-technical-intro).