Portfolio

Case studies, product foundations, and research work labeled by maturity.

Public examples are sanitized and intentionally avoid exposing proprietary code, private client details, unsupported metrics, invented screenshots, or claims that research systems are commercially available.

Portfolio structure

Operational work is not presented at the same level as long-term research.

The portfolio separates real or operationally relevant work from internal platforms and research programs. Each case study uses the same structure so maturity, evidence, and future role are clear.

Client and Operational Deployments

Real work delivered or shaped for operational use, sanitized where public disclosure would expose private customer or operational details.

Available

Client and Operational Deployments

Manufacturing workflow and material-control systems

Problem
Operational teams need clearer job status, material movement, approvals, and evidence without exposing private customer details publicly.
Operational constraints
Shop-floor adoption, sensitive operational records, role boundaries, audit history, and the need to avoid overbuilding before the workflow is proven.
Epyk approach
Start with the highest-friction path, model the real handoffs, then add records, permissions, dashboards, and history around actual work.
What was built
Reusable workflow and inventory patterns for jobs, requests, approvals, material movement, low-stock awareness, and operational audit trails.
Current status
Available through focused client engagements; public examples remain sanitized.
Evidence or result
The public site does not publish proprietary screenshots, customer files, or metrics.
Future role in the ecosystem
Forms the commercial base for operational software and inventory control inside the broader ecosystem.
WorkflowInventoryApprovalsAudit history
Available — Pending Review

Client and Operational Deployments

Manufacturing CRM and Order Visibility Platform

Problem
Sales and marketing teams track quotes, active jobs, and leads across spreadsheets, email, and memory, with no visibility into where an order actually sits on the floor once it has been released to production.
Operational constraints
Public disclosure is limited; customer records, screenshots, implementation details, and results are not published from this site.
Epyk approach
Build practical internal software around the real workflow while keeping sensitive operational context out of public marketing.
What was built
A CRM and order-visibility platform for desktop and mobile covering leads and sub-leads, quotes and offers, and job pipeline stages from prospective through active to completed — combined with live order position tracking through production stages such as press, mold, machining, and plating. Built to run standalone or connect optionally to an existing ERP or workflow system rather than replacing it.
Current status
Delivered and available through engagement; the initial client deployment is awaiting review.
Evidence or result
No fabricated screenshots, metrics, or customer claims are included.
Future role in the ecosystem
Informs Epyk's manufacturing modernization and operational software patterns.
CRMSales pipelineLead trackingOrder visibility

Epyk Products and Internal Platforms

Reusable platforms, product directions, and reference architectures that support current services and future ecosystem integration.

Active Development

Epyk Products and Internal Platforms

Sentinel Vision / Epyk Perception

Problem
Physical events such as movement, presence, staging, and process drift are hard to connect to jobs or inventory after the fact.
Operational constraints
Legitimate operational purpose, local processing, privacy boundaries, lighting conditions, camera placement, retention policy, and human review.
Epyk approach
Use operational computer vision only where it produces useful signals and can be governed by clear permissions and deployment boundaries.
What was built
Computer vision and object-tracking concepts that inform Epyk Perception and the longer-term Epyk-3 layer.
Current status
Working direction under active development; complete Epyk-3 is not presented as a finished commercial platform.
Evidence or result
Public claims are limited to development status and feasibility-oriented engagement.
Future role in the ecosystem
Feeds event awareness, evidence, and environmental understanding into local-first systems.
PerceptionDetectionTrackingEvidence
Reference Architecture

Epyk Products and Internal Platforms

Epyk Edge-18 reference architecture

