Blog
Notes from the workbench.
Plain notes on accessible PDFs, how Operator Co tests its software, and what is being built next. Each post says what was measured and what was not.
Why Operator Co builds software that stays on your PC
Three rules behind every Operator Co app: pay once, process files locally, solve one real problem properly. And why PDF accessibility came first.
Accessibility · 4 min readWhat a PDF/UA check can and cannot tell you
A veraPDF pass proves the machine-checkable rules hold. It cannot judge whether a picture description is useful or whether the reading order makes sense.
Testing · 3 min readHow TagSmith-PDF 0.7.0 was tested: 97 real documents
What was measured on the 0.7.0 release build, with veraPDF 1.30.2, and what those numbers do and do not prove.
Roadmap · 2 min readWhat Operator Co is building next, and what it is not
Three apps are in development and none is for sale yet. A plain look at where each one stands, and what Operator Co will not make.
Founder · 3 min readWhat Is a Local Operator? Software That Stays on Your PC
People search for “local operator” and find cloud infrastructure. We explain why a local operator runs on your own PC instead.
Founder · 3 min readLocal LLM Deployment vs Cloud AI: Why TagSmith Runs Offline
Local LLM deployment keeps your data on your machine. Why TagSmith-PDF uses a built-in local vision model instead of cloud AI.
Founder · 3 min readCloud Operator vs Local Desktop: Which Is Right for PDF Accessibility?
Comparing cloud operator platforms with local desktop software for remediating confidential PDFs.