Joshua Opolko

Perplexica (Now Vane) Self-Hosted Guide (2026): Your Own Open-Source Perplexity

A glowing orb suspended in a dark library ringed by floating open books lit by teal beams and god-rays, representing Perplexica AI search grounded in cited sources

Perplexica is the most popular open-source, self-hostable alternative to Perplexity: an AI search engine that reads the live web and answers your questions with citations, images, and videos. In March 2026 the project was rebranded to Vane, so the GitHub repository and Docker image now carry the Vane name, but it is the same tool and most people still search for it as Perplexica. It is MIT-licensed and completely free, with no paid tiers or seat caps. The best part for privacy: it ships as a single Docker image that bundles the web front end, the API, and its own private SearXNG metasearch engine, so there is almost nothing to wire up. This guide covers the install, connecting a model (including a fully local one via Ollama), the connection errors people hit, and how it compares to Perplexity and Morphic.

Key takeaways

Install Perplexica (Vane) with Docker

Because the image bundles SearXNG, a single docker run is enough to get a working private Perplexity clone. Map the web port, give it a volume for persistent data, and open the setup wizard.

# Run Perplexica / Vane (bundles the UI, API, and a private SearxNG)
docker run -d \
  --name perplexica \
  -p 3000:3000 \
  -v perplexica-data:/home/vane/data \
  itzcrazykns1337/vane:latest

# Open the app and complete the setup wizard
# http://localhost:3000

On first visit the setup wizard asks for a model provider. Pick one, paste your API key (or point it at a local model), confirm, and you are searching. SearXNG runs inside the same container on its own internal port, so there is nothing extra to configure for web search itself.

Connect a model (hosted or local)

Perplexica is model-agnostic and needs two kinds of model: a chat model to write the answer, and optionally an embedding model to rerank search results. In the wizard or the settings menu, choose from OpenAI, Anthropic, Gemini, Groq, or a local backend such as Ollama, LM Studio, or local Transformers. Running the chat and embedding models locally through Ollama gives you a fully private answer engine where neither your queries nor your keys leave your machine.

1. Perplexica cannot connect to Ollama

What you see: a 500 error from Ollama, a message like "llama runner process no longer running," or the model simply never responds even though Ollama works fine in your terminal.

What it is: the most common Perplexica issue, and it is almost always Docker networking. From inside the Perplexica container, localhost means the container itself, not your host where Ollama runs. Ollama also binds to localhost by default and will refuse connections from another origin.

The fix: two changes. First, make Ollama listen on all interfaces by setting OLLAMA_HOST=0.0.0.0:11434 in its service and restarting it. Second, in Perplexica's settings set the Ollama API URL to your host's real address, not localhost: use http://host.docker.internal:11434 on Docker Desktop, or your machine's LAN IP (for example http://192.168.1.50:11434) on Linux. Verify the URL is reachable from inside the container before blaming the model.

# On the Ollama host: listen on all interfaces
sudo systemctl edit ollama
#   [Service]
#   Environment="OLLAMA_HOST=0.0.0.0:11434"
sudo systemctl restart ollama

# In Perplexica settings, set the Ollama API URL to one of:
#   http://host.docker.internal:11434   (Docker Desktop)
#   http://YOUR_HOST_LAN_IP:11434        (Linux)

2. Web search returns nothing

What you see: the model answers from its own knowledge but no live sources or citations appear.

What it is: the bundled SearXNG is not reachable, or an outbound network restriction is blocking it.

The fix: since SearXNG is bundled in the same container in the current Vane image, confirm the container is healthy and has outbound internet access. If you are on a locked-down network or behind a corporate proxy, allow the container's egress. Check the container logs for SearXNG errors rather than assuming the LLM is at fault.

3. Answers are slow or low quality

What you see: responses take a long time, or the synthesis is thin compared to Perplexity.

What it is: answer quality and speed track the model you chose and the mode you are in. A small local model on Speed mode will be fast and shallow; a strong hosted model on Quality mode is slower and deeper.

The fix: match mode to need. Use Speed for quick lookups, Balanced for everyday use, and Quality when depth matters. If local answers feel weak, step up to a larger local model (mind your VRAM, see the Ollama guide) or use a hosted model for the chat step while keeping search local.

Optimization modes and focus modes

