Mission
The Copilot Stack helps developers move from basic AI-assisted coding to advanced GitHub Copilot, AI-agent, DevOps, and agentic software-engineering workflows through structured technical education.
Most writing about GitHub Copilot falls into one of two categories: marketing copy that describes what the product is supposed to feel like, or scattered blog posts that answer one narrow question and leave you to assemble the rest. Neither helps a working engineer decide whether to hand a multi-file refactor to an agent, or what to check before merging the result.
This site is organised as a curriculum instead. Lessons are ordered, each assumes the ones before it, and every version-sensitive claim carries the date it was last checked against GitHub's own documentation.
What we publish
- The GitHub Copilot Academy — a structured curriculum of 100 published lessons across all 8 clusters, taken in order.
- Technical references — 10 lookup pages: shortcuts, commands, plan comparisons, model and agent references and feature matrices.
- Labs — 31 hands-on exercises and guided walkthroughs, inside the lessons that support them.
- Articles — comparisons, buying decisions and failure modes: the questions the curriculum does not answer because they are not lessons.
- Tools, research and datasets — browser-local tools built on maintained datasets, research pages markedmeasured or harness according to whether a run has happened, and the datasets themselves with their verification dates. See tools, research and data.
What is paid, and what is not
Everything above is free and stays free. One thing is sold: The Copilot Stack Pro, a maintained implementation library (a subscription, with one resource public in full). It is not a GitHub Copilot subscription, which GitHub sells, and it is not required to use anything else on the site. Payments are processed by Stripe; the site never sees your card details. Accounts are optional and exist only to sync progress and hold purchases. There are no testimonials, customer logos or case studies on this site because there are none to show honestly.
Who writes it
The Copilot Stack Editorial Team — Technical education and developer reference.
The Copilot Stack editorial team researches, writes and reviews the GitHub Copilot Academy curriculum. Every version-sensitive claim is checked against GitHub's primary documentation before publication and re-checked on a fixed review interval, and the checks that can be automated run in the build rather than relying on anyone remembering.
How those claims are checked is set out in the technical testing methodology, including what this site does not test and does not claim.
Areas of focus:
- AI-assisted software development
- GitHub Copilot and AI coding agents
- Developer tooling
- DevOps and platform engineering
- Technical documentation
We do not claim vendor certifications, partnerships or credentials we do not hold. Where a claim on this site depends on authority rather than evidence, treat it with suspicion — and check the primary source we link to instead.
How we work
Our editorial policy sets out how content is researched, how AI is used in the process, what we do and do not verify, and how corrections are handled. It is worth reading before you rely on anything here.
In short: GitHub's primary documentation is the source of record, AI output is never assumed accurate, code examples are labelled honestly about whether they were executed, and we do not publish fabricated screenshots, benchmarks, test results or statistics.
Independence
The Copilot Stack is an independent educational resource and is not affiliated with, sponsored by, or endorsed by GitHub, Inc. or Microsoft Corporation. GitHub, GitHub Copilot, and related names and marks are trademarks of their respective owners.
We have no commercial relationship with GitHub or Microsoft. We are not a certification provider, and completing lessons here does not confer any credential. See the full disclaimer for details.
Contact and corrections
Found something inaccurate or out of date? That is the most useful thing you can tell us. The corrections section of the editorial policy explains how reports are handled and what happens to the page afterwards.