Fully Managed AnythingLLM
as a Service

Deploy AnythingLLM as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

AnythingLLM is an open-source private AI application, workspaces, retrieval over your own files and in-workspace agents, combining the convenience of a hosted assistant with the control of software that runs on infrastructure you chose.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

AnythingLLM

AnythingLLM

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
AnythingLLM Preview Image

ABOUT THE SOFTWARE

What is AnythingLLM

AnythingLLM is an open-source private AI application built by Mintplex Labs. It gives a team workspaces, retrieval over their own documents and in-workspace agents, running against whichever model provider they choose, hosted or local.

The project ships under the MIT licence, which puts no restriction on running it as a hosted service and no obligation on what you build around it. The codebase is a monorepo: a React front end, a NodeJS server that manages model and vector-store connections, a separate collector process that parses documents, an embeddable chat widget and a browser extension. The container build bundles the front end, server, collector and the default vector store into one running unit.

Two things about the default install matter more than anything else on the page. The vector store is LanceDB, embedded on the instance, so document text and vectors stay where the application runs. The embedder is the built-in native model, which runs on CPU, was trained on English, and wants roughly 2 GB of free memory. Against an external model provider the documented baseline for the container is about 2 GB of RAM, two CPU cores and 5 GB of storage, with 10 GB recommended. Multi-user roles exist on the container build only; the desktop application is single-user.

FEATURES

What AnythingLLM does

AnythingLLM sits between your documents and whichever model you connect. It parses and embeds files, groups them into workspaces, answers with citations back to the source, and can run agents and external tools inside the same conversation.

Workspaces

Documents are grouped into isolated workspaces, each with its own document set, system prompt, chat history and optional model override. A file pinned to one workspace is not visible from another.

Document parsing

The collector process handles PDF, DOCX, XLSX, PPTX, CSV, Markdown, HTML, more than fifty code file types and audio through speech-to-text, turning each into chunked text ready for embedding.

Retrieval with citations

At query time the closest matching chunks are pulled from the vector store and placed in the prompt, and the answer carries links back to the source documents the chunks came from.

Agents

Agents invoked inside a workspace can browse the web, run code, read files and query SQL, and a no-code flow builder chains those steps into a repeatable sequence without writing an integration.

MCP tool servers

External tool servers are loaded from a configuration file over stdio or HTTP transports. Tools are supported; the resource, prompt and sampling parts of the protocol are not implemented.

Multi-user roles

Three roles exist on the container build. Admin holds system settings, Manager handles workspaces and users without touching model configuration, and Default can only chat in assigned workspaces.

Developer API

A REST API covers workspace, document and chat operations, so an instance can be driven from a script, a scheduled job or another application rather than only through the browser interface.

Embeddable chat widget

Any workspace can be exposed as a chat bubble on a website through a script tag, with per-embed and per-session message limits and an origin allowlist controlling who can load it.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to AnythingLLM the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed AnythingLLM

Per-seat AI pricing is what usually starts the conversation. Microsoft reset list prices across its business plans and folded a baseline chat assistant into the suites while keeping the fuller assistant as a separate per-seat add-on. Teams then look at what a private instance costs instead.

Running AnythingLLM yourself is not hard to start and is easy to get wrong in a way you only discover later. The application is one container, but a working deployment is a container plus a persistent storage volume with the right ownership, a proxy that upgrades websocket connections, TLS renewal, and a backup that captures the database, the vector store and the source documents as one consistent set. Miss the volume ownership and the database comes up read-only on first boot. Miss the websocket headers and every agent session returns a proxy error while ordinary chat looks fine.

The failure mode that costs the most time is quieter than either of those. The embedding model is a system-wide setting, not a per-workspace one. Change it after you have ingested documents and retrieval degrades or breaks outright, because the stored vectors and the query vectors no longer come from the same model. There is no automatic migration, so the fix is to delete and re-embed everything. The same is true of moving off the default vector store. Teams find this out after loading several thousand documents, which is exactly the wrong moment.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run AnythingLLM on DANIAN

The shape of an AnythingLLM deployment follows the corpus, not the headcount. These three patterns cover most of what teams bring to us: client work split by engagement, internal operational knowledge, and a research corpus that must stay on one instance.

12-PERSON CONSULTING FIRM

One workspace per client engagement

Proposals, deliverables and interview notes are loaded into a workspace per engagement, so a question about one client cannot retrieve another client's material. The instance runs in the region closest to the client base and connects to a hosted model provider the firm already contracts with.

40-SEAT SUPPORT AND IT TEAM

Runbooks and ticket history behind one assistant

Runbooks, wiki exports and resolved-ticket text feed a single workspace. The three-role model gives first-line staff chat access only, while the widget is embedded on the internal portal with an origin allowlist so it answers there and nowhere else.

9-PERSON RESEARCH GROUP

Papers and protocols against a self-hosted model

The group loads papers and protocol documents, keeps the on-instance vector store, and points the model connection at their own inference endpoint rather than a public API, so no document text leaves the instance at query time. One workspace per project.

COMPARISON

Four ways to run AnythingLLM

Four paths lead to a private assistant over your own documents. Three of them scale with headcount or with your own time. The comparison below holds the workload constant and changes only who runs the software and what it costs at one, five and ten users.

