Overview
zw3rk is a small engineering company that fixes hard, low-level software problems for other teams: compilers, build systems, and getting programs to run on new hardware1. It suits companies whose engineers are stuck on a failure that crosses tools, operating systems, and release pipelines, and who want one senior specialist to own the fix. Based in Singapore, zw3rk works while its European clients sleep, so a team can hand off a problem in the evening and find code, tests, or findings waiting the next morning1.
The company is run by Moritz Angermann, a longtime contributor to GHC, the main compiler for Haskell, the programming language used to build Cardano's node software2. Its Cardano tie runs through his ZW3RK stake pool, a server that helps run the Cardano network in return for rewards. The Cardano Foundation has profiled how the pool helps pay for GHC build machines and hands out ready-to-run copies of the Cardano node software to other pool operators2.
Key Features
- Help with compiler and toolchain problems. zw3rk works on compiler internals, linkers that stitch compiled pieces into one program, and cross-compilation, which means building software on one kind of computer so it runs on another, such as phones or ARM chips1.
- Reliable builds and releases. zw3rk sets up Nix, Hydra, and binary caches, the systems that turn source code into tested, shippable programs the same way whenever a developer makes a change1.
- Linux programs on a Mac. The open-source hyper-linux tool runs selected Linux programs on Apple Silicon Macs3, each in a lightweight virtual machine of its own, without Docker or a full Linux installation1.
- Faster feedback on code changes. The hydra-tools project connects GitHub, the Hydra build server, and a shared build cache so builds react to code changes as they happen instead of checking on a timer1.
- Ready-made Cardano node builds. Moritz Angermann's ZW3RK pool has supplied self-contained builds of cardano-node for 64-bit ARM and x86 machines, so pool operators can skip compiling the software themselves2.
What to Expect
For engineering teams, hiring zw3rk works like bringing in a specialist contractor for one bounded problem rather than a general agency. Most engagements start small: a diagnostic sprint that ends with a reproduction and a recommended fix, a focused implementation, embedded senior work on a defined workstream, or stewardship of changes meant for shared open-source projects1. Contact starts with an email or a short form that asks what the hard part is, and the person who discusses the problem is the one accountable for the result1.
For developers curious about the work, the zw3rk GitHub organization and the engineering blog hold public code and long-form posts on GHC, cross-compilation, and linker bugs. The Haskell Foundation interviewed Moritz Angermann about cross-compilation to Windows and mobile platforms on its podcast4.
For Cardano stake pool operators, the most visible output is the node builds. The Armada Alliance guide for Raspberry Pi pool operators walks through downloading and installing one of these builds5. The Cardano Foundation profile also describes experimental node packages for Synology home storage devices, meant to give people a local node on their own network, and cardano-node apps for iOS and Android phones that are not yet meant for everyday use but could one day act as gateways for lighter wallets2.
