Embed Partner is the plan for organisations where Coassemble is core infrastructure rather than a feature inside a product. With Embed Partner you get dedicated hosting (or region-locked, or self-hosted), a fully negotiable Master Services Agreement, negotiated commercial terms across pricing, IR commitment and allowances, dedicated account management, and go-to-market support where it makes sense for both sides. The full Coassemble API and every embeddable are part of the plan, the same as on Embed Automate.

Embed Partner is the plan for organisations where Coassemble is core infrastructure rather than a feature inside a product. With Embed Partner you get dedicated hosting (or region-locked, or self-hosted), a fully negotiable Master Services Agreement, negotiated commercial terms across pricing, IR commitment and allowances, dedicated account management, and go-to-market support where it makes sense for both sides. The full Coassemble API and every embeddable are part of the plan, the same as on Embed Automate.

Use Embed Partner when the relationship is strategic and the integration needs depth beyond what a fixed plan can offer. Common scenarios: a regulated business with strict data residency requirements (UK or EU only), a large enterprise platform running Coassemble on dedicated infrastructure for security and isolation, a strategic partner with joint go-to-market alignment, a company at significant scale where commercial terms genuinely need to be bespoke, or a deployment where self-hosting Coassemble inside the partner's own infrastructure is the right architecture.

## Who is Embed Partner for?

Embed Partner suits an executive or senior commercial buyer at an organisation where Coassemble is a strategic dependency. The customer profile is typically a regulated business, a large enterprise platform, or a partner running content at significant scale, where the relationship involves legal negotiation, dedicated implementation, and a long-term commitment in both directions.

The decision to move to Embed Partner is rarely driven by a single feature. The API capabilities are identical to Embed Automate's. It is driven by infrastructure requirements (dedicated or region-locked hosting), legal requirements (MSA-level contract terms), or commercial requirements (custom-negotiated pricing, partnership economics, joint go-to-market).

## What you can do on Embed Partner

Embed Partner includes everything from Embed Automate, plus the partnership layer.

### Dedicated infrastructure

* **Dedicated server.** A private, single-tenant environment, optionally region-locked. Your workspace runs on infrastructure dedicated to your organisation, not shared with other Coassemble customers. Use this when you need infrastructure-level isolation for compliance, security, or contractual reasons.
* **Region-locked server (UK or EU).** Data processing and storage confined to the specified region. Use this when you have data residency requirements that prevent data from leaving a region.
* **Self-hosting.** Coassemble running inside the customer's own infrastructure. This is a deeper conversation than the other options and involves additional approval at our end before it can proceed.

Two notes on regional and self-hosted setups. First, region-locked configurations are not compatible with Slack or Microsoft Teams integrations, because those integrations involve cross-region data flow. Second, self-hosting needs additional approval before we engage on it, so the conversation will involve more than your account team.

### MSA (Master Services Agreement)

Embed Partner moves you off the Order Form model and onto a full MSA. The contract is fully negotiable. Indemnification, intellectual property ownership, liability caps, security provisions, and data breach notification timelines are all on the table. Expect a two to six week legal review cycle, depending on how heavy the redlines are. A DPA is included and negotiable.

### Negotiated commercial terms

Pricing on Embed Partner is fully negotiated. The platform fee starts at a defined floor and scales based on the IR commitment, AR allowance, AI allowances, infrastructure choices, and partnership terms agreed during the commercial conversation. IR overage rates are derived the same way as on the other Embed plans (platform fee divided by committed annual IR volume), but the inputs themselves are negotiated rather than fixed. Reference figures live on the pricing page.

### Go-to-market support and dedicated account management

Embed Partner customers get a named account manager and dedicated technical support, alongside go-to-market support for the integration where it makes sense (joint customer stories, co-marketing, partnership-level engagement).

### Implementation

Dedicated implementation support is part of Embed Partner. The team helps stand up the integration and stays engaged from day one.

### Security and trust

Everything Embed Automate has, plus the security and compliance posture that comes from running on dedicated or region-locked infrastructure.

## Usage allowances on Embed Partner

| Allowance | What is included |
|----|----|
| Course creators | Unlimited |
| Courses | Unlimited |
| Identified Recipients (per year) | Fully negotiated (reference tiers: 500, 2,000, 10,000 per month) |
| Anonymous views (per month) | Negotiated |
| AI narration (tokens per month) | Negotiated (reference floor: 25,000,000 premium voices) |
| AI image generations (per month) | Negotiated (reference floor: 15,000) |

A few notes.

Reference values exist as a starting point for the commercial conversation, not as fixed allowances. IR commitment tiers, AR allowances, and AI metric allowances are all negotiated as part of the contract.

Anonymous views and AI metrics are soft-capped, the same as on Embed Core and Embed Automate. If you exceed the allowance, anonymous access and AI generation continue. The breach is tracked and the conversation about adjusting your allowance happens commercially.

## What Embed Partner does not change

Worth being explicit about this, because the question comes up: Embed Partner does not unlock new API capabilities beyond Embed Automate. The full API surface is already available on Embed Automate. If your reason for considering Embed Partner is a specific API capability you cannot find on Embed Automate, the most likely answer is that the capability does not exist, rather than that it is gated behind Embed Partner.

