Self-host the free tools in 3 commands
The seven free tools from locan.ai, running on your own server with Docker Compose: no daily limits, no database, no account.
This covers the free tools. The AI visibility tracker isn't packaged for self-hosting; it runs only at app.locan.ai.
git clone https://github.com/vaitko/locan-tools.git && cd locan-tools
cp .env.example .env # fill in GOOGLE_PLACES_API_KEY
docker compose up --build
The site is then on http://localhost:8080, with the API behind /api.
What you need
Docker, a Places key, and an LLM
- Docker and Docker Compose.
- A Google Places API (New) key, set as
GOOGLE_PLACES_API_KEY. -
An LLM: a Replicate token (
REPLICATE_API_TOKEN, the default), an OpenAI key (LLM_PROVIDER=openai+OPENAI_API_KEY, withLLM_MODELset to an OpenAI model such asgpt-4o-mini), or an OpenAI-compatible endpoint such as Ollama viaOPENAI_BASE_URL. Whatever you pick,LLM_MODELhas to be a model name that provider accepts.
Which tools need what
Not every tool calls Google or an LLM
| Tool | Needs Places key | Needs LLM |
|---|---|---|
| Google Business Profile Optimizer | Yes | Yes |
| GBP Category Optimizer | Yes | No |
| Local Rank Checker | Yes | No |
| AI Visibility Checker | No | Yes |
| AI Review Response Generator | No | Yes |
| LocalBusiness Schema Generator | No | No |
| Google Review Link & QR Poster | No | No |
What self-hosting removes
No quotas, no analytics, no email capture
The self-hosted build is the same code as locan.ai with SELF_HOSTED=true /
PUBLIC_SELF_HOSTED=true: the daily per-visitor quotas are gone, there is no analytics
or cookie consent, and there is no email capture. There is also no database and no auth; put it
behind your own reverse proxy if you expose it beyond localhost.