student-offers: a hand-maintained list of free student software and credits

A list, published as a site

The repository is described as a collection of all free student offers and discounts while you are a student, and the primary language of the repository is HTML. That is the whole architecture: there is no application, no database server and no build pipeline in the traditional sense.

The top level listing shows a .nojekyll file, a CNAME file, an Assets directory, a Database directory, an index.html, a README.md, a LICENSE, a CODE_OF_CONDUCT.md and a CONTRIBUTING.md, plus a directory called instructions and a .github directory. The CNAME and the .nojekyll marker are the two files that say this is a GitHub Pages site, published directly from the repository rather than through a site generator. The live site is at student-offers.ml, which is the homepage recorded for the project.

The separation between the Database directory and the rendered page is the one structural decision worth understanding. The offers live as data, and the page and the README are generated from or around that data, which is why the README contains a table with three columns, Product, Offer Benefits and Type, and why it is wrapped in a marker comment. The instructions directory presumably tells contributors how to add an entry, and the contribution guide and code of conduct sit alongside it.

So the project is a database with a front end and an open contribution flow, which is a fair description of what it is: a shared reference list, not a service.

The licence is MIT, the default branch is main, the repository is not archived, and the last push was on 2026-08-25. There are no GitHub releases, which is what you would expect from a site that deploys itself on every push.

What is actually on the list

The table is the product, so it is worth looking at what is in it rather than how it is stored.

The entries are organised by type, and the type column is where the list becomes useful as a search space. The categories include Cloud, Domains, Learn, Development, Design, Productivity, Infrastructure and APIs, Tools, Video Conferencing App, Social Media Links Manager, Survey creation and distribution app, 3D Rendering, 3D Work, Cross Platform development, Internet of Things and Infrastructure, and Developing and Learn. That last one, Developing and Learn, is a hint that the data model is a free-text category field rather than a controlled vocabulary, which is fine for a list and is also the thing that makes searching it slightly awkward.

The entries themselves are mostly obtained through the GitHub student developer pack. The first row of the table is that pack, with the benefit described as 200K worth of free software for all your development needs, and several rows link to the vendor's github-students URL, which is the giveaway that the same pack is the entry point. The GitHub education benefits page, the GitHub pro package and GitHub Campus Experts are separate rows, and the GitHub student developer pack appears again through a .tech domain row.

The non-GitHub entries are the interesting ones for a reader who already has the pack. AWS Educate with a starter account worth 100 dollars, Microsoft Azure with 25+ cloud services and 100 dollars in Azure credit, MongoDB with 200 dollars of credit plus courses and certification, Digital Ocean with 50 dollars of credit, Twilio with 50 dollars of credit plus APIs, Heroku on a hobby dyno, and Mailgun with 12 months of subscription and 20,000 free emails.

The rest are mostly time-limited subscriptions or education licences: Jetbrains, Jetbrains-adjacent tools like GitKraken, Unity, Prezi, LucidChart, Notion Pro described as for lifetime for students, AnyDesk, Spotify at a student discount, DataCamp, Educative, Frontend Masters, Interview Cake, One Month, and the rest of the table continues in the same shape. The practical way to use it is what the README suggests, with CTRL or Command + F to find anything.

The README is also a storefront

One structural feature deserves a mention, because it shapes the repository rather than the list.

Above the offers table, the README carries a section titled Website and Autofill Extension, promoting Zapply: a Chrome extension that autofills job applications in seconds, a dedicated job board, user accounts with multiple profiles for different resume types and roles, and job application tracking with streaks and commitment awards. There is a large call to action button image, an onboarding link, and a line marking it as sponsored by Zapply.

The project also carries a banner image for the same service at the top of the README.

This is worth naming plainly rather than treating as a detail. A repository whose entire value is a list of free benefits for students now spends the most valuable screen real estate above that list advertising a job application tool. For a reader it is a small intrusion; for a contributor it is a question about where the line sits, since a sponsored section in the README of a community list can crowd out the list itself over time, and every future addition has to decide whether it goes under the sponsor banner or above it.

