LanguageTool Hosting

Check grammar, spelling, and style in more than twenty languages through a private API.

Order now No setup fees
  • One click deploy
  • 1 GB RAM Memory needed
  • 15 GB Disk Space Needed
  • From 2 € Price

Tech

Docker image
erikvl87/languagetool:latest
Default port
8010

How LanguageTool works

The LanguageTool container runs the project’s embedded HTTP server. A client sends text and language parameters to the checking endpoint and receives structured matches describing possible spelling, grammar, punctuation, or style issues. Browser extensions and other compatible tools can be pointed at a self-hosted server when they support a custom LanguageTool endpoint.

This package is an API service, not the LanguageTool cloud editor or a complete writing application. Upstream states that the basic self-hosted server does not include cloud-only AI rules. Its desktop application does not work through this approach, synonyms are unavailable through the local server, and client compatibility depends on how each extension or application implements custom-server support.

Key LanguageTool features

Language coverage and rule depth differ by language. Additional n-gram datasets can improve selected confusion checks, but upstream distributes them separately; they are large, require configuration and fast storage, and are available only for certain languages. The catalogue image does not mount those datasets or a custom fastText language-identification model.

The catalogue exposes the HTTP server through the application address but declares no login, API key, rate limiter, saved-document area, or persistent custom-dictionary volume. Users should not treat the endpoint as a confidential multi-tenant writing service without reviewing access controls, input sensitivity, request logging, abuse limits, and client-side transmission behaviour.

LanguageTool vs Grammarly

LanguageTool’s hosted package provides a self-hosted checking API with the project’s basic rules. Grammarly is a provider-managed AI writing platform with proofreading, paragraph rewrites, tone suggestions, browser and desktop integrations, mobile clients, plagiarism or AI-related tools, and products for organisations.

Grammarly may fit users who want a polished account experience, extensive clients, generative assistance, and managed team functions. The self-hosted LanguageTool server is better suited to technical integrations that need a controlled endpoint and accept the narrower rule set. Premium, cloud AI, plagiarism checks, paraphrasing, and Grammarly-style account features are not part of this package.

Who uses LanguageTool

Developers connect LanguageTool to editors, form workflows, publishing tools, support systems, or internal applications. Schools and organisations can use one endpoint for supported clients when they are comfortable operating access policy and reviewing the rule quality for each language.

LanguageTool suggestions are not authoritative proofreading, legal review, translation, accessibility validation, plagiarism detection, or a guarantee that text is correct. Writers should evaluate every suggestion in context, especially for names, technical vocabulary, regulated content, and languages with fewer rules.

Self-hosting LanguageTool: requirements and cost

LanguageTool workload depends on text length, request rate, selected language, enabled rules, simultaneous clients, and any optional language models. PostgreSQL and MariaDB are Not required, and the catalogue provides no persistent document store. The application has no separate software fee; sustained API traffic or large separately configured models can require more memory and processing.

On AvaHost, LanguageTool uses Plan 1 at €2. The hosted LanguageTool package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The package exposes the basic embedded HTTP service. It does not include cloud-only AI rules, Premium functions, n-gram datasets, fastText configuration, a writing editor, desktop application, plagiarism checking, account management, API keys, rate limiting, or saved documents.

F.A.Q

  • LanguageTool starts at €2 on Plan 1. That starting point is suitable for light internal checking. Request rate, text length, simultaneous clients, chosen languages, active rules, and any separately installed language models determine when more memory or processing capacity is appropriate. No per-request application fee is added by AvaHost.

  • A custom domain can be assigned to the hosted LanguageTool server, with automated HTTPS applied after DNS points to the application. Configure each compatible client to use the final endpoint and send checks with the supported API format. The package does not create API keys, user accounts, or per-client permissions.

  • The hosted image provides the basic embedded LanguageTool HTTP server. Upstream states that cloud-only AI rules are not included in this self-hosted approach. Premium checks, generative rewrites, plagiarism detection, a managed editor, account subscriptions, synonyms, and separately downloaded n-gram datasets should not be assumed to be present.

  • AvaHost applies application updates automatically and schedules backups for the hosted installation. Because the catalogue has no document store, clients should retain their source text independently. After a major release, test representative languages, custom client connections, rule changes, response formats, request limits, and any optional server configuration before using results in a production workflow.