Path1 user5 users10 usersWhat you still own
Proprietary SaaS: ChatGPT Business$40/mo$100/mo$200/moNothing to run, and nothing to decide. Two-seat minimum, per-seat billing, monthly rates higher than annual, and agent usage capped per user per month.
Self-host on a VPS$24/mo$24/mo$24/moThe whole stack. A production-class VPS at roughly $24/mo plus your model spend, plus patching, TLS renewal, proxy configuration, backup verification and the embedder decision.
Home server~$900 once~$900 once~$900 onceHardware and power. An HP ProLiant ML30 Gen10 class tower plus electricity, your own uplink, your own redundancy, and no off-site copy unless you build one.
DANIAN managed AnythingLLM€9/mo€9/mo€9/moThe documents and the model choice. Flat price regardless of how many people use the instance, with updates, backups, monitoring, TLS and support included.

Seat prices reflect published list rates for the proprietary path and exclude what you pay your model provider on any of the four. On the managed path the €9 does not change with user count, because it is priced per app rather than per person.

BY INDUSTRY

AnythingLLM for specific industries

Three sectors put unusual demands on a document assistant, because the underlying records carry a retention duty and a control requirement. In each case the configuration decision is made before ingestion, since the embedder and vector store cannot be changed later without re-embedding.

The ABA Model Rules for Client Trust Account Records require trust and financial records to be kept for five years after the representation ends, and New York and Illinois extend that to seven. That retention duty sits on the underlying documents, so an assistant reading them has to leave the originals intact and traceable. We configure one workspace per matter, which keeps a question asked about one client from retrieving another client's file, and we keep the vector store on the instance so document text is not copied into a third-party index. A paralegal loads pleadings and the executed agreement into the matter workspace, an associate asks what notice periods the contract sets, and the answer cites the paragraph it came from. A mid-sized practice group typically holds tens of thousands of matter documents.


ISO 9001:2015 clause 7.5.3 governs controlled documented information: it must be stored and retrievable, protected from unintended alteration, and given a retention and disposition rule that the organisation sets rather than the standard. Work instructions and test records are exactly the corpus engineers want to question. We set a larger chunk size and a longer overlap for these deployments, because specification tables and tolerance clauses lose meaning when split mid-row, and that choice is fixed before ingestion. An engineer asks which torque figure changed between two revisions of an assembly instruction, and gets the answer with the revision it came from. A single plant quality system commonly holds several thousand controlled documents plus test records.


21 CFR 312.62 requires investigator records to be retained for two years after a marketing application is approved for the indication, or two years after the investigation is discontinued and the regulator is notified. Study documents therefore outlive the study, and they cannot be sent to a public model endpoint. We run these instances against a self-hosted inference endpoint with the on-instance vector store, so no protocol text leaves the machine at query time, and we set one workspace per study. A coordinator asks what the inclusion criteria and dosing schedule are, and the answer points at the protocol section. A single trial's essential-document set runs to hundreds or thousands of pages.


FAQ

Frequently asked questions

Three groups of questions. The first covers how AnythingLLM is configured on our platform, the second covers getting your existing setup and documents onto it, and the third covers billing, support and the platform rules that apply to every app we run.

01

Technical and configuration

Thirty or more, including OpenAI, Anthropic, Azure OpenAI, Amazon Bedrock, Google Gemini, Mistral, Groq, Cohere, OpenRouter and DeepSeek, plus self-hosted endpoints such as Ollama, LM Studio and LocalAI. You supply the key or the endpoint and we wire it in.
Not for the application itself. The server, collector and the built-in embedder all run on CPU. A GPU only matters if you want the language model running on the same machine, which most of our AnythingLLM customers do not; they point at a provider instead.
The parsed text and the vectors stay on the instance in the on-instance vector store. What travels is the chunk of text sent as prompt context to whichever model provider you enabled. Point the instance at a self-hosted model and nothing leaves at query time.
We run the embedded on-instance store by default, because it keeps vectors on the machine and removes a network dependency from the query path. For very large corpora we will set up an external store such Qdrant instead, agreed before you start ingesting.
You can, but the setting is system-wide and there is no migration. Every stored vector was produced by the old model, so retrieval breaks until everything is re-embedded. We pin the embedder at provisioning and note it on the instance record so it is a deliberate change, not an accident.
We disable it in the environment rather than in the settings screen. The in-app toggle does not survive a container rebuild, so an instance that was switched off by hand quietly starts reporting again after the next update. Setting it at the environment level makes it stick.
The REST API is available and the interactive schema browser is switched off, since there is no reason to publish it next to your instance. API keys carry full access with no narrower scope, so we treat them as administrator passwords and recommend rotating them on staff changes.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Parsing and embedding is CPU work, so it scales with page count and file type. Clean text moves quickly; scanned files need character recognition first and are slower by a wide margin. We size the instance for the initial load, not just for the steady state.
Yes. Send us the domain and we handle the records, the certificate and the renewal. You can also run on a subdomain we provide while your own DNS is being sorted, then switch later without rebuilding the instance.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed AnythingLLM for 7 days

No card. Cancel from the dashboard.