Pilot Program
See your operational reality before committing.
A structured 30-day pilot that gives you full visibility into what Alpyx captures, how the encrypted dataset looks, and what workflow intelligence emerges — before committing to Tier 1. Two to three Swiss SME pilots ongoing.
30 days · 10–50 seats · revFADP-aligned · Full data sovereignty throughout
How the Pilot Works
Three phases. Four weeks. A complete picture.
Technical setup, revFADP scoping, works council brief
We work with your IT team to deploy the agent to the pilot group (typically 10–50 seats, one or two operational teams). revFADP compliance documentation, DPIA template, and works council materials are provided. No workflow disruption. Agent live by end of week.
Capture and accumulation
The agent runs passively. Your team works normally. Encrypted workflow data accumulates on your infrastructure. Alpyx has zero access to it — by architecture. Capture scope can be reviewed and adjusted at any time through the admin console.
First workflow review
Our analysts work within your environment (no data leaves) to produce the first workflow review: cross-software time allocation, initial bottleneck indicators, taxonomy validation against your operational reality, and the first benchmark for cycle-time savings under Tier 2.
Pilot Outcomes
What the pilot delivers.
A quantified picture of how work actually happens.
Time allocation by application, workflow stage, team, and role. The first behavioural operational baseline your organisation has ever had — based on observed sequences, not self-reporting.
A structured analysis of your first 30 days.
Cross-software workflow patterns, deviation indicators, bottleneck candidates, and automation-readiness signals — delivered as a formal report presentable at board or management level.
Confirmation of the zero-knowledge architecture.
Your IT and security teams will have reviewed the agent, the encrypted store, the encryption model, and the capture scope directly — with complete access. Architecture, not policy. No black boxes.
30 days of operational data on your infrastructure.
Whether or not you proceed beyond the pilot, the dataset is yours. Alpyx has no way to remove, return, or recall it. You own it. You keep it.
What the Pilot Requires
Lightweight requirements. No infrastructure transformation.
Windows 10 / 11 enterprise devices. Standard enterprise management tools (Group Policy, SCCM, or Intune). Sub-2% CPU and under 50MB RAM target footprint per endpoint.
On-premise server or VM within the client network perimeter. Minimum 4 vCPUs, 8GB RAM, 500GB storage for a 30-seat pilot. No cloud dependency. Air-gapped compatible.
Local network only. TLS 1.3 between endpoints and the encrypted store. No inbound or outbound internet connections initiated by the agent.
Estimated 4–8 hours of IT time during deployment week. The local admin console reduces ongoing management to near zero.
Frequently Asked Questions
What pilot applicants ask us most.
How much does the pilot cost?
The pilot is offered at a fixed fee covering deployment, the 30-day capture window, and the workflow review. Contact us for current pricing. There is no commitment to Tier 1 or Tier 2 subscription beyond the pilot.
Can we limit which employees are included?
Yes. Pilot scope is defined at the team and role level. Individual inclusion and exclusion is managed through the local admin console. You control exactly which devices and roles participate.
What happens to our data if we don't proceed after the pilot?
Your data remains on your infrastructure. It is not deleted by Alpyx — we have no access to delete it. You choose what to retain, archive, or remove.
Can we run the pilot in an air-gapped environment?
Yes. Alpyx is compatible with air-gapped deployments. No internet connectivity is required. Deployment in highly restricted environments — including regulated medtech and finance — is supported.
How long before we see meaningful intelligence?
Initial patterns are visible within 14 days. The workflow review at week 4 delivers the first structured analysis. Tier 2 analytics (deviation detection, rework loops, automation candidates) activate at 60–90 days of full deployment.
How does this fit with revFADP and works council obligations?
The deployment package includes a revFADP compliance analysis, DPIA template, employee notification templates, and works council information materials. A Swiss data protection law firm has reviewed the consent framework and capture architecture.
Apply for the Pilot Program
The pilot takes four weeks and requires two to four hours of IT time.
We accept a limited number of pilot partners per quarter to ensure each receives dedicated deployment support and a rigorous intelligence review.
30-minute discovery call to confirm fit and scope
Technical scoping with your IT team (60 minutes)
Pilot agreement and privacy documentation signed
Deployment week begins
Current pilot availability: 2026 — seed raise targeting Q3 2026