Learn AI.
Know where to start.

Start with a general introduction rather than a tool tutorial. Elements of AI from the University of Helsinki builds conceptual understanding with no technical background assumed, and Google AI Essentials covers practical use at work in under ten hours. Either one is enough to make the rest of this directory navigable.

Use the role section. Pick the role closest to your work and you get why AI matters there, what to learn first, the topics that apply, and a short list of external resources — rather than a general course that spends half its time on material irrelevant to you.

No — not for the majority of what is listed here. AI literacy, prompting, responsible use and applying AI to everyday work require no code at all. Programming becomes necessary only when you move into the Build route: models through an API, retrieval, agents and evaluation.

AI literacy is understanding what these systems do, where they fail and how to use them responsibly — the skill of judging output. AI engineering is building software on top of models: integrating them, grounding them in your own data, giving them tools, and measuring whether the result is good enough to ship. Most people need the first. Fewer need the second.

That is decided by your professional body, not by us, so the explorer reports only what the provider publishes. The CPE filter separates resources whose provider states that they carry continuing-education credit, resources that award nothing at all and so cannot be evidenced, and — the largest group — resources where the provider is silent. Alongside it, the Assessment filter shows whether a credential is earned by passing an exam or by completing the material, and the Issue date filter shows how recently the provider published the offering, which is what most reporting periods actually turn on. Where a provider publishes no credit claim we say so rather than assert eligibility on its behalf; take the provider's own page to your body if you need a ruling.

A substantial part of the catalogue. Use the Cost filter in the resource explorer and select Free to see them. We mark a resource free only where the provider publishes it at no cost; anything we could not confirm is shown as "See provider" rather than guessed at.

Both. Around half the catalogue is published free by the provider, and the rest includes paid certifications earned by examination — cloud and AI credentials from AWS, Microsoft and Google Cloud, audit and governance credentials from ISACA and the IAPP, and paid university and professional programmes. Use the Cost filter to separate them, and the Assessment filter if you specifically want something examined rather than awarded on completion. We never state a price: fees change, and the provider's own page is the only reliable place to read one.

Check who publishes it and go to their own site. Every link here points at the provider's official destination, never a mirror or a reseller, and the provider is named on every card. Beyond that: prefer material that states its level and prerequisites honestly, and be sceptical of anything promising expertise in a weekend.

Each entry carries the date Nakoda last reviewed it, shown on the resource card. Providers restructure their catalogues often, so if you find a link that has moved or a description that no longer matches, tell us and we will correct it.

No. Nakoda does not create, teach, host or accredit any of the learning listed here. Every course, programme, tutorial and credential belongs to the organisation that publishes it, and enrolment, payment, support and certification all happen with that organisation. Nakoda's work is discovery: finding what exists, describing it accurately and helping you get to the right one quickly.

Yes — separately from this directory. Everything above is curated from other organisations' public courses; this question is about the one thing on the page that Nakoda does teach. Nakoda's own Learning and Development practice runs live training directly for boards, teams and departments, built around your organisation's own tools and use cases rather than a generic deck. See the "For teams" section on this page, or get in touch to talk through what your organisation needs.