ENTR

Make Complexity Work.

Engineering Intelligent Systems.
Intelligence for the Physical World.

01 · Engineering position

Software — Intelligence — Systems

A technology and engineering company.

MERYNOX develops software for automotive service operations and prototype-stage engineering architectures for heavy-vehicle environments.

Current work includes automotive service-record workflows, a heavy-vehicle warning architecture exercised in simulation, and YAMAN's account and onboarding foundations.

Software

Applications that organize operational work, starting with customer, vehicle and service-order workflows.

Intelligence

Research into software-based perception and contextual information. Each product distinguishes verified implementation from design direction.

Systems

Perception, warning and system-health architecture for physical environments, developed so far in software and simulation.

02 · System thinking

Intelligence for the Physical World.

The engineering disciplines MERYNOX works across.

Engineering Intelligent Systems.

Physical world Computer Vision / Perception · Edge Systems Connected Systems · Automation · Data / Integrations Software · AI & Intelligence Engineering Intelligent Systems. Intelligence for the Physical World.
03 · Products

Products

Four platforms for operational environments, alongside YAMAN — by Merynox, exploring personal-context experiences.

04 · Operational orchestration

MERYNOX Service Operations Platform

In development Product page

Operational orchestration platform designed to streamline and coordinate complex service operations, technician workflows, and service event lifecycles.

Servicelifecyclerecord Customer Vehicle Service order Workflow Status

Data model · three record types · field names only · no customer data

P1CustomerName and contact details. Each service order references its customer directly.
P2VehiclePlate, make and model, mileage.
P3Service orderOrder number, mileage at intake, reported issue, diagnosis, status. One customer, one vehicle.
P4WorkflowService-order workflows for automotive service operations.
P5StatusThe order's recorded state, held on the service-order record.

Current work · Customer, vehicle and service-order workflows for automotive service operations.

05 · Field operations

MERYNOX Field Operations Platform

Entry / Exit Movement Yard zones Occupancy Dock operations Edge intelligence Evidence Status
P1Entry / Exit
P2Movement
P3Yard zones
P4Occupancy
P5Dock operations
P6Edge intelligence
P7Evidence
P8Status
06 · Awareness / Perception

MERYNOX Perception & Safety Platform

Prototype development

Perception and safety infrastructure integrating sensor awareness and environmental understanding for operational safety across complex physical environments.

Environment Perception Detection Safety envelope Hazard · Risk WarningPresentation boundary System health Event

Simulation only · not vehicle-integrated · no field testing · no autonomous-driving claim

P1EnvironmentLane geometry and roadside constructed from simulated inputs.
P2PerceptionMulti-sensor fusion builds a scene understanding, in simulation.
P3DetectionVehicles, pedestrians, cyclists and obstacles are classified.
P4Safety envelopeDrivable space with dynamic boundaries.
P5Hazard boundaryA detected risk is classified and contained.
P6WarningRisk state crosses the presentation boundary. One direction only.
P7System healthSensor and compute status: operational, or not.
P8EventScene snapshot and data recorded for analysis.

Current work · Software architecture, contracts and simulation. Not integrated into a vehicle; no field testing.

Simulated inputs → Safety core → Presentation boundary → Machine-channel intents · One direction only: risk state to warning state to presentation.

Simulation only · Software-simulation architecture derived from accepted design records. Not a vehicle-integrated system, field-test result or product interface.

07 · Fluid process automation

MERYNOX Fluid Process Automation Platform

Interlock Pump control Valve logic Fluid routing Dosing Process Monitoring Drainage / recovery
P1Interlock
P2Pump control
P3Valve logic
P4Fluid routing
P5Dosing
P6Process
P7Monitoring
P8Drainage / recovery
08 · Context

YAMAN — by Merynox

In development

An in-development product exploring personal-context experiences under Merynox engineering.

Current work
Account and onboarding foundations. Broader contextual capabilities remain design direction.

Completed at the 28 September 2026 checkpoint
Engineering foundation. Account, profile and onboarding foundations.

Not started at the 28 September 2026 checkpoint
Later phases.

Development record · Development phases recorded in the 28 September 2026 source snapshot. Not a product interface.

Person Profile Context Memory Knowledge Preferences Services Guidance Continuity

Engineering foundation complete · later phases not started

09 · Technology

Technology

The engineering disciplines MERYNOX works across.

Physical world Computer Vision / Perception Edge Systems Connected Systems Automation Data / Integrations Software AI & Intelligence Foundation stack

Areas of Focus

The operational contexts MERYNOX engineers for.

Our current focus areas are automotive service software and prototype-stage heavy-vehicle system architecture.

Operating field 01Automotive Service→ Service Operations Platform
Operating field 02Commercial Vehicles→ Perception & Safety Platform — prototype development
10 · Engineering method

How Merynox Works

A three-phase methodology.

01Understand

Immersion into real-world operational complexity, physical constraints, and human-machine friction points.

02Connect

Synthesizing fragmented data, physical systems, and software layers into a coherent operational architecture.

03Build

Engineering reliable software, intelligent models, and robust systems designed for operational dependability.

Our engineering work connects documented requirements, implementation boundaries and verification evidence.

11 · Closing

Let’s build what
complexity demands.