Self-hosting
What self-hosting Coassemble Embed involves: who it's for, what Coassemble provides, what you provide, and how to start the conversation.
Yes, on the Partner plan. Self-hosting is available to Partner plan customers only, on request. It 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 isn't something you opt into through a standard order, so it starts with a scoping conversation with the Coassemble team.
Why do 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 does Coassemble provide, and what do 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 work the same way as 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 engineering support. Coassemble does not access your environment.
What are the licensing terms?
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.
What should I know before I commit?
- Self-hosting is available on the Partner plan only, on request.
- Decide on your server option with the Coassemble team before you set anything up, including any infrastructure for self-hosting.
- Self-hosting starts with a scoping conversation with the Coassemble team, because requirements vary.
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
Which plan includes self-hosting?
Only the Partner plan, and only on request. Talk to the Coassemble team to start a scoping conversation.