AIOHM Platform

Appearance

Platform Features ​

This page maps the main capabilities of the AIOHM Platform so the public /docs/features/ route has a stable home in production.

Muse ​

Muse is the platform's private AI partner. It keeps long-running context, reads your brand knowledge, and helps with research, planning, writing, and execution.

  • Uses your brand book and knowledge base as working context
  • Can delegate tasks to specialist agents when the job needs deeper tooling
  • Supports private conversations inside the platform and public-facing mirror experiences

See the full deep dive at Muse Deep Dive.

AI Console ​

The AI Console is the operator view for working with Muse and the specialist agents directly.

  • Launch targeted prompts for specific domains like SEO, WordPress, analytics, and marketing
  • Monitor outputs and keep tenant-aware context attached to each run
  • Reuse the same knowledge and connection stack across agents

Agents ​

AIOHM includes a multi-agent layer for marketing, content, WordPress, analytics, automation, and technical operations.

  • Each agent can use tenant-aware tools and custom prompts
  • Agents can be enabled or disabled per tenant
  • Model choice, provider fallback, and behavior stay configurable in the admin panel

MCP Servers ​

Model Context Protocol servers expose structured tools to the AI layer.

  • WordPress, Mautic, SEO, analytics, and internal knowledge servers are supported
  • MCP tools let agents create posts, inspect data, and automate external systems safely
  • Server registration and tenant attachment stay under platform control

Knowledge Base ​

The knowledge base turns uploaded documents into reusable context for the AI system.

  • Stores tenant-specific documents, notes, and extracted content
  • Feeds private Muse conversations and other specialist workflows
  • Supports retrieval-based answers instead of starting from zero each session

Brand Book ​

The brand book captures voice, values, audience, visuals, and positioning in one place.

  • Keeps AI output aligned with each tenant's tone and identity
  • Supports brand voice, offers, personas, and visual guidelines
  • Acts as the grounding layer for Muse and other agents

WordPress ​

WordPress integration connects the platform to content operations.

  • Manage posts, pages, products, and media
  • Generate and refine content with AI assistance
  • Sync platform changes back to the connected WordPress site

Autoblog ​

Autoblog workflows turn feeds and source material into publishable content.

  • Pull fresh source items from configured feeds
  • Rewrite or expand them with AI assistance
  • Route approved output into WordPress publishing flows

Image Studio ​

Image Studio helps generate branded visual assets for posts, campaigns, and social content.

  • Build reusable visual templates
  • Generate image copy in-brand with AI assistance
  • Save outputs to tenant media storage for later reuse

RSS Feeds ​

RSS ingestion gives the platform a steady stream of source material for curation and automation.

  • Import feed items into AI-assisted workflows
  • Filter for the most useful or relevant entries
  • Hand off approved items into blog, email, or social flows

Media ​

Media tools cover both generated and uploaded assets.

  • Image gallery for generated creative assets
  • Document gallery for source material and tenant files
  • Reusable files for AI context, publishing, and operations

Mirror Mode ​

Mirror Mode is the public-facing AI experience for your audience.

  • Answers from public knowledge, not private internal content
  • Lets visitors interact with a brand-aligned assistant
  • Keeps a clear boundary between internal Muse work and public support

Social Scheduler ​

Social scheduling keeps connected channels active from one platform surface.

  • Draft, queue, and review posts across multiple platforms
  • Connect scheduling engines like Postiz
  • Support multi-account publishing for multi-brand teams

Workflow Builder ​

The workflow builder connects AI, content, and integrations into repeatable automation.

  • Design sequences with nodes and conditional logic
  • Combine MCP tools, AI steps, and publishing actions
  • Reuse flows across campaigns and operational routines

Scheduling ​

Scheduling lets operators decide when flows should run.

  • Time-based execution for recurring jobs
  • Campaign-friendly planning across content and channels
  • Less manual monitoring once the flow is stable

AI Settings ​

AI settings control providers, fallback behavior, and model preferences.

  • Choose primary and fallback providers
  • Tune behavior for creativity versus reliability
  • Keep provider credentials and defaults isolated per tenant

Connections ​

Connections centralize external service setup.

  • OAuth and API-driven integrations live in one place
  • Brand-level credentials stay separated from other tenants
  • Connected services become available to agents and workflows

Credentials ​

Credential handling is built around environment variables, tenant settings, and protected admin surfaces.

  • Production secrets should stay outside Git
  • Tenant integration credentials are stored with the appropriate isolation boundaries
  • Release packages exclude local-only secret files and generated runtime state

Security ​

Security spans tenant isolation, secret handling, and production validation.

  • Multi-tenant database and file boundaries protect brand data
  • GitHub validation blocks dev-only files and secret-like leaks from main
  • Production deploys preserve runtime storage while shipping clean release packages

Users ​

User management covers team access, roles, and tenant membership.

  • Admins can control who can operate inside a tenant
  • Platform-wide administration is restricted to the configured super-admin context
  • Access patterns are designed around tenant isolation first

Tutorials ​

The platform includes onboarding help and explainers for first-time users.

  • Guided setup flows help new tenants understand the core surfaces
  • Documentation now resolves to stable production URLs under /docs
  • Tutorial material can be expanded without changing the main product flow