Five engineers on a team, all setting up CI the same way from memory, is five different pipelines by the end of the quarter. The implementation products fix that for one engineer at a time. This is a proposal for fixing it for a team in one purchase — and, more usefully, for giving the person who has to roll it out something better than “here are some files”.
The problem it is meant to solve
Section titled “The problem it is meant to solve”You are a lead or a manager. Your team keeps re-deriving the same decisions: what CODEOWNERS
should say, which ruleset options to enable, what the workflow’s permissions block needs, how the
release gate should work. Each engineer solves it slightly differently, and the differences surface
during an incident.
Buying one copy each solves the licensing question and none of the rollout question. The Team Pack is the two products plus the two things a team actually needs: a sequence for adopting them and a map from each file to the lesson that explains it, so the reasoning is reviewable rather than inherited.
What is in it
Section titled “What is in it”Every line below is a file that exists today in this repository — nothing here is promised future content.
Team adoption guide — a four-week sequence (one repository, then make it fit, then security in the order that matters, then a second repository and a handover), a team-level customization checklist, and a rollout record to keep. A preview is below.
File-to-lesson map — every file in both products linked to the free lesson that explains the reasoning behind it, so a reviewer can check a template rather than trust it, and a new engineer can be sent to the explanation.
A licence for a named number of engineers, with reassignment when people leave.
Individual versus team
Section titled “Individual versus team”At today’s prices — $9.99 for the Vault and $19.99 for the Toolkit, unchanged by this proposal — both products cost $29.98 per engineer.
| Individual purchases | Proposed Team Pack | |
|---|---|---|
| 5 engineers, both products | $149.90 | $99 |
| 15 engineers, both products | $449.70 | $249 |
| Licensed to | each engineer personally | the organisation, seats reassignable |
| Adoption guide and file-to-lesson map | — | included |
| Purchases to manage | one per engineer | one |
A real preview of the adoption guide
Section titled “A real preview of the adoption guide”This is the opening of week 1, verbatim from ADOPTION-GUIDE.md in the pack:
Week 1 — One repository, the minimum. Goal: one pull request that runs CI and is reviewed by the right people.
- Set the token default to read-only before any workflow runs. Repository → Settings → Actions → General → Workflow permissions → Read repository contents and packages permissions. Every Vault workflow assumes this.
- Copy one CI workflow — the one for your language, not all five. Work through every
# CUSTOMIZEmarker.- Open a pull request on a branch where nothing can publish or deploy. The first run is the integration test. Expect it to fail once on something environmental; that is the point of doing it on a branch.
- Add
CODEOWNERS. Read the comment about catch-all ordering before you write your paths — a*line above a specific one silently disables it.- Add the pull request template. Cut any section your team will not fill in honestly. A template nobody completes teaches people to ignore templates.
Stop here for a week. Let the team use it. Collect the complaints — they are the customization list for week 2.
Three decisions come before week 1 (which repository, who owns the result, what “done” means), and weeks 2 to 4 cover requiring checks, the security order, and the handover. The free labs are referenced throughout, because every engineer on the team can use them without a licence.
Licence scope, in short
Section titled “Licence scope, in short”The full draft is being reviewed; this is its shape.
- Licensed to the organisation, for the number of engineers on the receipt.
- Those engineers may use and modify every file in the organisation’s repositories, public or private, and share the files internally.
- Seats are reassignable immediately when someone leaves. Nothing to deactivate.
- Contractors working on your repositories count while engaged.
- No redistribution or resale: not the archive, not the download page, not a competing template product.
- Updates included, published to the same download page.
- Nobody needs this licence to use the files in an employer’s repository — the existing individual licence already permits that, and this proposal does not narrow it.
Six questions in the draft are genuinely unresolved and marked for decision, including how agency work inside a client’s repository should be treated and how long the update window runs. If one of those is your situation, writing is worth more than waiting.
Delivery, updates, support and refunds
Section titled “Delivery, updates, support and refunds”Proposed to work exactly as the individual products do today, because that machinery already exists and is documented:
- Delivery: Stripe takes payment and sends you to a download page that keeps working. No account.
- Updates: published to that same page, included.
- Support: order, licence and download questions by email. Not pipeline debugging, not consulting, not training, and no response-time commitment — none of those is offered.
- Refunds: the published policy is a full refund within 14 days, on request.
Talk to us about it
Section titled “Talk to us about it”Team licensing questions: admin@moderngitacademy.com. Useful to include: how many engineers, whether they already own the products individually, and whether agency or client-repository use applies.
Team Pack — up to 5 engineers
$99 one-time
Both implementation products, licensed for a team of up to five engineers.
- GitHub Actions Production Workflow Vault — 57 files
- Professional Toolkit — 29 files plus its README
- Team adoption guide: a four-week sequence, a customization checklist and a rollout record
- File-to-lesson map: every file linked to the free lesson that explains it
- Named-engineer licence for up to five engineers, with reassignment
- Updates included, at the same download page
Ask about this tier — opens your email client with a subject line; it does not place an order or submit anything.
Team Pack — up to 15 engineers
$249 one-time
The same pack, licensed for a team of up to fifteen engineers.
- Everything in the five-engineer pack
- Named-engineer licence for up to fifteen engineers, with reassignment
Ask about this tier — opens your email client with a subject line; it does not place an order or submit anything.
More than fifteen engineers
By arrangement
A licensing proposal for a larger organisation, agreed in writing.
- Both products, licensed for the engineer count you name
- The adoption guide and file-to-lesson map
- Terms agreed in writing before anything is invoiced
Ask about this tier — opens your email client with a subject line; it does not place an order or submit anything.
Questions about licensing go to admin@moderngitacademy.com. Nothing on this page charges a card.
Frequently asked questions
- Can I buy this today?
- No. The price and the licence terms are proposals awaiting a decision, so there is no checkout. If a team licence is what you need, say so by email — that is the only thing that will move it up the queue, and it is genuinely useful to know.
- My engineers already bought the products individually. Do they need this?
- No, and nothing about this proposal changes their licences. An individual licence already covers use and modification in unlimited personal and employer repositories. A team licence exists to buy that right for several people in one transaction, not to take anything away from people who bought first.
- What is actually in it?
- Both existing products — the Workflow Vault's 57 files and the Professional Toolkit's 29 — plus two things written for teams: an adoption guide with a four-week sequence and a customization checklist, and a map linking every file to the free lesson explaining it. No new templates; the value is the licence and the rollout material.
- How would the engineer count be enforced?
- It would not be, technically. There is no activation, no seat server and nothing that phones home. The count is a licence term, honoured on trust, and seats are reassigned freely when people leave.
- Is this a subscription?
- No. It is proposed as a one-time purchase, like both existing products. Updates would be included at the same download page. Nothing that is included today would be repackaged as a recurring charge.
- What about contractors, subsidiaries and client repositories?
- Contractors working on your repositories are proposed to count as covered engineers while engaged. Agencies adapting the files inside a *client's* repository is the genuinely unresolved case and is flagged for decision — if that is your situation, it is worth writing, because the answer is not settled.
- Does any of this affect the free lessons?
- No. Every lesson, lab, tool and free download stays free, for everyone, licensed or not. Nothing that is free today moves behind any of this.