---
title: "Self-hosting Coassemble Embed"
description: "Self-hosting is one of the server options available to Embed Partner customers. It allows the application to run inside the partner's own infrastructure rather than on Coassemble-managed servers."
canonical_url: "https://support.coassemble.com/articles/self-hosting-coassemble-embed-a2W5QrblJ0"
md_url: "https://support.coassemble.com/articles/self-hosting-coassemble-embed-a2W5QrblJ0.md"
---
# Self-hosting Coassemble Embed

Self-hosting is one of the server options available to Embed Partner customers. It allows the application to run inside the partner's own infrastructure rather than on Coassemble-managed servers.

It is offered only to Embed Partner customers. It is not available on Embed Core or Embed Automate.

### **Typical reasons partners consider self-hosting**

* Data residency requirements beyond the regions Coassemble offers as managed options
* Security or compliance obligations that require the application to run inside the partner's own network
* Sovereignty requirements that need the runtime under the partner's direct control

### **What Coassemble provides**

A container image of the Embed application. The image contains the full Embed runtime.

### **What the partner provides**

* An environment to run the image. This can be any infrastructure the partner chooses (cloud, on-premise, private region) and sits entirely within the partner's perimeter.
* A Postgres database. Provisioning, backups, security, and location are the partner's responsibility.
* All keys and secrets for the third-party services the application uses. These are supplied to the image at startup as configuration the partner controls. They are not provided to Coassemble.

Because the third-party credentials are injected at mount time, Coassemble does not receive, store, or hold a copy of them at any point.

### **Functional parity with hosted Embed**

Access is through the partner's own domain or wherever the application is hosted within their infrastructure, not through a Coassemble URL. Beyond that, the API surface, embeddables, authoring, AI features, tracking, SCORM, themes, multi-tenancy, and webhooks behave identically to hosted Embed. Integration code does not change between the two deployments.

### **Responsibilities**

Partner: infrastructure provisioning, scaling, monitoring, database administration, applying published updates, and security of the runtime environment.

Coassemble: maintaining the application, publishing updates, and providing Embed Partner engineering support. Coassemble does not access the partner's environment.

### **Important constraints**

* Server choice is permanent; we don’t offer a supported migration path. 
* The decision to self-host must be made before any infrastructure is provisioned.
* All self-hosting conversations require sign-off from Coassemble leadership before they progress.

### **Licensing and IP**

* License grant: non-exclusive, non-transferable, object-code only, for the partner's own use. The license does not permit hosting Coassemble for third parties outside the partner relationship.
* Restrictions: no reverse engineering, decompiling, or circumventing license checks.
* IP ownership: Coassemble retains all intellectual property in the Coassemble applications.


### **Next steps**

Self-hosting is not something a partner can opt into through a standard order. Because the server choice is permanent and the requirements vary by partner, the first step is a scoping conversation with the Coassemble team.

That conversation covers:

* The driver for self-hosting and whether a managed option would also meet the requirement
* The partner's infrastructure, security, and operational capability
* The list of third-party services the partner will need to provide credentials for
* The update cadence and how new versions of the image are applied
* Commercial terms and the agreement structure