elmo
  • Pricing
  • Changelog
  • Roadmap
  • Vision
  • Docs
575Sign up
IntroductionQuick Start
Edit this page·View as Markdown·Report an issue·Join our Discord

Get product updates

New features and releases from Elmo, straight to your inbox.

Product

  • Features
  • Pricing
  • Off-Site AEO
  • Changelog
  • Roadmap

Resources

  • Blog
  • Documentation
  • Support
  • API Reference
  • Elmo Cloud Status
  • Provider Status
  • Issues

Learn

  • What is AEO?
  • What is GEO?
  • AEO Glossary
  • AI Search Guides
  • AI Search Statistics
  • AEO by Industry

Tools

  • Tool Directory
  • Free & Open-Source Tools
  • Compare Tools

Company

  • About
  • Vision
  • Brand Assets
  • Merch
  • llms.txt

© 2026 Blue Whale Software, LLC

TermsPrivacyCookiesSubprocessorsAcceptable Use
v0.7.8Open source on GitHub
Twitter / XLinkedInDiscordGitHub
elmo

Quick Start

Get Elmo running on your infrastructure in under 5 minutes using the CLI.

Prerequisites

  • Docker — Docker Engine 24+ with Docker Compose v2
  • Node.js — 18.x or later (for the CLI)
  • At least one AI provider API key (OpenAI, Anthropic, or OpenRouter)
  • A TypeSafe API key for Jev, which judges which answers mention your brand and their sentiment, or an OpenRouter key to call Jev through OpenRouter. Very roughly $0.15–0.35 per 1,000 answers, about $2–4 a month for 25 daily prompts on 3 platforms (pricing by volume)
  • (Recommended) A scraping provider to track the real ChatGPT and Google AI Mode experiences — see Providers

Install the CLI

npm install -g @elmohq/cli

Initialize Your Instance

Run the interactive setup wizard:

elmo init

The wizard walks you through:

  1. Config directory — Where to store your elmo.yaml and .env files (default: ./elmo)
  2. PostgreSQL — Run Postgres in Docker (recommended) or provide an existing DATABASE_URL
  3. AI Providers — Configure scrapers (Cloro, BrightData, Oxylabs, SearchApi, Olostep, DataForSEO) and/or direct model APIs (OpenAI, Anthropic, Mistral, OpenRouter); see Providers for details
  4. Access — Use Elmo on this machine (localhost), or from a domain behind a reverse proxy (see Serving Elmo from a Domain)
  5. Start — Optionally start the stack immediately

Once complete, Elmo generates two files in your config directory:

FilePurpose
elmo.yamlDocker Compose configuration for all services
.envEnvironment variables, secrets, and API keys

Start Elmo

If you didn't start during init, bring everything up with:

elmo compose up -d

This pulls the Docker images and starts all services. Once they report healthy, open http://localhost:1515 in your browser.

System Architecture

Elmo system architecture: User connects to Web; Web and Worker share a Postgres database; Web calls LLM APIs; Worker calls both LLM APIs and an LLM Scraper.
ServiceRole
WebDashboard UI and REST API
WorkerBackground scheduler that drives prompt runs
PostgresShared database and job queue
LLM APIsDirect API calls (OpenAI, Anthropic, OpenRouter)
LLM ScraperScrapers for ChatGPT, Google AI Mode, and other live AI surfaces (Cloro, BrightData, Oxylabs, SearchApi, Olostep, DataForSEO)
Elmo CLIGenerates elmo.yaml + .env and runs docker compose

CLI Commands Reference

Once Elmo is running, these commands help you manage it:

# View live logs
elmo compose logs -f

# View logs for a specific service
elmo compose logs -f web

# Check service status
elmo compose ps

# Stop all services
elmo compose down

What's Next

With Elmo running, head to the User Guide to create your first brand, configure prompts, and start tracking AI visibility.

Was this page helpful?

On this page

PrerequisitesInstall the CLIInitialize Your InstanceStart ElmoSystem ArchitectureCLI Commands ReferenceWhat's Next