Alpha-Omega Open Source Security Grant

Alpha-Omega, a Linux Foundation project, funds open source maintainers to improve the security of critical software through its Alpha funding stream. Applications are not open yet. The next submission window runs from 1 January 2027 to 31 January 2027; the October 2026 window has already closed. The official page says grant amounts vary with the proposal but typically range from US$50,000 to US$100,000 (about ₹47.5 lakh to ₹95 lakh).

What the program offers

Alpha-Omega's stated mission is to protect society by improving the security of critical open source software through direct maintainer engagement and expert analysis. The Alpha stream gives money to maintainers, and the money is meant to raise the overall security quality of the project. The official page says amounts depend on the proposal and typically fall between US$50,000 and US$100,000.

The page does not list a fixed set of eligible costs. It does mention that a proposal should say whether you plan to hire staff and how quickly work can start once funding arrives. Beyond money, grantees become a peer group: they join monthly strategy roundtables with other funded projects and take part in community efforts around the grants. The grant agreement is described as light on timelines and fixed outcomes, and future funding depends on meaningful progress.

Who can apply

Standalone open source projects, foundations that look after many projects, and core ecosystem services can apply. Every project must use an OSI-approved open source licence, and your proposal must include proof of it. The official page does not restrict applicants by country, so a maintainer based in India is not excluded by anything stated there, but the page also does not say anything about paying recipients abroad.

This suits maintainers of widely used libraries, tools or infrastructure who can explain why their project is critical and what a funded security effort would change. It does not suit projects without an OSI-approved licence, and requests sent by email or any route other than the official form are not considered.

How to apply

Alpha-Omega runs four seasons a year, each lasting 12 weeks across three months. In month one you fill in a short Grant Submission Form. If your project fits, you receive a Security Consultation Invitation. In month two you are paired with an Alpha-Omega team member to write your formal proposal and Statement of Work together. In month three comes the final decision and funding.

The proposal covers four things: who the recipient is and proof of the licence; why the project is critical, its current security posture and its challenges (without disclosing unpatched or sensitive vulnerabilities); the outcomes you expect, how you will measure success and who benefits; and your plan, including whether you will hire and how fast you can start.

How applications are judged and what happens next

Alpha-Omega first checks that the project fits its security mission. Evaluation then weighs two things: how much security impact the funding will bring to the ecosystem, and how well you collaborate during the month-two co-design work. For the January 2027 season the calendar is: submission 1-31 January, review and co-design in February, decision and funding in March 2027. The later seasons open on 1 April, 1 July and 1 October.

Once funded, grantees publish monthly reports and write blog posts at the start (kickoff and baseline), the middle (challenges and pivots) and the end (final security posture and what comes next).

About Alpha-Omega

Alpha-Omega is a project of the Linux Foundation. Its aim is to improve the security of critical open source software by working directly with maintainers and by analysing the software itself. The Alpha stream is the part that funds maintainers; the website also lists grant recipients, case studies, reports and guidance for grantee blogs.

Things to check before you apply

The official page contains a small timing inconsistency: it says grants are funded the following quarter after application, while its calendar shows decisions and funding within the same three-month season. Plan for the calendar dates but do not be surprised if payment lands a little later, and confirm with the programme.

A practical tip: use the waiting time before January to write down why your project is critical, who depends on it and what security work you would do first, because the co-design month moves quickly. A practical tip for Indian recipients: check with an adviser how a foreign grant is paid to you and taxed before you accept it.