Company
About SPX
Built by HammerHeads Engineers, SPX brings practical experience in control systems, industrial networks and connected devices to simulation and testing.
Aleksander Stanik
Creator of SPX · Founder of HammerHeads Engineers
Aleksander is an engineer and software architect with more than 20 years of professional experience. He specialises in software for control systems and industrial networks, with expertise spanning embedded systems, IoT and cybersecurity.
He combines hands-on software development, system architecture and technical leadership. This engineering background shapes SPX and its focus on practical, repeatable testing of connected systems.
Why SPX exists
Connected software needs devices it can communicate with and behavior it can test. Hardware may arrive late, be busy in the lab, or make failure scenarios difficult to reproduce.
SPX gives engineers a controlled environment for that work: run virtual devices, connect a real client and inspect the response. The aim is to make integration testing practical before hardware arrives, alongside it and during later development.
From engineering practice to SPX
Experience across device software, communication and system integration gives SPX a practical direction: help engineers understand how a connected system responds to commands, changing conditions and failures.
Who it is for
SPX is for integrators, automation engineers and software or QA teams who need to test how connected systems behave. Start with a library model, your own YAML or an AI-assisted workflow.
What that experience brings to SPX
Working across software, electronics and real equipment shapes three priorities in SPX:
- Inspectable models: make behavior and assumptions explicit in YAML.
- Real communication: check commands and readbacks through the protocol your software uses.
- Repeatable evidence: exercise a scenario, inspect its result and keep the model for the next test.
Next step
See the engineering in action.
Run a virtual device or explore a working protocol example.