The Technology
Compute hardware for high-performance workloads
What It Is
The Photonic Accelerator Unit (PAU) uses photons to perform computations. The shift in compute substrate — from electrons in silicon to light — sidesteps the thermal, power, and supply-chain constraints that conventional accelerators are now hitting.
Why It Matters
Compute-intensive workloads are now bound by physics. Power and heat are no longer engineering details — they dominate the economics of large-scale compute deployments.
A photonic substrate addresses these constraints at the foundation, rather than as an optimisation layered on top of an electronic system.
Design Principles
Compute happens in the photonic domain. The substrate is engineered for the operating regime PAU requires.
PAU is a general-purpose photonic compute platform. Use cases span AI inference, scientific compute, signal processing, and other workloads where the limits of silicon hardware are the bottleneck.
The fabrication path sits outside the leading-node silicon foundry bottleneck. All components are sourced from suppliers in the United States and Europe. No critical component depends on Asian suppliers.
The architecture is the subject of a US provisional patent filed at the USPTO in April 2026 (sole inventor). A continuation-in-part covering an extended embodiment is also in the priority chain. Conversion to non-provisional within the statutory twelve-month window is planned, in coordination with patent counsel.
Validation
Software simulation has validated the PAU architecture end-to-end against analytical reference. Every target operation resolves within tolerance. The simulation is reproducible from first principles in publicly available tooling.
The next milestone is a tabletop prototype that demonstrates the architecture in hardware. Further technical detail is available under NDA after a deployment-partnership conversation is in place.
The Precision Question
The conventional criticism of photonic compute — that it cannot match the numerical precision of digital silicon on demanding inference workloads — applies specifically to continuous-amplitude analog photonic architectures, where the achievable precision is bounded by the analog noise floor of the substrate.
Our architectural approach addresses inference accuracy not through analog-precision improvement, but through compositional mechanisms at the representation and algorithm layers. Software validation of the resulting system reaches floating-point parity within seed-noise on a representative inference workload at the canonical configuration. A future bench prototype build will validate the substrate-level claims directly.
The specific architectural mechanisms by which the system recovers effective accuracy are the subject of the pending US patent and the planned non-provisional conversion.
What the Simulation Shows
The architectural claims on this page are derived from a 2026 software validation campaign that simulates the substrate physics, the per-element arithmetic, and the full inference pipeline on representative workloads. The simulation reaches floating-point parity within seed-noise on the canonical inference workload when the full compositional architecture is engaged.
Software simulation projects an approximate halving of elementary operations per inference at matched precision against the conventional arithmetic baseline. One PAU delivers roughly 13× the per-device request throughput of a current top-tier GPU on language workloads. The advantage is the same on chat and on code generation: both workloads scale the work proportionally on PAU and GPU, so the ratio between them stays constant in this simulation.
Every quantitative claim above is backed by an open software test suite that reproduces the underlying numbers in approximately two seconds on a laptop. A future bench prototype build will validate the substrate-level claims directly.
Performance Projection
Simulation projections against a 1000-user mixed AI workload — LLM chat, code generation, image generation, video generation, and research-document workflows — comparing a PAU deployment to a conventional inference-GPU cluster sized to serve the same load.
Projected p95 latency per workload to serve 1000 concurrent users. Simulated projection from the documented substrate and workload assumptions; cluster sized to keep device utilisation at or below 60%.
Per-device request throughput on language workloads. The per-device advantage is approximately 13× on both LLM chat and code generation; in this simulation the ratio is workload-invariant because the workload's compute-per-request cancels in numerator and denominator. Simulated projection from the same substrate assumptions as the latency chart above.
Economics
The throughput advantage translates directly into lower wall power and lower operating energy cost for the same workload.
The numbers below are modelled projections derived from substrate-component datasheets and the per-element arithmetic counts of the simulated architecture. A future bench prototype build will measure the per-multiply-accumulate energy directly. Modelled projections are reported with their assumptions stated, against NVIDIA H100 FP8 at the published 2.8 pJ per multiply-accumulate as the conventional baseline.
Cluster totals to serve 1000 mixed-workload users — total wall power consumed by the deployed cluster, and annual operating energy cost at a $0.10/kWh blended rate. PAU draws approximately 9.6× less wall power and incurs approximately 9.6× lower annual energy cost than the GPU equivalent. Simulated projection from the same assumptions as the charts above.
Deployment Model
PAU is designed to be deployed alongside existing inference infrastructure, not in place of it. First-generation units operate as drop-in additions to existing racks, extending inference capacity without requiring write-off of previously procured equipment.
Subsequent generations follow a phased upgrade path: as new compute capacity is added, photonic units progressively displace traditional equipment until the site reaches a fully photonic configuration. Operators who adopt early are positioned to make that transition incrementally, rather than as a capital-write-off event.