Self-Host
Open the app: Run it on your own server → (products.documentize.ai)
Summary
Self-host is the Documentize API and web UI running on your machine or server. Files are processed there and never leave your network. It is a standard ASP.NET Core application with no external services required, aimed at developers, internal tools and production use. Page: the Self-Host product page on products.documentize.ai.
Requirements
- .NET 9 runtime for direct execution, or Docker (20.10 or newer) for containers.
- About 2 GB of RAM recommended.
- Default port 80 (map another with Docker).
Install and run
Download the package from the self-host page, extract it, then:
dotnet Documentize.SelfHost.dll
and open http://localhost. With Docker, use the supplied Dockerfile:
docker build -t documentize .
docker run -p 80:80 documentize
The API is served under /webapi/ on the same address, so the REST flow works against http://localhost/webapi/.
Licensing and tiers
Without a license, the instance runs in trial mode: output may carry evaluation watermarks. The page lists the tiers:
| Free / no key | Paid subscription | |
|---|---|---|
| Operations per day | 5 | Unlimited |
| Max file size | 10 MB | Unlimited |
| Concurrent operations | 2 | 8 |
| Watermark and 4-page limit on PDFs | Applied | Removed |
Ways to unlock a paid tier:
- License file:
curl -X POST http://localhost/webapi/license -F "license=@documentize.lic"; check withGET /webapi/license. - Account activation (recommended): create a self-host activation key on the page (requires sign-in) and set
DOCUMENTIZE_API_TOKEN=dmk_...on the instance. It refreshes a short-lived signed entitlement about every 6 hours, so plan changes follow your account automatically. This is not the sidebar's "Copy API token". - Signed key: a
DMZ1....subscription key, set on the instance (see the page for the variable names).
The numbers are compiled into the binary; no environment variable can raise them.
What differs from the cloud
- Your data stays local; usage is metered by a local encrypted counter, not by the cloud.
- You update it, back it up and secure it yourself.
- The instance reports usage to Documentize (there are usage-report routes in the code), so it is not fully disconnected; confirm with the vendor if you need air-gapped operation (verify).
- Which apps are included in the self-host build may differ from the cloud list (verify).
Pointing clients at it
The desktop clients accept a provider profile (Kind: Documentize REST, Base URL http://localhost/webapi/, trailing slash kept).