Hub Lite
The dense, low-cost, solar-powered backbone of the mesh. Quietly does its job on a pole.
The work AESTRION was preparing for the years ahead has become work the present demands. We are not naming the events — readers can read a paper. The point is simpler: cities need this network sooner than we planned to deliver it.
The roadmap is sound. The hardware is real. The bottleneck is not technology, judgement, or appetite — it is funded engineering throughput. With capital, we can parallelise work that is currently sequential, hire ahead of the pilot, and bring the first live mesh forward in months.
We are opening a pre-seed window for investors who want to compress this timeline with us. Nothing else about the system or the principles changes. Only the dates — and only if the capital arrives to move them.
Designed so that buses, parking, air sensors and lighting can run on the same mesh, through the same APIs, onto the same municipal dashboard. One integration, citywide — these are examples of what the network is built to carry.
When upstream goes dark, the same hubs become the last working channel — citizen ↔ emergency services, satellite-backed, mesh-relayed, offline-capable.
Smart-city projects today each run on their own connectivity — separate carriers, separate contracts, each silent the moment its upstream link is cut. AESTRION is a network of street-level hubs that gives every project one always-on connection — and stays reachable to citizens when the public internet doesn't.
◆ Hub Lite · pole-mounted, solar-trickle · Hub Main · totem with screen, charging strip, Starlink dish · both run the same firmware and the same Aestrion-Core mesh radio.
In peacetime, the network connects every smart-city project — one shared mesh where sensors, lighting, and civic systems all run. The moment a crisis hits — no power, no internet — the same network is the city's lifeline: dispatch reach, citizen comms, cached information, charging. Same hardware. Same network. No mode switch.
The network is built from a deliberate pair of devices. The two share firmware, mesh role, and operational model — they differ only in form, energy budget, and the additional services a Main Hub can host on the street.
A typical city deploys a small number of Main Hubs at plazas, transit stops, and civic anchors, with a much larger population of Hub Lites along streets, lampposts, and rooftops. Density and reach come from the Lites; internet bridge and citizen-facing services come from the Mains.
The dense, low-cost, solar-powered backbone of the mesh. Quietly does its job on a pole.
A standalone street fixture. Brings satellite internet, a public screen, and charging to the corner — and bridges the mesh to the outside world.
Both devices run the same firmware, sit on the same Aestrion-Core mesh, host the same offline cache, and collect from the same municipal IoT integrations. A city scales by mixing the ratio — not by maintaining two parallel platforms.
Hub Mains sit in the most-trafficked spots — squares, transit nodes, civic gateways — and their public screens carry the council's identity in plain view. Hub Lites handle the rest of the city, paired with mounted info boards on lampposts, plaza edges, and façades. Together they sit there, day in and day out, telling the citizen: this corner is connected, this council has invested, and if anything ever goes wrong, this hardware is on your side.
"Commissioned by the city of ___" — visible to every citizen, every day. The work is attributable. It's a public good with an author.
The mesh is the unified backbone. Add parking, lighting, sensing — they ride this rail. No fragmented vendor stack. No re-platforming.
An everyday utility every citizen uses, paid for once, branded by the city — not an annual procurement line that competes with social budgets.
When the next storm or outage hits, this city is the one whose network stayed on. That story is told once and earned for years.
This city, by act of its council, commits to continuous civic infrastructure for the safety, communication, and care of its citizens — in peacetime and in emergency, on the same hardware, under its own name.
We are currently in the hardware prototyping phase, with validated urban range testing underway in Limassol, Cyprus, targeting live pilot for 2026.
The pilot will deploy a small mesh of Citizen Readiness Hubs across a defined urban perimeter to characterise real-world range, peacetime utility, and failover behaviour when the upstream link is severed under controlled test conditions.
Updates will be posted to this section as milestones are reached. The page is the log.
Satellite, mesh radio, and local cache form three independent paths. The system continues to deliver civic value when any one of them is degraded or absent.
The mesh is a unified backbone for all smart city applications — and grows with every new municipal project layered on top. Continuity is paid for by everyday usefulness; emergency capability is intrinsic, not a separately-budgeted layer.
Data residency, governance, and operational control sit with the host city — not with a remote vendor. AESTRION supplies and manages the network — hardware, firmware, integration, and operations — under the city's authority.
Public-sector services consume open, documented interfaces. Cities can build, contract, or migrate against them without re-platforming.
No exotic silicon. No bespoke radios. The novelty is in the integration, the firmware, and the operational model — not in the bill of materials.
Every claim about the system is anchored to a public test. If a target slips, we will say so, and explain what changed. The page is the log.
Technology proven. Radio link budgets, power profiles, and civic-API surface validated in field tests.
Component integration, urban range characterisation in Limassol, firmware bring-up.
Small mesh deployed across a defined urban perimeter. Public field log updated as milestones land.
Scale beyond Limassol — live AESTRION networks operating across multiple cities. First civic-API consumers integrated; cross-city interoperability tested in production.
Open hardware specification + civic API standard for cross-municipality readiness networks.
Every city deserves a network that works when everything else fails. We are building it.