What Embed Partner changes is the commercial, infrastructure, and partnership layer, not the product surface.

## How the Embed Partner conversation works

Embed Partner is not a self-serve plan. The conversation goes through our commercial team, and typically involves:


1. An initial scoping discussion: what you are building, what your scale looks like, what your infrastructure and compliance requirements are.
2. A technical conversation about API, embeddable, and infrastructure fit.
3. A commercial conversation about pricing, IR commitment, allowances, and partnership terms.
4. Legal review: MSA redlines, DPA negotiation, and the surrounding agreement work.
5. Implementation and handover to the dedicated account team.

For pricing reference points and the full plan range, see [coassemble.com/pricing](https://coassemble.com/pricing). For an Embed Partner conversation specifically, contact your account team or reach out through the pricing page.

Embed Partner

Flow

Pulse

Embed Core

Embed Automate

Overage, bands, and rates

Payments, billing, and subscriptions

Plans and advanced features

Release notes

General

What is Coassemble?

Coassemble terminology explained

Accessing the login page

Getting to know your Coassemble workspace

Build the business case for Coassemble

Getting started: Common questions

How do I sign up for a Coassemble account?

What file types can I transform into a course?

What is a screen?

What tone should I select?

What is a collection?

Can I use Coassemble as an LMS?

How to log in to your account

Getting started

Connecting to Google Drive or OneDrive

Convert a presentation into an online course

Your knowledge

Usage limits

Identified Recipients and Anonymous Recipients

Logging in with Microsoft

Folders

Creators

Transfer ownership of your workspace

Configuring your email preferences

Common questions: Workspaces

How to delete a creator

Managing account, workspace, and billing settings

Organizing courses with folders

Your workspace & settings

How to upload custom fonts in Coassemble

How to save a legacy course theme

Brand kit: Saving pre-existing themes

How to apply Brand voice when generating courses

Brand voice

Asset library

Managing logos

How to create and configure themes

Managing and defaulting themes

Using the Brand kit

Brand Kit: A complete guide

How to edit video details

Brand kit

AI image generation

Generate a screen with AI

Refine with AI

Difference between transforming a document and converting a presentation

Coassemble's AI

Screens

Creating courses from scratch

Deleting courses

Duplicating courses

Enforce completion of videos

Generate a course with AI

The Finish screen

The Quiz screen

Transforming a document to a course

Translations

Images

Upload your videos to your course

Which screen should I use?

How do I create a course?

Common questions: Course creation

How to Upload Videos to Your Course

Narrating translations

Narration

Publishing

Loom integration

How to preview and review a course

Customizing course appearance with Themes

Managing and editing your course

Guide to AI Narration Tokens in Coassemble

Create & customize

Sharing course links & invitations

Collections: create, customize, share, and track learning paths

How to import a course from a template link

How to share your courses

Sharing courses with Slack

SCORM packages and translations

Exporting courses as SCORM

Common questions: Sharing

Template links

Email invitations

How to Add Your Coassemble Courses to Another Platform

How Coassemble tracks unique anonymous users

Sharing

How to filter Course insights by date range

Course insights

Link Insights

SCORM usage

Common Questions: Tracking Learners, Reporting, and Limits in Coassemble

Detailed Quiz results

Sentiment

Analyzing course-level Insights

Analyzing Collection-level Insights

Tracking content performance with Insights

Insights

Explore best practices for sharing your knowledge.

Accessibility

Assessment: Best practice for quizzes

Coassemble is WCAG 2.2 Level AA Conformant

Best practices

SCORM files not loading

SCORM session errors on Apple devices

Why isn't my Embed screen working?

Common questions: Troubleshooting

What do I do if there is a bug?

Requesting a password reset link

Setting a new password

How to change or reset your password

Troubleshooting

SOC 2 compliance

Coassemble's approach to AI

AI & data security

Data security & AI

API keys

Passing identity (and tenant context) in embedded sessions

Notion

YouTube

Hubspot

Arcade

Vimeo

Unsplash

360Learning

aNewSpring

Docebo

Embed and Stripe: How to Sell Access Using Your Own Checkout and Coassemble Embed

Connections & Integrations

Upcoming plan changes

Updates and communication

Resources specifically for Embed (previously referred to as Headless course creation). These are resources that previously lived on the Headless Resources Hub.

Coassemble Embed Partner Security, Data Protection & AI FAQ

Default usage caps for clients

Managing tenant caps

Accessibility guide

AI and Data Security for Coassemble Embed Partners

Coassemble vs. Articulate: Feature comparison guide for course authoring teams

Competitor analysis

Designing effective microlearning courses

How to access and interpret the Headless usage report

How to handle competitor objections when positioning your Embed solution

Guide to pricing models for Coassemble Embed and key competitor benchmarks

Sales enablement guide: Driving user adoption

Customer testimonials for Coassemble Embed course creation (sales enablement)

Our mission: Barrier-free knowledge transfer (partner-friendly positioning language)

Embed Partner

Share

Share

Embed Partner

Share

Share