Key Concepts

Keep'em is built around a hierarchy of concepts that organize your content, viewers, and data. Understanding these will help you get the most from the platform.

Organization

An organization is your top-level account. It handles billing, team management, and serves as the container for everything else.

Every Keep'em account has at least one organization. If you're a solo founder, you'll have one. Agencies managing multiple clients might have one organization per client, or use one organization with multiple projects.

Organizations have roles: Owner (full access including billing), Admin (manage projects and members), and Member (participate based on project assignments).

Project

A project sits inside an organization and groups your events under a shared brand identity. Each project has its own colors, logo, custom domain (Growth and above), and settings.

Think of a project as a branded container. If you have one product, you have one project. If you have a main product and a separate training portal, those might be two projects with different branding.

Projects also scope your API keys — each project has its own publishable and secret keys.

Event

An event is a single interactive video experience. It combines your video content, AI knowledge base, and viewer configuration into something people can watch and interact with.

Events come in three types:

• On-demand — Always available. Viewers watch whenever they want.
• One-time — Scheduled for a specific date and time.
• Recurring — Repeats on a pattern (weekly, monthly, etc.).

Each event has its own analytics, viewer list, and chat history.

Registration

A registration links a viewer to an event. When someone signs up to watch your video — either through a registration form or programmatically via your API — a registration record is created.

Registrations track cumulative engagement: total watch time across all viewing sessions, completion status, and contact information.

Viewing Session

Each time a registered viewer opens your video, a new viewing session is created. A single registration can have many sessions — someone might watch half today and come back tomorrow.

Sessions track per-visit data: start time, watch progress, drop-off point, and chat messages sent during that session.

Conversation and Messages

When a viewer asks a question in the chat, it becomes part of a conversation linked to their viewing session. Messages are attributed to either the viewer (USER) or the AI assistant (ASSISTANT).

Messages carry context: which video was playing, what timestamp the viewer was at when they asked, and what transcript/document chunks the AI used to generate its response.

API Keys

Each project has two types of API keys:

• Secret keys (sk_live_*) — For backend-to-backend calls. Full permissions. Never expose these in client-side code.
• Publishable keys (pk_live_*) — For client-side widgets. Limited permissions. Safe to include in frontend code.