A high-level view of what running self-hosted Embed on AWS involves. Specifics are confirmed during the scoping conversation with Coassemble engineering, based on the partner's expected user volume and media load.

A high-level view of what running self-hosted Embed on AWS involves. Specifics are confirmed during the scoping conversation with Coassemble engineering, based on the partner's expected user volume and media load.

### **What Coassemble provides**

A container image of the Embed application, plus reference Terraform that can serve as a starting blueprint.

### **What the partner provisions on AWS**

* Container compute for the Embed runtime (ECS on Fargate or EKS), behind an Application Load Balancer.
* A managed PostgreSQL database (RDS or Aurora).
* Optionally, a managed Redis-compatible cache (ElastiCache). The application falls back to an in-memory cache when no Redis is provided
* An S3 bucket for media, fronted by CloudFront served from a partner subdomain.
* AWS Elemental MediaConvert for video processing.

All components of an Embed deployment (compute, database, cache, storage, media) sit in a single AWS region of the partner's choice.

### **Sizing**

Partner setups will vary in size. For reference, Coassemble's own production runtime sits at roughly 4 CPU / 8 GB RAM for the backend, 0.5 CPU / 512 MB for the frontend, and 2 CPU / 8 GB for the database. Many partner deployments will run on less, depending on their setup and expected user volume. Final sizing for compute, database, and bandwidth is confirmed during scoping.

### **Third-party services**

Embed relies on a handful of external SaaS services to do things like send emails, generate AI content and narration, and capture errors. In a self-hosted deployment, the partner holds their own accounts with those vendors and supplies their own API keys. For example, the partner would bring their own Google account for the Gemini and Chirp models that power AI features and narration, alongside accounts for email delivery, document conversion, monitoring, and any optional services tied to features they enable.

Keys are injected into the container at startup and are never provided to Coassemble. The exact list of services to supply credentials for is confirmed during scoping, as it shifts slightly release to release and depends on which features the partner turns on.

### **Scope**

Self-hosting here means the Embed application runs inside the partner's own cloud, while still calling out over the public internet to the third-party SaaS services it depends on. Coassemble does not currently support a fully air-gapped deployment with no external network access.

### **Partner responsibilities**

Provisioning, scaling, monitoring, database administration, security of the runtime, and applying published updates.

These are indicative initial requirements, not a committed specification. Self-hosting requires a scoping conversation, and server choice is permanent with no supported migration path.




Initial AWS requirements for self-hosting

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

Coassemble is WCAG 2.2 Level AA Conformant

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)

Getting started guide

How to communicate Coassemble feature releases to your customers 

How to migrate courses from other authoring tools into Coassemble Embed

Guide to releases

Curate

AI Create

Customize

Learner experience

Self-hosting Coassemble Embed

Embed Partners

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

Flow

Pulse

Embed Core

Embed Automate

Embed Partner

Overage, bands, and rates

Payments, billing, and subscriptions

Plans and advanced features

Explore best practices for sharing your knowledge.

Accessibility

Assessment: Best practice for quizzes

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

Initial AWS requirements for self-hosting

Share

Share

Initial AWS requirements for self-hosting

Share

Share