An organization gets tens of thousands of dollars in cloud credits and celebrates like it won the lottery. A year later, the credits expire unused: there was no project that actually needed them.
A resource with no task isn't a resource. A neighboring organization's story runs the other way: it had a specific data project, and the same kind of credits covered a real expense line it would otherwise have paid for in cash. The same credits turned out useless in one case and valuable in another, and the difference wasn't the credits, it was whether a task existed for them.
Tech grants are a separate continent of the grant world, where what's given isn't so much money as technology resources: cloud, engineering support, sometimes a cash component. Programs like AWS Imagine Grant and Google.org offer serious resources, but in return they ask for a clear technology project and a track record, not just nonprofit status.
Flagship programs give resources for specific projects. AWS Imagine Grant, for example, runs on an annual cycle: applications open in spring, there are several categories for different stages of technology maturity, from basic infrastructure modernization to projects at the cutting edge of artificial intelligence, and winners get a combination of unrestricted money, cloud credits, and expert support.
Simpler programs sit alongside these. AWS separately offers small cloud credits to nearly any verified organization through its credit program, closer to the ongoing benefits from Level I than a competitive grant. And some programs give neither money nor credits, but people: Twilio.org, for instance, works through a community of volunteer developers who help organizations with communication technology.
An important caveat: this list of programs is a living one. They open, close, and change terms and categories from year to year faster than the structural topics from earlier levels of this course. Always check a specific program's current terms on its site before actually applying, don't rely on what was true a year ago.
A flagship tech grant is a full-fledged grant application, not a discount request form. It asks for a clear technology project: not "cloud would come in handy," but "we're building this specific thing, and here's why it matters to our mission." A vague desire for resources just in case almost always loses to a clear project with an understood purpose.
It also asks for a track record of using technology: proof the organization has already done something with data or tools, not that it's taking credits for the first time in its life with no idea what to do with them. And a realistic plan: exactly how the resources turn into a result for the mission. Every application-writing skill from the next module applies directly here, because this is essentially the same grant application, just about technology.
Competitive tech grants strengthen an organization that already has a working program and accumulated data, and are nearly useless to an organization still at the paper stage from the five stages of a nonprofit. The resource comes tied to a task, and a very young organization doesn't yet have a task of that scale.
It's worth clearly separating two things that are easy to mix up. Ongoing nonprofit benefits from Level I, discounted software, basic cloud credits, are available to nearly any verified organization and require no competition. Competitive tech grants from this lesson are separate contests for mature organizations with a finished project. Nearly everyone gets the first, few win the second, and confusing them means either underestimating available benefits or overestimating your odds at a competitive grant.
Below is a table of the main tech programs: what they give, what they require, and what stage of readiness an organization needs to be at. The filter helps separate what's available to you now from what's still too early.
A table of tech programs with your organization's statuses marked: "fits now" or "too early, revisit later" for each. This document closes out the entire map of the grant world: all five continents are marked, and you can see where you have an open door and where you still need to grow into it.
How are basic cloud credits different from a competitive tech grant?
Basic credits go to nearly any verified organization with no competition, closer to Level I benefits. A competitive grant is a contest requiring a clear application and track record.
What happens if I get credits with no project for them?
Most often they simply expire unused, like in this lesson's opening scene. A resource with no specific task doesn't benefit the organization.
Do I have to be a technology organization to get a tech grant?
No, but you need a clear technology project inside your mission, whatever that mission is. What matters is a specific task for the technology, not the organization's overall profile.
How often do these programs open?
It varies: some, like AWS Imagine Grant, run an annual cycle with applications opening in spring. Terms and timing change, so check the program's site before preparing an application.
That completes the map of the grant world: all five continents are marked, a short list of targets is built, and readiness for each type of money is honestly assessed. Next, the course moves from the map to the craft: how to write an application a funder reads to the end and wants to support. The next module is about grant writing as engineering.