Verba hosting

A ready-made RAG interface built on Weaviate.

Agents & RAGBSD-3-Clauseupstream discontinuedfrom $11.99/mo
In short

Verba hosting at AIHostBox means a dedicated, single-tenant Verba instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and patch everything around it. Plans start at $11.99 per month and the admin account, the data and any API keys are yours.

No longer maintained upstream

Weaviate archived the Verba repository on 8 June 2026. There will be no new features and no upstream bug or security fixes.

We still host it for teams who depend on it: we keep the instance running, backed up and behind TLS, and patch the operating system and the services around it. We cannot fix bugs or vulnerabilities inside Verba itself, and there will be no feature updates. Order it only if you accept that; if you are starting fresh, the alternatives below are the safer choice.

Weaviate-nativeConfigurable chunkingSource displayImport UI

Verba, nicknamed the Golden RAGtriever, is the retrieval-augmented chat application written by the Weaviate team as a reference for building on their database. Its interface covers the whole pipeline: readers for PDF, DOCX, CSV and spreadsheets, GitHub and GitLab repositories, chunkers from token and sentence to semantic, Markdown, code and JSON, a choice of embedders, and a chat view that shows which chunks an answer came from. Retrieval uses Weaviate’s hybrid search, so keyword and vector matches are combined without extra setup.

Every stage is switchable from the browser, which makes it useful for comparing retrieval settings without writing code. Upstream archived the repository in June 2026, so Verba is now a finished reference application rather than a moving project. Hosting it next to a persistent Weaviate means your imported corpus and chosen configuration survive restarts and can be reached by anyone you give the address to. That is often all a proof of concept needs before a team commits to a heavier platform.

Verba hosting plans

PlusRecommended minimum
4 GB RAM · 2 vCPU · NVMe
$11.99/mo
Order
ProTeams & heavier load
8 GB RAM · 3 vCPU · NVMe
$18.99/mo
Order

Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.

How we run Verba

Two containers from the official compose file: the Verba FastAPI and Next.js app on port 8000, and a Weaviate database with its data on a persistent volume.

What we configure for you

  • WEAVIATE_URL_VERBA pointing at the private Weaviate container
  • OPENAI_API_KEY, COHERE_API_KEY, ANTHROPIC_API_KEY or GROQ_API_KEY as you choose
  • OLLAMA_URL, OLLAMA_MODEL and OLLAMA_EMBED_MODEL for a local model plan
  • GITHUB_TOKEN or GITLAB_TOKEN for private repository imports
  • UNSTRUCTURED_API_KEY or FIRECRAWL_API_KEY if you use those readers

Which plan fits

Plus (4 GB) runs Verba and Weaviate for a corpus of a few thousand documents embedded through an API. Pro (8 GB) is the choice for larger imports, the SentenceTransformers embedder running locally, or several people querying at once.

The honest limits

Verba is archived upstream and has no authentication of its own. Local SentenceTransformers embedding on CPU is slow for large imports; an embedding API is faster.

What people run Verba for

Evaluate retrieval settings

Change chunking and embeddings and see the effect immediately.

Demo a RAG stack

A presentable interface without building one.

Code and repository Q&A

Import a GitHub or GitLab repository and ask questions about it with the source files shown.

Licence and version policy

ItemPosition
Upstream licenceBSD-3-Clause
Sold as managed hostingYes
TenancySingle tenant — one customer per instance
PatchingCritical advisories within 24 hours, high severity within 72

Our full position on licences, including the applications we decline to sell, is on the licensing page.

Works well with Verba

More Agents & RAG we host

Questions

Verba hosting: your questions

Is Verba still maintained?
The Weaviate team archived the GitHub repository in June 2026 and no longer reviews issues or pull requests. The code still runs as it is, and we keep the container and Weaviate patched, but you should not expect new features. For an actively developed alternative, look at AnythingLLM or RAGFlow.
Which models and embedders can Verba use?
Generation through OpenAI, Anthropic, Cohere, Groq, Novita, Upstage or Ollama; embeddings through Weaviate, OpenAI, Cohere, VoyageAI, Upstage, Ollama or SentenceTransformers. Keys go in as environment variables such as OPENAI_API_KEY or COHERE_API_KEY, or point OLLAMA_URL at an Ollama plan.
Where are my documents stored?
Chunks, vectors and Verba’s saved configuration are stored in the Weaviate instance deployed alongside it, on a persistent volume. Backing up that Weaviate data directory captures the whole corpus, and it is included in the nightly off-box backup.
Does Verba have user accounts?
No. Verba has no login or user management of its own, so everyone who can reach the interface sees the same documents and settings. It suits a single user, an internal team or a demo, not a multi-tenant knowledge base.
Can I connect Verba to an existing Weaviate?
Yes. Verba’s custom deployment mode takes a Weaviate URL and API key through WEAVIATE_URL_VERBA and WEAVIATE_API_KEY_VERBA, so it can read from a Weaviate plan you already run with us instead of the bundled one.

Run Verba without running a server

A dedicated Verba instance, deployed and maintained by us. Month to month, cancel whenever.