Problem
Private AI, operational software, and secure modernization need a local foundation that owners can understand and control.
Operational constraints
Compute capacity, storage, networking, segmentation, service health, backup, recovery, observability, and physical maintainability.
Epyk approach
Design a local infrastructure pattern that can host private services and connect outward only where the owner chooses.
What was built
A reference architecture for Edge-class compute, storage, networking, security, observability, AI hosting, and recovery.
Current status
Substantially designed as a reference architecture, not a standardized shipping product.
Evidence or result
Presented as architecture, not as a fabricated deployment or commercial availability claim.
Future role in the ecosystem
Acts as the infrastructure anchor for Epyk AI, local software, perception, and future environmental systems.
EdgeInfrastructurePrivate AIReference
Active Development

Epyk Products and Internal Platforms

Epyk AI orchestration

Problem
Private documents, operational data, local services, and model tools need controlled orchestration instead of scattered experiments.
Operational constraints
Data boundaries, permissions, model routing, tool access, offline behavior, and auditability.
Epyk approach
Coordinate specialized models, retrieval, tools, and local infrastructure under owner-defined permissions.
What was built
Architecture patterns for private retrieval, local model hosting, and permission-aware tool execution.
Current status
Active development; private AI engagements can be scoped from this foundation.
Evidence or result
Presented as internal platform direction and engagement capability, not as a generic public AI product.
Future role in the ecosystem
Becomes the intelligence layer connecting Epyk Edge, operational software, perception, and future devices.
Private AIRetrievalLocal modelsTools
Active Development

Epyk Products and Internal Platforms

CNC monitoring and controller integration

Problem
Machines and controllers often contain useful status and telemetry but are difficult to connect without creating operational risk.
Operational constraints
Legacy protocols, safety boundaries, segmented networks, uptime expectations, and practical operator visibility.
Epyk approach
Connect carefully through adapters, monitoring, and local dashboards while preserving machine safety and network boundaries.
What was built
Controller-integration and monitoring patterns informed by CNC and manufacturing experience.
Current status
Active development and custom implementation area.
Evidence or result
No production metrics are published.
Future role in the ecosystem
Feeds secure industrial modernization, Epyk-2 control patterns, and Myne-3 fabrication research.
CNCTelemetryAdaptersDashboards

Research and Engineering Laboratory

Long-horizon explorations and experimental architectures that point toward the complete ecosystem without being sold as finished products.

Research Program

Research and Engineering Laboratory

Epyk-1 spatial-interface work

Problem
Work surfaces should be able to host sessions without owning the user's data or becoming permanent endpoints.
Operational constraints
Shared spaces, personal sessions, privacy, input methods, Edge hosting, and graceful non-AR fallback.
Epyk approach
Treat tables, windows, and temporary surfaces as portals into owner-controlled sessions.
What was built
Concept architecture for ambient spatial interfaces and portable workspaces.
Current status
Research program.
Evidence or result
No commercial availability or deployment metrics are claimed.
Future role in the ecosystem
Forms the environmental interface baseline for The Epyk Environment.
Spatial interfaceSessionsEpyk-1
Research Program

Research and Engineering Laboratory

Myne research programs

Problem
Communications, energy resilience, personal context, and fabrication need long-term technical work before they can be responsibly integrated.
Operational constraints
Physical limits, safety, power, manufacturability, user choice, recoverability, and honest maturity labeling.
Epyk approach
Separate long-horizon research from present commercial offerings while keeping the shared Epyk language in view.
What was built
Named research tracks for Myne-0 communications, Myne-1 energy resilience, Myne-2 wearable context, and Myne-3 fabrication.
Current status
Research program.
Evidence or result
The site labels these as research and does not imply commercial readiness.
Future role in the ecosystem
May support future communications, power, personal computing, and fabrication layers in the integrated ecosystem.
Myne-0Myne-1Myne-2Myne-3

Evidence boundaries

No fabricated proof.

The repository currently provides brand assets, not public product screenshots or approved client visuals. Where screenshots or operational metrics are not available for public release, the site says so directly.

Need a system shaped around a real operation?

Epyk can use existing operational patterns, internal platforms, and reference architectures as starting points for focused client builds.

Discuss Your OperationView Solutions