We Built the Tool We Needed at 3 AM.
Every architect knows the “ghost” haunting their hard drive. This nightmare usually takes the form of a file named PROJECT_FINAL_v2_USE_THIS_ONE_FINAL.rvt. Additionally, it manifests as three hours wasted digging through an inbox for a single PDF markup while a deadline looms. Ultimately, you realize that you have become a digital janitor rather than an actual designer.
Our Story: From the Studio Floor to the Source Code
We didn’t build HyperArch in a boardroom. Instead, we forged it in the design studios of Singapore Polytechnic and the lecture halls of NUS. For years, we pulled late-nighters and watched file fragments, broken links, and “version panic” swallow our best creative energy.
Furthermore, we saw brilliant peers—future licensed architects—burn out because administrative chaos consumed 30% of their lives. Consequently, we decided that “the way it’s always been done” simply wasn’t good enough.
The Manifesto
We believe:
- Design is Sacred: You should focus your time on spatial logic and human experience, not folder structures.
- Version Control is a Right: Architects deserve the same “undo” power and timeline clarity that software engineers have enjoyed for decades.
- Collaboration Shouldn’t Hurt: Sharing a file should never feel like a gamble.
The Team
A team of Architecture and Business A.I. Systems students at the National University of Singapore founded HyperArch to bridge the gap between the drafting table and the cloud. Since NUS Enterprise backs our mission, we are currently building the definitive operating system for the AEC industry. Specifically, we aim to kill the “Final_v3” madness and give architects their evenings back.