Perplexica gives you two dials that decide the speed, cost, and shape of every answer. The optimization mode trades latency against depth: Speed does a quick single pass for fast lookups, Balanced is the sensible default, and Quality does more retrieval and reasoning for harder questions at higher latency and token cost. The focus mode narrows where it searches, with options such as a general web search, an academic mode that favors papers and scholarly sources, a writing-assistant mode that skips web search entirely, and dedicated modes for video and discussion sources. The practical habit: leave it on Balanced web search for everyday questions, switch to Quality plus academic focus for research, and use the writing mode when you just want the model without live search.

Keep it updated and persistent

Because Perplexica ships as a single image, updating is a pull-and-recreate, and your settings survive as long as the data volume does. Pull the new image, stop and remove the old container, and start a fresh one against the same named volume so your provider keys and history carry over.

# Update to the latest image without losing your data
docker pull itzcrazykns1337/vane:latest
docker stop perplexica && docker rm perplexica
docker run -d --name perplexica -p 3000:3000 \
  -v perplexica-data:/home/vane/data \
  itzcrazykns1337/vane:latest

The named volume (perplexica-data) is what makes this safe: your configuration lives there, not in the container, so recreating the container is routine rather than risky.

Expose Perplexica on your network

By default the app answers on localhost:3000, which is fine on your own machine but not for a household or team instance. To reach it from other devices, put a reverse proxy (Caddy or Nginx) in front, terminate TLS with a real certificate, and forward to port 3000. Caddy makes this a two-line config with automatic HTTPS. Do not expose port 3000 directly to the public internet without auth in front of it, since anyone who reaches it can spend your model credits; keep it on your LAN, behind a VPN, or behind proxy authentication.

What to use a self-hosted answer engine for

Once it is running, Perplexica earns its keep as a private research tool. It is genuinely useful for literature and source gathering where you want citations you can click through rather than an unsourced summary, for searches you would rather not send to a commercial engine tied to your identity, and for offline-leaning setups where a local model answers from live web results without any data leaving your control. Paired with a capable local model through Ollama, it becomes an answer engine whose queries, keys, and history are entirely yours, which is the whole reason to self-host instead of using the hosted original.

Perplexica vs Perplexity vs Morphic (2026)

If you want web answers with citations, these are the three names that come up. The trade is convenience versus control and privacy.

ToolHostingCostPrivacyNotes
Perplexica / VaneSelf-hosted, one Docker imageFree (MIT), pay only your own modelHigh; bundled SearXNG, local models possibleClosest open-source Perplexity clone; bring your own key
PerplexityHosted SaaSFree tier and paid ProLower; your queries go to their serviceMost polished, zero setup, not private or self-hostable
MorphicSelf-hostable or hostedFree / open sourceMedium to highGenerative-UI answer engine; local mode leans on OpenAI-style APIs

Choose Perplexica/Vane when you want a private, free answer engine you control and can point at local models. Choose Perplexity when you want the most polished hosted experience and do not need privacy or self-hosting.

Frequently asked questions

Is Perplexica the same as Vane?

Yes. Perplexica was rebranded to Vane in March 2026. The GitHub repository and Docker image (itzcrazykns1337/vane:latest) now use the Vane name, but it is the same open-source AI search engine. Most people still search for it as Perplexica.

Is Perplexica free?

Yes. Perplexica (Vane) is MIT-licensed and free, with no paid tiers, license keys, or seat caps. Your only cost is whatever model you connect, and that is zero if you run a local model through Ollama.

Why can't Perplexica connect to Ollama?

Almost always Docker networking. Inside the container, localhost is the container, not your host. Set OLLAMA_HOST=0.0.0.0:11434 on the Ollama side, then in Perplexica's settings use http://host.docker.internal:11434 (Docker Desktop) or your host's LAN IP (Linux) as the Ollama API URL.

Does Perplexica need a separate SearXNG?

No longer. The current Vane image bundles a private SearXNG inside the same container, so web search works out of the box with nothing extra to deploy. You only need to supply a model provider.

Perplexica vs Perplexity: what is the difference?

Perplexica is self-hosted, free, and private; you run it and bring your own model, including local ones. Perplexity is a polished hosted service with zero setup but no self-hosting and less privacy. Choose Perplexica for control and privacy, Perplexity for convenience.


Resources

Last updated: June 13, 2026.

Josh writes about AI agents, local AI, and GEO, and runs nowservingto.com, a daily-fresh directory of Toronto's newest restaurants.