The Product
The infrastructure layer work has always been missing
A lightweight agent. An encrypted on-premise dataset. A complete picture of how operational work actually unfolds — across every tool, every team, every day.
Capture Specification
What the agent records.
ALPIX captures behavioral workflow signals — not content. It records patterns, sequences, and transitions. Not documents, keystrokes, or personal communications.
Cross-software transitions
Which applications are active, in what sequence, for how long. Application switching patterns. Time allocation by software, role, and task type.
File interaction patterns
Which files are opened, compared, edited, closed. Document co-occurrence patterns. File types involved in specific workflow sequences.
Sequence and duration
How long each step takes. Where hesitation occurs. The rhythm and pacing of complex multi-step workflows. Time spent between steps.
Interaction patterns
Mouse and keyboard behavioral signals indicating cognitive load, comparison behavior, review thoroughness, and decision point proximity.
Cross-session sequences
How workflows span across sessions, days, and team members. Handoff patterns. Workflow completion signatures.
- Document content or text
- Personal communications
- Passwords or auth inputs
- Browser URLs or web content
- Audio or video
- Personal device activity
ALPIX captures the behavioral meta-layer of work, not the content of work. The distinction is architectural, not administrative — the agent is not capable of capturing content.
Technical Architecture
Lightweight. Local.
Invisible to the workflow.
Silent enterprise installation
Deploys via Group Policy, SCCM, Intune, or manual install. No end-user action required. No workflow disruption.
Minimal system resources
Background system process. Sub-1% CPU in standard operation. Under 50MB memory footprint. Invisible to the user.
Real-time behavioral capture
Workflow signals captured in real time, structured into sequences, and written to the local encrypted store within milliseconds.
AES-256 at source
Data is encrypted on the endpoint before it is written anywhere. The encryption key is held by the client. ALPIX does not hold, request, or transmit keys.
On-premise encrypted store
Integrates with existing enterprise infrastructure — on-premise servers, private cloud, or air-gapped environments.
Centralized agent console
IT administrators manage deployment, scope, and permissions through a local console. Role inclusion/exclusion and consent management handled centrally.
Tier 2
When the dataset is ready, unlock the intelligence layer.
Tier 2 activates when your operational dataset has sufficient depth — typically 60 to 90 days after full deployment. The analytical layer transforms your encrypted workflow data into operational intelligence you can act on.
Talk to us about Tier 2- Workflow bottleneck detection
- Process deviation analysis
- Time allocation by role, team, software
- Automation readiness scoring
- Cross-role workflow comparison
- Operational expertise mapping
- Long-term operational trend analysis
Deployment & Onboarding
From signed contract to live capture in two to four weeks.
Technical scoping
IT integration review. Infrastructure assessment. Agent distribution method selection. Privacy & works council documentation prepared.
Pilot deployment
Agent deployed to scoped pilot group (10–30 seats). Data store configured. Admin console live. IT team trained.
Validation & expansion
Data quality confirmed. Capture coverage validated. Scope expanded to full deployment group.
Full deployment
All seats live. Dashboard access granted. Tier 1 operational.