About us

About Aerokasix

Aerokasix builds operations and maintenance software for wind energy teams, so that the knowledge gained on a turbine does not leave with the person who was there.

What Aerokasix does

Aerokasix is a web platform for running the day to day operations and maintenance of a wind farm. It keeps one connected record of the fleet, from the wind farm down through turbines, systems and components, and of the work performed on them. Faults and field observations are captured as incidents or operational notifications, turned into work orders, and executed as maintenance sessions that move through safety, diagnosis, repair, verification and reporting.

Around that workflow the platform holds the practical information a maintenance team needs to act: alarm codes and troubleshooting knowledge tied to the right turbine technology, spare parts and stock levels, technician qualifications and certificate expiry, and the reliability history that shows which components keep failing. A daily plan view brings the faulted turbines, the warnings and the scheduled work into one priority order, and an AI Copilot helps a technician read the available evidence during diagnosis. The AI is an assistant: approved procedures, manufacturer requirements and authorised personnel still govern safety-critical work.

Who Aerokasix is for

Aerokasix is made for the people responsible for keeping turbines producing, whether they run a single site or a portfolio of wind farms.

  • Wind farm owners and operators who need one reliable record of their fleet
  • O&M service providers running maintenance across several customer sites
  • Maintenance managers and supervisors planning the working day
  • Field technicians who need the right procedure, part and history on site
  • Reliability and performance engineers reviewing what keeps failing and why

How we work and who builds it

Aerokasix is designed and built in house by our own product and engineering team, in close contact with the wind maintenance practice the software is meant to support. We build for the working day of an O&M team rather than for a dashboard: the platform is only useful if a supervisor can plan the work, a technician can execute it on site, and an engineer can later understand what happened and why.

That view shapes the principles we build against:

  • Engineering records stay with the asset, not in a technician’s notebook
  • AI assists the technician and never replaces engineering responsibility
  • Every maintenance session is traceable from safety check to verified repair
  • Qualifications and certification are checked before work is assigned