Loading the 3D line
  1. 01 SeeCodes
  2. 02 Local pDigger
  3. 03 SCADA pDigger
  4. 04 Factory pDigger

eprojac · applied work intelligence

Work, made visible.

We build software that turns every kind of work — AI-agent code, desktop actions, business processes and the factory floor — into structured data you can inspect.

Station 01 · Developer tokens

SeeCodes

Unbox AI agent work in real time.

SeeCodes connects Jira Cloud tickets to the AI-agent work happening in VS Code and Cursor. Progress and confidence sync back to the ticket, risk flags surface early, and local checkpoints keep the trail.

  • Jira Cloud
  • VS Code · Cursor
  • US · EU · UK data regions
seecodes.com

Station 02 · Window actions

Local pDigger

Your past has answers.

Local pDigger records the work you see on your computer — the app windows you focus on Mac or Windows, the clicks and the keyboard shortcuts — and keeps that history on the device. Ask a question and the answer comes with the moment it came from; repeated work becomes editable skills.

  • Windows · clicks · keys
  • History stays local
  • Answers with evidence
local.pdigger.com

Station 03 · Factory states

SCADA pDigger

Process mining from the signals a factory already emits.

Every machine state change — run, idle, set-up, fault — becomes an event. SCADA pDigger mines those events into the process that actually runs: where the time goes, which transitions repeat and where work waits. Demos are shown by invitation.

  • SCADA state events
  • Task & process mining
  • By invitation
Request a demo

Station 04 · Research

Factory pDigger

One frame in. Scene data out.

Our single-frame 3D decomposition turns one monocular camera frame into surface orientation, relative depth, people as a body model and skeleton, and individual items — lifted into 3D and packaged as scene data. The hologram above the gantry is simulated in your browser: every tray brings new stones — loose ones of four kinds with a second layer and gaps, or packed pavers like those in our real frames — and a worker gripping one stone while a fingertip rests on another. Each scene shows one stage in turn: frame, surfaces, depth, people or stones. Real frames are on the research page.

  • 1 frame · 1 camera
  • Stones by kind & layer
  • Body model + skeleton
  • Simulated here
Open the decomposition

How we build

Instruments, not oracles.

Evidence over claims

Answers link back to the moment they came from. Scene data carries its own honesty flags — relative scale, no invented surfaces.

Local where it matters

Local pDigger keeps work history on the device. SeeCodes lets teams choose a US, EU or UK data region. This site sets no cookies at all.

Real lines, real frames

Our research runs on frames from working production cells. People in them are published only as geometry — depth points, a skeleton and a body model — never as image pixels or identities.

Research

Take the frame apart yourself.

Seven stages, two camera frames: the worker as a body model and skeleton, and every stone by kind, with the holes between them. Orbit them and switch layers.

Open the decomposition
  1. 01Frame
  2. 02Surface orientation
  3. 03Relative depth
  4. 04Refinement
  5. 05Body model & skeleton
  6. 06Stones, kinds & holes
  7. 07Lifting & package

Company

eprojac Ltd

A software company registered in England and Wales. We build products for people who want to see how work actually happens — and research the parts that don’t exist yet.