Modules

Provider-neutral channel responder and shared external chat runtime for direct messages and shared chat channels.

Google login provider for kickside/sso.

Links a provider account (Discord, Slack, Telegram, and others) to a KickSide user through short-lived dashboard-issued codes, so any bot resolves an external sender provider-neutrally.

User management and security tokens

User single sign-on via OAuth2/OIDC identity providers.

File upload handling with content processing and resource management

Bounded audience dispatch through the selected realtime owner

KickSide execution identity — the one principal codec, delegation encoding and live run-as path

KickSide Data Sync automation kind — source-to-destination synchronization built on the shared automation engine.

KickSide UI — platform navigation API plus admin UI surfaces. Ships the kickside-appearance web component (a System tab) that edits navigation layout, categories, and per-surface overrides backed by kickside.ui settings.

KickSide KB10 — the document/graph knowledge-base engine. Owns the kb10_* schema and node/edge/embedding store, durable embeddable/queryable/deletable bindings, and the kb_store engine contract used by kickside/knowledge.

KickSide Hub — module discovery and lifecycle management. Ships the kickside-hub System surface plus a standalone onboarding component that recommends real catalog modules and reviews selected installs sequentially through Keeper.

KickSide realtime — a centralized contract for pushing topics to connected UIs. broadcast() fans out to every client via the wippy/relay central hub; notify() targets one user's hub. Any module (nav, inbox, …) publishes through one seam so all UI reacts live.

Per-user first-agent onboarding with the installed agents capability catalog.

KickSide sessions — a self-contained web component that lists the user's chat sessions and lets them rename, resume, restart, preview, and delete. Reuses the wippy/session API; ships a single start-token endpoint for "new chat with the same agent".

Object-neutral CRM infrastructure for KickSide. Business modules declare typed object and relation tables; CRM supplies transactional schema editing, native search, imports, events, Blocks, agent tools, APIs, and maintained web components.

KickSide MCP — user- and workspace-scoped Model Context Protocol endpoints. A user mints a scoped bearer credential whose synthetic principal is granted, over a chosen component subtree (their account root or a workspace slice), only the access the owner themselves holds. A single stateless streamable-HTTP endpoint multiplexes every credential; two-layer authz (tool allowlist + the native component access model) gates each call. Tokens are hashed at rest and shown once.

Optional visual authoring, versioning, and run lifecycle for published Workflows composed from canonical Blocks and native Dataflow nodes.

Task scheduling service with interval and cron support, plus live scope resolution

One tree of typed entries modelled as components with an access cascade, declarative entry types that each own a renderer and lifecycle, and the workspace shell web component.