Features

Everything Waddles ships with today.

Bot, Community, Loyalty & Workflows

One bot engine for Twitch, Discord, Slack, YouTube Live, Kick, Microsoft Teams, Mattermost, and Google Chat, plus native community spaces.

  • Bot module: shoutouts, commands, connectors, and interactions run on eight platforms β€” Twitch, Discord, Slack, YouTube Live, Kick, Microsoft Teams, Mattermost, and Google Chat.
  • Community module: forum, chat, virtual stages, polls, and announcements, so engagement can live in your own deployment.
  • Events flow through a fixed ingest β†’ process β†’ action pipeline of Rust services (svc-ingest, svc-process, svc-action) with svc-core handling identity, security, credentials, and entitlement.
  • Loyalty: per-community virtual currency earned from chat activity, watch time, follows, and subscription tiers, spent on minigames, PvP duels, and a gear/cosmetics shop; giveaways support reputation-weighted odds, and leaderboards rank by balance, lifetime earned, or wins. Every currency transaction is audit-logged.
  • Visual workflow automation: no-code, DAG-based workflows with triggers, conditions, loops, and platform actions, validated before execution and kept with full execution history. The free tier allows 1 workflow per community; Premium is unlimited.
  • The Marketing module (early release) adds campaigns, shortlinking, and emailing to the same platform.

App Bundle Marketplace

Vendor-submitted App Bundles run as WASI 0.2 WebAssembly components in a gVisor sandbox.

  • Vendors submit App Bundles for review; the marketplace manages submission, review, and lifecycle.
  • Bundles run as WASI 0.2 WebAssembly components in a credential-less executor under a gVisor (runsc) RuntimeClass, isolating third-party code from your credentials.
  • A three-tier lifecycle governs availability: installed βŠ† available βŠ† activated.
  • The model is layered Core β†’ Module β†’ Feature β†’ App (Bundle), so extensions slot into a defined structure.

Music Station, Presentation & Overlays

A per-community YouTube and Spotify queue with live OBS overlays, plus full_screen, media, and crawler overlay surfaces.

  • Music Station keeps a per-community queue that mixes YouTube and Spotify, with live OBS overlay integration.
  • Presentation & Overlays provides full_screen, media, and crawler overlay surfaces delivered as OBS browser sources.
  • Both are served by svc-presentation, the presentation stage of the pipeline.

Streaming Control Plane

RTMP/AV1 recording, transcoding, relay, and an RTC control plane in svc-streaming.

  • svc-streaming handles RTMP and AV1 recording, transcoding, and relay.
  • An RTC control plane manages real-time sessions and broadcast alongside the rest of the pipeline.
  • Streaming is the final lettered module of the SCCEMBS set.

AI Routing

Route AI work from free local models to metered local inference to bring-your-own-key providers. Token billing ledger: planned.

  • Model routing follows a free-local β†’ metered-local β†’ BYOK order, so you decide where AI work runs.
  • Planned: a single token billing ledger covering streaming transcode and premium AI tokens. It is design-only today and not available.
  • Qdrant is part of the data stack for search and AI workloads.

Analytics, Trust Scoring & Bot Detection

Engagement analytics, 300–850 trust scoring, and confidence-scored bot detection.

  • Free tier: basic statistics (chatters, stream time, messages per user), 7-day and 30-day active user counts, and real-time activity ingestion from every platform module.
  • Premium: composite A+ through F community health scoring, bad-actor detection and flagging, cross-session user-journey tracking, retention cohort analysis, and engagement funnel analytics.
  • A FICO-style 300–850 trust score is built from behavior and can drive warnings and moderation thresholds.
  • Bot-detection scoring combines four weighted signals into a 0–100 score that moderators can review and override.

Hub Admin Portal, Multi-Tenant & RBAC

An Express + React 18 portal on a Python 3.13/Quart hub-api, with community-isolated data and role-based access.

  • hub-webui is built on Express with React 18, Vite, and Tailwind v4; it talks to hub-api, a Python 3.13/Quart control plane.
  • Each installation hosts multiple independent communities, each with its own members, roles, settings, and connected platforms, keyed by community_id.
  • Role-based access control follows a resource:action permission format, with a default role hierarchy of admin, community_owner, moderator, and user.
  • Broadcast announcements push to every connected platform at once; security middleware includes Helmet, CSRF protection, rate limiting, and XSS filtering.

Kubernetes, Helm & Observability

Docker and Kubernetes (Helm v3) deployment of an 8-container pipeline, with structured logging and metrics.

  • The fixed 8-container pipeline β€” six Rust services plus hub-api and hub-webui β€” runs on Docker or Kubernetes with Helm v3 charts.
  • The data spine is Valkey Streams (TLS + ACL), with PostgreSQL, Valkey, MinIO (S3), and Qdrant as stores.
  • Every service logs Authentication, Authorization, and Audit (AAA) events in a consistent structured format, with sensitive fields redacted before any log line is written.
  • Suggested retention: 2 years for AUTH/AUTHZ security logs, 7 years for audit logs in compliance-sensitive deployments, 90 days for system logs.

SDK & Mobile Apps

Build custom modules with the module template, and manage communities from native iOS and Android apps.

  • New modules follow the same structure every shipped module uses β€” a Quart REST app, environment-driven config, Pydantic validation, and a PyDAL-backed per-module database account.
  • Native apps ship for Android (Kotlin, Jetpack Compose, Android 8.0+) and iOS (Swift, SwiftUI, iOS 16+), both using MVVM with the same Hub API the web portal uses.
  • Mobile features: JWT-based auth with refresh, community management, real-time WebSocket chat with typing indicators and paginated history, and a member directory.

Customer (CRM) β€” Coming in v3

Coming in v3: accounts, contacts, opportunities, pipelines, and cases. Not yet available.

  • Coming in v3: accounts and contacts so public-facing teams can track who they are talking to across community and support channels.
  • Coming in v3: opportunities and pipelines, plus cases for customer support.
  • This is a greenfield module on the roadmap. Treat every item above as roadmap intent, not a shipped feature; no date is committed.

Event β€” Coming in v3

Coming in v3: event and conference management. Not yet available.

  • Coming in v3: event and conference management as a first-class module of the SCCEMBS set.
  • This is a new module on the roadmap. Treat it as roadmap intent, not a shipped feature; no date is committed.
  • Live community stages and polls are available today in the Community module.

Socials β€” Coming in v3

Coming in v3: external social media management for LinkedIn, X, Facebook, Instagram, and TikTok. Not yet available.

  • Coming in v3: manage external social media accounts on LinkedIn, X, Facebook, Instagram, and TikTok alongside your community platforms.
  • This is a new module on the roadmap. Treat it as roadmap intent, not a shipped feature; no date is committed.
  • Chat-platform bots (Twitch, Discord, Slack, and more) are available today in the Bot module.

Full technical documentation β†’