AI/Run CodeMie Standalone

CodeMie Standalone packages the frontend, backend API, and an nginx reverse proxy into a single Docker image, paired with a separate PostgreSQL container through Docker Compose. It is the fastest path to a running CodeMie instance, with no Elasticsearch, Keycloak, or LiteLLM dependency.

The image is published on Docker Hub as codemie/codemie-oss-standalone, so no source checkout or local build is required to try the platform.

When to Use

CodeMie Standalone is designed for:

• Proof of Concept (PoC) and demos — a single image and two containers are enough to explore the platform.
• Local development and testing — no external identity provider, search cluster, or LLM proxy is required to start the application.

Not for Production

CodeMie Standalone runs a single instance of every component with no high availability, scaling, or automated backups. For production workloads, use the Kubernetes or On VM deployment guides.

What's Included

Component	Delivery	Notes
Frontend + Backend + nginx	Single Docker image, published on Docker Hub as codemie/codemie-oss-standalone or built by build-image.sh	nginx proxies /api/, /v1/, /code-assistant-api/ to the backend and serves the frontend static assets
PostgreSQL	postgres:17 container	Primary application database
Authentication	Built-in local auth (IDP_PROVIDER=local)	Seeded with a superadmin account from .env.standalone; no Keycloak required
Retrieval (Elasticsearch)	Disabled by default (RETRIEVAL_BACKEND=none)	Knowledge Bases, Data Sources, and code indexing are unavailable unless a retrieval backend is configured — see Configuration
Budget Management (LiteLLM)	Not included	Disable features:budgetManagement — see Run Guide

Repository

The packaging assets (Dockerfile, build-image.sh, Compose file, nginx and entrypoint scripts) live under standalone/ in the codemie backend repository. The image bundles the frontend from the codemie-ui repository at build time — no separate frontend repository checkout is required to run the image, only to build it. Consumers of a published release use its version-matched standalone deployment files and the image from Docker Hub; they do not need either source checkout.

Next Steps

Proceed to the Run Guide to pull the image, configure the environment, and start the stack.