Enterprise · On-Prem

FontScanner on your infrastructure

We can install FontScanner on your network. You provide a web UI, a database, and an API environment. We bring Docker Compose and work with your team.

Enterprise solutionsWhat we need from you

Architecture

Three environments. Docker Compose.

You host the web UI, the API, and the database. We publish FontScanner onto them.

Your network

How people use it

Website scans

Intranet, staging, and public sites from your network.

PDF scans

Upload a document and extract embedded fonts.

Scheduled scans

Daily, weekly, or monthly website crawls from the dashboard.

CI/CD

The same website and PDF jobs from your pipeline, if you want them.

We publish with Docker Compose

Three environments you provide

1 · Web UI

Dashboard

Website and PDF scans, reports. Published on your web environment.

2 · Backend API

Scanner & CI/CD

Crawls internal and public sites, reads PDFs, serves pipeline jobs. Published on your API environment.

3 · Database

PostgreSQL or SQL Server

Users, scans, and reports stay here. You host it; we connect the API.

Dashboard

Paste a website URL or upload a PDF. See history and reports in the same place.

Internal and public sites

Intranet, staging, and public websites. The crawler runs on your network.

Scheduled scans

Daily, weekly, or monthly website crawls from the dashboard — same as in our cloud.

CI/CD

The same website and PDF scans from GitHub Actions, GitLab CI, or Jenkins if you want them in the pipeline.

How a deployment works

Three things from you. Compose from us.

1

You provide three environments

A place to publish the web UI, PostgreSQL or SQL Server, and a place to publish the backend API.

2

We bring Docker Compose

That is the only install step we run with you.

3

You start scanning

The dashboard is for website and PDF scans. Recurring crawls and CI/CD are there if you need them.

We do not run a custom OS setup, IIS, or bare-metal services with you. Compose is the install.

For IT

What we need, and how it installs

You provide three environments. We publish FontScanner onto them with Docker Compose — that is the only install step we run with you.

What we need from you

  1. 1Web UI environmentWhere we publish the dashboard — a VM, app service, or equivalent your team already operates.
  2. 2DatabasePostgreSQL or Microsoft SQL Server. Users, scans, and reports live here.
  3. 3Backend API environmentWhere we publish the API — website crawls, PDF extraction, and CI/CD.

Install

  1. You prepare the three environments.
  2. We give you the Compose file and container images.
  3. You start the stack:
docker compose up -d

Then publish the web UI and the API on those environments. People scan websites and PDFs from the dashboard. Recurring crawls and CI/CD are there if you need them.

Cloud vs on-prem

Same engine, different place it runs.

Cloud EnterpriseOn-Prem
Where data livesFontScanner cloudYour PostgreSQL or SQL Server
What you can scanWebsites, PDFs, and imagesWebsites and PDFs
Scheduled scansDaily, weekly, or monthly website crawlsDaily, weekly, or monthly website crawls
What you can reachPublic websites (and what you expose)Intranet, staging, and public sites
CI/CDCI/CD API in our cloudThe same scans from your CI/CD
Who operates itFontScannerYour environments — we deliver Compose

On-prem questions

What is FontScanner On-Prem?
FontScanner installed on your infrastructure. You provide a web UI environment, PostgreSQL or SQL Server, and an API environment. We bring Docker Compose and work with your team.
How do people scan?
From the dashboard: paste a URL, upload a PDF, or set a recurring website crawl. The same website and PDF jobs can run from CI/CD if you want that.
What do we actually install?
Docker Compose onto three environments you provide: web UI, PostgreSQL or SQL Server, and the backend API.
Which database?
PostgreSQL or Microsoft SQL Server. You host it; we connect the API to it.
Can it scan sites that are not on the public internet?
Yes. The API runs on your network, so intranet, staging, and pre-prod are in reach. Public sites go out through your firewall.
Can we schedule recurring scans?
Yes. Daily, weekly, or monthly website crawls from the dashboard — the same scheduler as in our cloud.
Does it work with CI/CD?
Yes, if you want scans in the pipeline. Website and PDF jobs can run from GitHub Actions, GitLab CI, or Jenkins.
Can we use SSO?
Yes. We can set up Entra ID, Okta, or SAML if you want it.
When should we pick cloud instead?
If you mainly scan public websites and prefer we operate the stack, Cloud Enterprise is simpler. Choose on-prem when website and PDF scans must stay inside your network.

Put FontScanner on your network

Talk to us. You provide the web UI, the database, and the API environment. We install with Docker Compose.

  • Install on your infrastructure
  • Website and PDF scans from the dashboard
  • Your PostgreSQL or SQL Server