1. Inspiration – Where it started
The idea behind CUBE comes from a simple frustration: important decisions affect our everyday lives, but we often have very little clarity about how those decisions are made or what information they are based on. I started thinking about how we could make sense of overwhelming information instead of constantly adding to it. My interest in building hardware systems began in my second year of college, when I built an unmanned aerial vehicle and reached the final round of a competition. That experience pushed me towards building things that solve real problems.
2. What CUBE does
CUBE (Cybernetic Universal Behavioral Engine) is a hardware-led sensing, monitoring, triage and long-range communication system. It is designed to bring information from distributed environments together, understand its significance and identify what needs attention first. The idea is not just to collect more data, but to help people and institutions see what is happening, understand what matters and communicate important findings even in environments with limited connectivity.
3. How I built it
I've been developing CUBE independently, starting with its underlying architecture rather than jumping straight into building a product. I've broken the system into different layers, covering distributed sensing, local computing, information analysis and communication. I've also been working on the hardware side through LongLink, the distributed sensing infrastructure intended to work alongside CUBE. My approach is to build systems that can perform meaningful computing locally without depending entirely on cloud infrastructure or constant internet connectivity.
4. Challenges along the way
One of my biggest challenges has been turning a very broad idea into something technically structured and achievable. I had to understand how different hardware components, computing systems and communication technologies could work together. Working independently also means researching, making technical decisions and figuring things out without a dedicated team. There have been plenty of moments when I had to step back, question my assumptions and rethink parts of the architecture.
5. Where I stand today
I have developed the foundational architecture for CUBE and worked towards a proof of concept for its distributed sensing layer. However, the core CUBE system and its complete integration are still under development. My immediate milestone is to bring these individual components together into a working integrated prototype and validate it in practical environments.
6. What I've learned
This journey has taught me that having an interesting idea is probably the easiest part. The real challenge is understanding the problem deeply enough to build something that actually works. I've learned to break complicated problems into smaller parts, question my own assumptions and become comfortable with not having every answer at the beginning. Most importantly, I've learned to keep moving even when progress is slower than expected.
7. What's next for CUBE
My next goal is to develop a working prototype, integrate the sensing, local computing and communication layers, and test the system under real-world conditions. Eventually, I want CUBE to become a reliable decision-support infrastructure for governments, institutions and field teams, helping them understand situations better and identify what needs attention before it becomes too late.
Built With
- artificial-intelligence
- autonomous-systems
- c++
- data-processing
- decision-support-systems
- deeptech
- defence-technology
- disaster-management
- distributed-systems
- edge-computing
- electronics
- embedded-systems
- hardware
- infrastructure
- iot
- long-range-communication
- public-safety
- real-time-systems
- remote-monitoring
- robotics
- ros-2
- sensing-technology
- sensor-networks
- situational-awareness
- systems-engineering