Open source

The door nobody watches.

PaperTrail is our open source print auditing tool for Windows. It reads the Print Service event log, turns it into a searchable record of who printed what, where and when, and produces an audit report you can hand over. It runs entirely offline, so nothing it sees ever leaves the building.

PaperTrail · DashboardDemo environment
The PaperTrail dashboard for one audit case, with totals for users, printers, pages and jobs, failed jobs, and a chart of pages printed over the last thirty days
Real product screen, sample dataAzbersInnovations

Screens from PaperTrail running locally with a month of sample print jobs. The users, machines and documents are sample data.

Why we kept it

A narrow tool, kept honest by being readable.

PaperTrail is not a flagship and was never meant to be. It stays in the portfolio because print remains a genuine exfiltration path, because small utilities age well, and because publishing the source is the only reasonable way to ask someone to run an auditing tool on their estate.

Visibility on a quiet channel

Most investigations can reconstruct what left by email or upload. Far fewer can say what walked out of the building in a folder.

Useful during an investigation

When something has gone wrong, a print record is often the difference between a theory and a timeline.

Open by principle

Anything that watches user activity should be inspectable by the people it watches. The source stays public for that reason.

How it works

From an event log to a signed off report.

An audit in PaperTrail is a case. You open one, bring in the logs, read what they say, and finish with a report that carries the auditor's name and the period it covers.

01 · Case

Open an audit

Each case keeps one organisation, site and period apart from the rest.

02 · Import

Bring in the logs

Read the local system live, or import one log file or a whole folder.

03 · Clean

Keep only real jobs

Duplicates are merged and system noise is separated from printing.

04 · Read

See the pattern

By user, computer, printer, paper size and hour of the day.

05 · Report

Produce the PDF

A branded audit report with the sections you choose and the auditor named.

06 · Export

Take the data

CSV or JSON for anything the report does not cover.

What it records

Four fields, and the reason each one matters.

It is deliberately small. Everything it captures is something an investigation later turns out to need.

01

What was printed

The document name and the job, so a later question about a specific file has an answer rather than a shrug.

02

Who printed it

The user account behind the job, which is usually the first thing anyone asks and the hardest thing to reconstruct afterwards.

03

Where from

The workstation and the queue, which is what turns a single record into a pattern across an estate.

04

When

The timestamp, which is what makes the record a timeline rather than a list, and what makes after hours activity visible at all.

What you hand over

Reports written for the person who asked the question.

An audit usually starts with a narrow question from someone who is not technical. Who printed the contract? How much does the finance floor print after hours? The reports answer in their terms.

Reports

Five views of the same record.

Every report is drawn from the same cleaned record for the case, so the executive summary and the per user detail can never disagree. Choose the sections, name the auditor and the period, and export a branded PDF.

  • An executive summary with totals and the busiest printers and people
  • Top users by pages printed, for the question that usually starts an audit
  • A paper size breakdown, which is where cost questions get answered
  • Per user detail, job by job, for an investigation that needs a timeline
  • System events kept apart from printing, so spooler noise never inflates the count
PaperTrail · ReportsDemo environment
The PaperTrail executive summary report, with general statistics, top printers and top users by pages printed
Real product screen, sample dataAzbersInnovations
Before you start

Three things that decide whether the record exists at all.

Most print audits that come back empty fail for the same few reasons, none of them about the tool. Get these right first.

01

Switch the log on

Windows keeps the Print Service operational log disabled by default. Until someone enables it, there is nothing to audit, and a gap that started on day one cannot be filled later.

02

Collect from the print servers

Where printing goes through a server, its log covers every desk behind it. Where people print directly, each workstation holds its own piece, and a folder import brings them together.

03

Agree what it is for

Print records show what people do. Tell staff the record exists and what it is used for, and keep access to it as narrow as the investigation that needs it.

OFFLINE

Runs on one Windows machine. Nothing it reads is sent anywhere.

CASES

Each audit kept apart by organisation, site and period.

EXPORTS

Branded PDF for people, CSV and JSON for other tools.

OPEN SOURCE

The code is public, so anyone it watches can read it.

Questions we get asked

Before you get in touch

The questions that come up most often, answered the way we would answer them on a call.

Is it really free?

Yes, and the source is public. Anything that watches user activity should be inspectable by the people it watches, which is the main reason it is open rather than a commercial decision.

Why does print still matter?

Because most investigations can reconstruct what left by email or upload, and far fewer can say what walked out of the building in a folder. It is the one channel that almost nothing watches.

Does it read the documents?

No. It records the job, the user, the host and the time. The content of what was printed is not captured, which keeps it useful for investigation without turning it into surveillance.

Will you keep maintaining it?

It stays in the portfolio. It is deliberately small, which is precisely why it ages well and why it has not needed to change much.

Need print visibility across an estate?

Whether that means PaperTrail on its own or a broader look at data leaving the organisation, the conversation is worth having either way.