The topic list carries the fingerprints of how the project grew: hacktoberfest and hacktoberfest-accepted and hacktoberfest2021 and hacktoberfest2022, alongside collaborate, educational, free-software, github, github-pages, student-offers, student-vscode and students. A project that was shaped by seasonal contribution events accumulates a lot of additions quickly, which is the context in which the entries below should be read.

There is a separate banner for Zapply at the top of the page, and the README also refers to a Website and Autofill Extension as if it were part of the project's own offering, which is the part that could confuse a first-time visitor about what this repository actually is.

Why the list ages badly

A hand-maintained list of offers has a structural problem, and this one has it in a mild form.

The first problem is expiry. Most rows describe a duration, and the durations are short. Last Pass is 6 months, eSurveyCreator is a student licence while you are a student, DataCamp is 3 months, Interview Cake is 3 weeks, One Month is 30 days, and Mailgun is 12 months. A row that was accurate when it was written becomes wrong by quietly expiring, and nothing in the repository records when a row was last verified.

The second is that the offer behind a row can change without the link changing. A vendor can rename a plan, tighten its eligibility rules, or pull a programme out of the student pack while keeping the page, and the row still reads the same.

The third is the wording. Notion Pro is described as for lifetime for students, LucidChart as lifetime free subscription, and several others as lifetime. Those are strong claims, and they are the kind of phrase that is copied from a marketing page rather than confirmed against terms. Whether a student licence is genuinely perpetual, or simply persists while the student account is verified, is exactly the distinction a reader cannot resolve from a table row.

There is also a data quality artefact visible in the table itself. The Enscape row carries an extra empty cell after its type, which suggests rows are maintained by hand and appended without a schema check. That is not a criticism of the project so much as a description of what a volunteer-maintained list is, and it is the reason the table needs the search-the-page habit that the README suggests.

None of this is unusual for this kind of project, and the fix is the same one the project already invites: check the vendor page, and open a pull request when a row is wrong.

Contributing, and what the project asks of you

The repository invites contributions, and the mechanics are visible in the file list and the topic tags.

There is a CONTRIBUTING.md and a CODE_OF_CONDUCT.md at the top level, a .github directory for the workflows and templates, and an instructions directory that sits alongside the Database directory and the rendered page. The data and the instructions are kept next to each other, which is the arrangement that makes the list easy to extend: you edit the data, follow the instructions, and open a pull request.

The topic tags tell you what kind of contribution was happening. Hacktoberfest, hacktoberfest-accepted, hacktoberfest2021 and hacktoberfest2022 are all present, which is the signature of a project that was substantially built through seasonal contribution events. The collaborate tag is there too, and the README carries badges for pull requests being welcome and contributors being welcome.

That combination has a consequence worth naming. Contribution events produce a large, one-time influx of additions, often from people who have just signed up to a platform and are completing a task rather than maintaining a record. A list built that way will have breadth and uneven quality, and the entries that survive are the ones a later contributor happens to correct.

So the useful roles are split. The first-time visitor wants the list. The returning contributor wants a way to submit a row without breaking the rendering, which is what the instructions directory and the Database directory are for. And the project needs people who check rows, because that is the only mechanism that keeps the durations honest.

On maintenance, the last push was on 2026-08-25, roughly two months before this review, and the repository is not archived. The licence is MIT, so the list and the site can be reused and modified freely with the notice retained. This is not legal advice, and if you are thinking of mirroring the data into your own project, reading the LICENSE file in the repository is the sensible first step.

Editorial conclusion

Use student-offers if you are a student and want one place to check what is currently free for you, and expect to verify each offer on the vendor's own page before you rely on it. Do not treat the list as an entitlement catalogue or a source of truth for pricing, because it is a set of links with no verification step and no expiry tracking, and several entries describe offers that only last a term or a year. Before you rely on an entry, open the vendor link and confirm the terms, and if you find one that has expired, the project takes pull requests, so fixing the row is the useful contribution rather than quietly working around it.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. ShreyamMaity/student-offers on GitHub