Practical overview
When it fits
Use Llmaker when building a self-hosted AI application requires coordinating a model with Docker-based retrieval and supporting services, or when you want terminal-based management of those components as one fleet.
Who it is for
- Developers assembling local retrieval-augmented chatbots or document Q&A systems.
- Teams that want to manage self-hosted models and their supporting services together.
- Builders creating FAQ assistants or recommendation engines on local infrastructure.
Documented uses
- Provision a model together with vector search, embeddings, caching or observability services.
- Scaffold or apply a declarative stack configuration.
- Ingest documents and query an agent for grounded answers with sources.
- Inspect service status, logs and resource use across a managed fleet.
- Run a local model with an OpenAI-compatible endpoint.
Requirements & limits
The README requires Docker and lists Linux and macOS for prebuilt binaries. It also documents installation through Go or from source. The project is labeled alpha.
- Docker is a required dependency.
- The agent image must be built locally for stacks that include the agent; the assistant template is documented as not needing it.
- The README identifies the project as alpha.
- The CLI is written in Go; the agent uses Python and FastAPI, with LangGraph among its documented components.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Provision and query a document Q&A stack
Set up a retrieval-augmented stack and submit a document and question to its agent.
Before you start
- Docker
- Llmaker installed
- A locally buildable agent image for stacks that include the agent
- A document to ingest
Steps
Run
llmaker stack init ragto generate a stack configuration, or use the documentedragtemplate.Build the agent image with the command below.
make image-agentApply the configuration with
llmaker apply -f stack.yamland inspect the provisioned services withllmaker ls.Resolve the agent URL from
llmaker service ls --json, then submit the document to/api/ingestand a question to/api/chat.
Expected outcome
A provisioned retrieval stack whose agent accepts document ingestion and returns answers with sources.
Guide limitations
- The agent image must be built locally for stacks that include the agent.
- The README describes setup and request examples; this guide does not represent an independent execution test.
Compare options for Vector search
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Llmaker | Provision a model together with vector search, embeddings, caching or observability services. | CLI, Docker, Self-hosted | The README requires Docker and lists Linux and macOS for prebuilt binaries. It also documents installation through Go or from source. The project is labeled alpha. |
| Weaviate — weaviate | Store application objects alongside vectors and retrieve similar items. | Cloud, Self-hosted, Server | The repository describes Weaviate as open source and lists Docker, Kubernetes and Weaviate Cloud deployment options. |
| Qdrant Multi Node Cluster | Deploy Qdrant across multiple nodes using Docker Compose. | Docker, Self-hosted, Server | The repository is public and specifies an MIT license. The documented deployment requires Docker, Docker Compose, Python 3.8+, and Git. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- raiyanyahya/llmaker · Official homepage title · retained in its source language

