The questions that surface first on a real integration call — answered straight, without the marketing varnish. Different rooms ask different questions. Pick yours.
Engineers ask one thing. Procurement asks another. Defence asks a third. Investors ask a fourth.
Use the tabs below to jump to the questions that fit your role. Most answers are short — the depth lives in the integration conversation, not on a public page. If your question isn't here, the contact options at the bottom go to the right person directly.
The engineering questions that come up before, during and after a Dev Kit lands on the bench. The deeper certifications matrix and integration playbook are released to qualifying briefs after review.
Pogo pins look cheaper on a spreadsheet. They don't stay cheap. Two metal contacts rubbing every cycle, multiple times a day, for ten years — they pit, they corrode, they drift out of tolerance. They're exposed to whatever the platform meets in the field. They cap power, with no electric vehicle in production using them above a few hundred watts.
Designing a sealed pogo dock from scratch is a multi-month engineering programme on its own. NOA drops in from day one and removes the contact entirely.
Battery swap turns every charge into a labour event. Each swap needs a certified technician, months of training to handle a hazardous load, and pays at the loaded rate. Each swap is also a chance for human error — a wrong-way connector, a short, a dropped cell.
Wireless removes the technician, the certification overhead and the failure mode in one move. The platform lands on the dock the same way every time, day or night, with no operator in the loop.
A Dev Kit gets to a working bench setup in days, not quarters. Most engineering teams have it powering the receiver and tuning the configurator in their first session.
Total integration time scales with how custom the dock and enclosure are — that part is yours to design. NOA's electronics, the configurator, the protections and the firmware are ready out of the box.
Usually not. Depending on platform maturity, integration touches mounting points, the power-path connection to the BMS, dock geometry alignment, and a few firmware hooks.
The goal is adaptation, not redesign — and the help to do it comes from NOA's engineering team alongside yours, not a downloadable SDK.
The resonant inductive design is engineered against CISPR / FCC Part 15 emissions limits and is characterised before it ships to a Dev Kit programme. Final certification belongs to the integrated platform — the rating depends on your housing, your shielding, your antenna placement.
Jurisdiction-specific testing (CE, FCC, MIL-STD) is matched to the deployment context during the integration conversation.
The Dev Kit ships in the 5–20 mm band; the wider platform range scales up to 30 mm with coil and integration choices. Lateral and angular tolerance is high — the design is forgiving enough for battered landings, dock mechanical drift, and real-world vibration. That's the whole point. Efficiency stays close to peak inside the design envelope and degrades gracefully outside it.
Coil selection during integration narrows the envelope to the platform's specific dock geometry. The interchangeable coil set is what makes the same electronics fit a wearable and a marine ROV without re-spinning the board.
Up to 93% efficiency means almost nothing converts to heat. Modules run at 28 °C under continuous full load — dense-packable and quiet on thermal sensors. Competing wireless systems run at 80–90 °C and need active cooling. NOA's low thermal output gives platform integrators flexibility on production cooling — passive heat sinks, vented enclosures, or fans, depending on the cavity and the application. Dev kits ship with bench fans so engineers can push to the upper edge of the spec safely; production cooling is a platform-design decision.
That heat budget is the difference between sealing the enclosure and venting it.
Foreign-object detection (FOD), over-current protection (OCP) and over-voltage protection (OVP) are built into the module. They cut power in under 2 ms when triggered.
The detection profile is tuned during integration against the platform's own materials — chassis, mounts, payload — so legitimate metal in the airframe doesn't read as a foreign object. False-trip behaviour is part of bench tuning before any deployment, not a post-hoc surprise.
The module integrates with smart BMS designs from 1-cell to 9-cell packs. Switchable regulator modes — battery charge, constant voltage, constant current — are configured from the web-based NOA Configurator over USB-C.
For engineers who want raw rectified output to feed their own regulator, a single solder jumper drops NOA's onboard regulation out of the path.
Below 0.5 W. That's the figure that matters when a drone is parked on the pad or a robot is idle between sorties — the quiescent budget that decides how long a fleet can wait between charge cycles without bleeding the cell.
No. The module fails gracefully. Loss of coupling, FOD, OCP, OVP and thermal events all cut power cleanly without back-feeding the cell or stranding it in a half-charged state.
The next valid landing on the pad re-establishes the link and restarts charging in under two seconds.
That's deliberate. The 1 W to 500 W power family runs on one architecture — same protections, same configurator, same firmware approach. The 100 W Dev Kit is the lower bound. The 250 W Dev Kit is also shipping now. The 500 W class is the upper bound of the standard product family; above that, NOA engages on a project / partnership basis.
Integration work done once carries forward through the family. See the power family roadmap on the Technology page.
NOA is the source for its modules — there is no licensed second manufacturer of the IP, by design. What's portable is the integration architecture you build around it: your dock, your enclosure, your BMS hooks. Those don't change if the module class steps up (100 W → 250 W → 500 W) or if a future generation of the architecture lands.
The dependency is on a power family, not a single SKU.
Yes — for retrofits. If the chassis is locked and you're adding wireless to an existing platform, NOA can sit alongside pogo pins as a redundancy path.
New designs typically drop the pins entirely once integration is proven. The extra grams, the extra BOM line, and the failure mode you've now built in stop being worth it.
Most wireless power vendors target either extreme power (EV-class kilowatts) or extreme distance (over-the-air). Both impose cost and integration burdens that don't suit autonomous robotics or drones.
NOA is engineered for the platforms running the field — tight spaces, weight budgets that move grams, mixed environments where one design ships into rain and one into dust, a cool-running architecture that gives integrators real choice on cooling, certification owned by your team. Gen-1 wireless power technologies own extreme power. Legacy wireless power systems own extreme distance. NOA owns deployable.
The qualifier on the Request a Dev Kit page is the brief. Five minutes, five fields. We seed kits to engineering teams working on platforms that fit the technology — not to research-stage projects without a clear path to integration.
Either it's a fit and you get a kit, or we say so honestly.
Submit a brief. Qualifying engineering teams get a kit and the integration playbook.
What a procurement function needs before a purchase order. Specifics on volume terms, warranty and lead time are confirmed in the commercial conversation, not on a public page.
Designed in Australia. Engineered in Sydney, with operations across two spaces: Cicada Innovations — Australia's deeptech incubator at Eveleigh, NSW — where the team works alongside the country's largest deep-tech community, and NOA's R&D and engineering facility in North Sydney, where the day-to-day build happens. Manufacturing capability is being scaled under the current raise.
The supply chain for critical components is Australian-sourced by deliberate decision, not retrofit. See the Sovereignty section of the About page for the full pillars.
Lead times are confirmed in the commercial conversation, scoped against production volume, jurisdiction and the integration class.
Pre-production engineering samples and Dev Kits ship inside the qualifying brief workflow on the Contact page. Volume-production lead times scale with the manufacturing capability being established under the current raise.
NOA is the source for NOA modules. There is no licensed second manufacturer of the IP.
What is offered instead is a power family — 1 W to 500 W on one architecture — so a single integration carries forward across modules and across roadmap generations. The dependency is on a class of product, not a specific SKU.
NOA owns the wireless power IP — the receiver and transmitter electronics, the firmware, the configurator. The integrator owns the platform — the dock, the enclosure, the host firmware, and the certifications on the integrated product.
The boundary is deliberate and is documented in the integration agreement.
Module-level compliance posture is engineered against CISPR / FCC Part 15 emissions limits and standard industrial safety practice.
Final-product certification (CE, FCC, MIL-STD, jurisdiction-specific) is matched to the deployment during the integration conversation, and is the integrator's responsibility on the final platform. The certifications matrix relevant to a specific platform is shared with qualifying briefs.
Commercial terms are scoped in the integration conversation. Dev Kits are seeded to qualifying briefs without a price tag — the kit is gifted, not sold.
Production supply, OEM partnerships, regional licensing and exclusive vertical agreements are all available structures, depending on volume and jurisdiction.
Volume economics are part of the commercial conversation, not the public page. The number that matters in a procurement model is total cost of ownership across the fleet life, not the unit BOM line.
NOA's reference deployment delivered an estimated $214K equipment saving on a single 20-hectare site by reducing the airframe count from 18 to 6 — see the case study on the About page.
Warranty terms sit inside the production supply agreement, scoped to volume, deployment context and jurisdiction. Specifics are set in the commercial conversation, not on the website.
The supply chain is sovereign by design. Critical components are Australian-sourced by deliberate decision, not retrofit. Traceability is maintained from component intake at NOA's R&D and engineering facility in North Sydney through to module-level test data.
For procurement contexts where origin matters — defence, coalition assets, critical infrastructure — that's the whole point of the architecture.
Commercial terms, lead times and volume agreements are scoped one-to-one.
The questions a defence integration team or government procurement officer asks first. Programme-specific compatibility and classified-handling pathways are scoped one-to-one, not on a public page.
Yes, by design. The capability is engineered to fit AUKUS Pillar 2 sourcing requirements from day one — Australian-designed IP, Australian-engineered, Australian-manufactured, with Australian-sourced critical components.
There's no retrofitted compliance documentation to assemble after the fact. See the Sovereignty section of the About page.
NOA is Australian-designed and Australian-manufactured. The IP, the electronics and the firmware are Australian. NOA does not import controlled US technology into the chain.
ITAR posture for a specific platform depends on what the integrator builds around the module — if the host platform carries ITAR-controlled tech, the integration does. Per-platform assessment happens during the integration conversation.
The Australian Defence and Strategic Goods List (DSGL) controls apply where relevant — assessed per platform and per export jurisdiction. The assessment runs during the integration conversation against the deployment context and the destination, not as a generic posture statement.
Classified-handling pathways are jurisdiction-specific and are scoped during the integration conversation. NOA's engineering work is centralised at Cicada Innovations under standard industry security practice.
Classified-environment integrations are managed under the cleared partner of record for that programme.
Hardening is a platform-level integration question, not a module-level one. NOA's onboard protections (FOD, OCP, OVP) handle the module's own failure modes.
EMP and lightning hardening on the integrated platform is part of the integrator's enclosure, shielding and grounding design — and is scoped during integration support against the target environment.
The module is designed for industrial environments — vibration, dust, washdown, temperature swings — within the published power, gap and protection envelope.
The IP rating, the shock spec and the environmental sealing on the integrated platform belong to the integrator's enclosure design. NOA's contactless architecture is what makes that sealed enclosure possible in the first place — there are no exposed conductors to seal around.
Compatible with autonomous platforms across air, ground and maritime domains by design. The 1 W to 500 W power family covers most relevant duty cycles — from sensor-class wearables to heavy ground vehicles and marine ROVs.
Specific programme compatibility is scoped during the integration conversation against the platform's power envelope, form factor, dock geometry and jurisdiction certifications.
The current manufacturing footprint is Australian. Sovereign manufacturing pathways for AUKUS partner jurisdictions are part of the strategic roadmap and are explored on a case-by-case basis with cleared partners — not a generic offer on a public page.
The Contact page qualifier handles initial brief submission with a Defence / government role option. Briefs from cleared programmes are routed for direct conversation rather than through the standard engineering pack workflow.
Programme briefs are routed for direct conversation. The Contact qualifier is the entry point — flag the role correctly.
The questions an investor analyst asks before a meeting. Funding history and the current round are in the investor materials, not on the public page — request them through the contact below.
NOA designs and manufactures contactless wireless power infrastructure for autonomous platforms — drones, robots and mobile assets in defence, mining, agriculture, marine and industrial environments. The technology removes physical charging contacts (pogo pins, plugs, manual swaps) entirely, replacing them with sealed inductive power transfer across an air gap of up to 30 mm. Australian-engineered, sovereign supply chain, designed for AUKUS Pillar 2 sourcing.
100 W Dev Kits are shipping to qualifying engineering teams (replacing the prior 50 W kit), with the 250 W Dev Kit also orderable today. NOA's R&D and engineering facility in North Sydney is the day-to-day build space; manufacturing capability is being scaled under the current raise.
The 100 W kit is the lower bound of the platform; the 250 W class is shipping now; the 500 W class is the upper bound of the standard product family. Above 500 W, NOA engages on a project / partnership basis. See the power family on the Technology page.
Three layers. The first is technical — a single architecture from 1 W to 500 W with the protections, the configurator and the firmware shared across the family, which is how the integration scales without redesign.
The second is the usability wedge — Gen-1 wireless power technologies own extreme power, Legacy wireless power systems own extreme distance, NOA owns deployable. The third is sovereign supply — Australian-designed, Australian-manufactured, Australian-sourced critical components from day one, which is structurally hard to retrofit.
Every fleet of autonomous platforms that currently charges through pogo pins, manual swap or plug-and-cable. That spans warehouse robotics (AMRs), drone fleets (commercial and defence), mining and inspection robots, marine ROVs, agricultural automation, wearable sensors, and defence platforms across air, ground and maritime domains.
Yes. The reference deployment block on the About page details an Australian drone-as-a-service operator running autonomous bird-deterrence flights. The fleet was reduced from 18 drones to 6 across the same 20-hectare plot, with charging running autonomously between sorties.
Other deployments are under NDA and are discussed in private conversations.
The company origins and team are covered on the About page — including the decade-plus technology lineage in portable power, the Startmate '24 cohort selection, and NOA's stated position as the picks-and-shovels infrastructure layer for autonomous platforms across commercial, industrial and defence applications.
Australian wireless power IP, with the architecture's specifics covered in NDA-only conversations.
The defensible position is the system — the four-layer architecture (scalable power transfer, smart BMS integration, adaptive intelligence, full control plus telemetry) running coherently from 1 W to 500 W on the same workflow. Imitating one layer is straightforward; imitating the integrated stack at the same usability is the work.
Funding history and the current round are in the investor materials, not on the public website. The Executive Summary is shared with qualified investor enquiries — request it through the contact below.
The wireless-power category has consolidated through partial M&A and public-market exposure. NOA's strategic value sits in the autonomous-fleet picks-and-shovels position.
Adjacent buyers are the platform OEMs, the infrastructure aggregators, and the defence primes building the fleets running the field. Deeper analysis is part of the investor conversation, not a website summary.
Email enquiries@noawireless.com and flag the message as an investor enquiry. Direct conversations are scoped from there.
The Executive Summary and the current round are shared with qualified enquiries — direct, not through the website.