Skip to main content
PatentSchmiede
Request a conversation
Menu

Firm IT

The installation in your firm.

This page is for your firm's IT support. It describes the shape of the installation and the tasks that stay on site.

The shape in one sentence.

PatentSchmiede runs as a Docker Compose stack on a Linux host inside your firm's network. Caddy publishes the host ports. The backend, frontend, and Neo4j sit on the internal Docker network and are not directly reachable.

The topology.

The browser reaches Caddy, and Caddy routes requests to the frontend and the backend. The backend talks to Neo4j. Ollama is an optional service for the local model path.

BrowserCaddyFrontendBackendNeo4jOllamaoptional
Requests and data move through the internal network, with Caddy as the entry point. Ollama is an optional service.

Hardware sizing.

Two profiles, because the local model path drives the requirements.

Hardware sizing.
ProfileCPURAMDiskGPU
Cloud LLM (Azure — standard)4 cores16 GB100 GB SSD—
Air gap (local LLM via Ollama)8 cores32 GB250 GB SSDrecommended, ≥ 12 GB VRAM

measured as of 2026-08-09

TLS: two modes.

Caddy supports two modes. The selected Caddy file determines the mode.

Internal CA on the LAN

Caddy issues the certificate from its own certificate authority, and the installation needs neither internet access nor public DNS. The root certificate is installed on the workstations during setup, and HSTS is deliberately off in this mode.

ACME for a public name

Caddy obtains the certificate over ACME from a publicly trusted authority. This needs internet access and public DNS, and HSTS is on in this mode.

Backup, restore, upgrade.

  • The backup contains an offline dump of the Neo4j database and an archive of the uploads volume.
  • The restore checks the checksums against the manifest before it writes, and afterwards prints the node counts for comparison with the manifest.
  • The upgrade applies the new images and runs the versioned migrations.

The runbooks for backup, restore, and upgrade are delivered with the installation.

What your firm's IT provides.

  • Encrypted volumes under the Docker data root and at the backup target.
  • A Linux host with Docker Engine 20.10 or newer and Compose.
  • A person who installs the root certificate on the workstations.

Questions about the installation.

The setup follows a runbook. If you are planning the installation for your firm, write to us.

Questions about the installation