Inspiration As quantum computing scales, a massive cybersecurity threat is emerging: corporate espionage. Financial institutions and defense contractors cannot simply send unencrypted, proprietary quantum algorithms over the open internet to cloud compilers. They need secure infrastructure. We realized the Bitcamp Computational Track wasn't just a math problem—it was a data transmission problem. So, we built QBridge to bridge the gap between complex SWAP routing and enterprise-grade security.
What it does QBridge is a dual-layer Enterprise Quantum Compiler.
The Security Layer: We pull True Quantum Randomness (vacuum fluctuations from the ANU Quantum Numbers API) to generate AES-GCM encryption keys. This creates an impenetrable tunnel for our clients.
The Compiler Layer: We built a custom Python SDK that developers can install to easily communicate with our FastAPI backend. When a developer runs client.optimize_circuit(), QBridge encrypts the logical circuit, sends it to the server, runs our SWAP routing and qubit placement algorithms to map to the hardware topology, and returns the optimized, routed circuit back to the client.
How we built it We completely abandoned the idea of building a traditional web UI and focused entirely on backend infrastructure. We built the routing logic using Python and integrated it directly into a high-performance FastAPI server. To make it usable for developers, we engineered a native Python SDK (qbridge_sdk) that handles the payload packaging, encryption, and HTTP POST requests automatically.
Challenges we ran into Our biggest challenge was a massive late-night pivot. Halfway through the hackathon, we realized our initial web-app architecture (AxesQ) wasn't the right fit for the Computational Track. We had to freeze our frontend, completely restructure our routing algorithm to fit a REST API model, and ensure the decryption payload exactly matched the compiler's expected inputs without crashing the server.
Accomplishments that we're proud of We are incredibly proud of the fact that we didn't just write a local math script. We built a deployable product. Seeing our native Python SDK successfully ingest, encrypt, transmit, and route all 6 of the hackathon's benchmark programs in real-time through our local server was a massive win.
What we learned We learned that in quantum computing, the infrastructure is just as important as the physics. An optimized algorithm is useless if it can't be securely transmitted and executed on the cloud.
What's next for QBridge Because we built QBridge as a modular API infrastructure, the future is incredibly flexible. Right now, our server uses a baseline heuristic for SWAP routing. Tomorrow, we could easily hot-swap that backend logic for an advanced AI-driven routing model or SABRE, and our end-users wouldn't have to change a single line of their SDK code.
Log in or sign up for Devpost to join the conversation.