Self-hosting

Yes, if you're on Embed Partner. Self-hosting runs the Embed application inside your own infrastructure instead of on Coassemble-managed servers, so the runtime sits entirely within your network and under your control. It's available on Embed Partner only, not on Embed Core or Embed Automate.

Why teams self-host

Self-hosting is usually driven by one of these needs:

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

What Coassemble provides, and what you provide

Coassemble provides a container image with the full Embed runtime. You provide everything it runs on:

• An environment to run the image. Any infrastructure you choose (cloud, on-premise, or a private region), sitting entirely within your perimeter.
• A PostgreSQL database. Provisioning, backups, security, and location are yours to manage.
• All keys and secrets for the third-party services the application uses. These are supplied to the image at startup as configuration you control. They are never provided to Coassemble, which means Coassemble does not receive, store, or hold a copy of them at any point.

Does self-hosting change how Embed works?

No. Access is through your own domain rather than a Coassemble URL, but beyond that the API surface, embeddables, authoring, AI features, tracking, SCORM, themes, multi-tenancy, and webhooks all behave identically to hosted Embed. Your integration code doesn't change between the two.

Who is responsible for what?

You handle infrastructure provisioning, scaling, monitoring, database administration, security of the runtime environment, and applying published updates. Coassemble maintains the application, publishes updates, and provides Embed Partner engineering support. Coassemble does not access your environment.

Licensing

The license grant is non-exclusive, non-transferable, object-code only, for your own use. It does not permit hosting Coassemble for third parties outside your own product relationship, and it does not permit reverse engineering, decompiling, or circumventing license checks. Coassemble retains all intellectual property in the Coassemble applications.

Things to know before you commit

• Your server choice is permanent. There is no supported migration path between server options, so the decision to self-host has to be made before any infrastructure is provisioned.
• Self-hosting is not something you opt into through a standard order. Because requirements vary, it starts with a scoping conversation with the Coassemble team.

That conversation covers the driver for self-hosting (and whether a managed option would also meet it), your infrastructure and operational capability, the third-party services you'll supply credentials for, how new versions of the image are applied, and the commercial terms.

Common questions

Is self-hosting available on Embed Core or Embed Automate?

No. Self-hosting is an Embed Partner option only. Embed Core and Embed Automate run on Coassemble-managed servers.

Can I move to self-hosting later?

Server choice is permanent and there's no supported migration path, so it needs to be decided up front, before infrastructure is provisioned.