AWS Imagine Grant 2026-2027 U.S. Nonprofit Cycle (Historical Reference)

AWS Imagine Grant 2026-2027 U.S. Nonprofit Cycle (Historical Reference)

Cycle status

The 2026-2027 U.S. AWS Imagine Grant cycle is closed. AWS’s official program page says that the 2026 application cycle is closed, and its U.S. proposal guidelines show that public Round One applications closed on June 5, 2026. The September 14, 2026 date sometimes associated with this cycle was the close of Round Two, which was restricted to organizations AWS had invited after reviewing Round One. It was not an additional public deadline.

As of this update, AWS has not published a later cycle or a new application date on the official program page. AWS’s FAQ still has a generic submission instruction saying the “next application cycle” will open in March 2026; read alongside the dated 2026-2027 calendar and the program page’s closed-cycle notice, that sentence points to the cycle documented here, not to a later round. This record is therefore a historical reference to the completed 2026-2027 cycle. A nonprofit that did not submit in Round One cannot apply to this cycle now; organizations that were invited to Round Two should rely on the instructions sent to their proposal contact. Check AWS’s program page or sign up there for email alerts before planning around another cycle. Do not treat an old calendar or a past round date as an open application window.

Program at a glance

AWS Imagine Grant supports U.S. nonprofits proposing a pilot, proof of concept, or new or expanded program that uses cloud technology for mission outcomes. The 2026-2027 U.S. cycle offered three award categories intended for different stages of technology adoption. Each package could combine unrestricted financial support, AWS Promotional Credit, implementation guidance, training, and the possibility of AWS marketing promotion. AWS retained discretion over actual award amounts, so the listed figures are maximums rather than guaranteed awards.

These categories are not simply different grant sizes. A project’s architecture, current capabilities, operational maturity, and intended outcome should fit the selected track. AWS says an applicant may submit one project in one category per cycle. Applicants to Pathfinder could be considered for Go Further, Faster if they were not shortlisted for Pathfinder Round Two.

Who could apply

The U.S. award was open to nonprofit organizations based in the United States with active, registered 501(c) status. AWS’s eligibility language includes 501(c)(3) organizations, credit unions, public utilities, and other entities designated under 501(c). Organizations with annual budgets of any size could apply, and AWS welcomed proposals from different mission areas. Serving beneficiaries outside the United States did not itself disqualify an organization registered in the U.S. with the required status.

Educational institutions were excluded from this cycle. AWS specifically identified primary and secondary schools, colleges, and universities as outside the program’s priority funding areas. An education-focused nonprofit that is legally distinct from a school should have confirmed the applicant entity’s status rather than assuming a partner institution’s eligibility transferred to it.

Applicants did not need to already use AWS to submit. AWS stated that AWS use was not an application requirement, although the award package includes AWS-specific resources and the program is best suited to projects that plan to incorporate AWS technology. A proposal still needed a credible technical design and a clear relationship between its cloud work and the organization’s mission.

The invitation rule matters when interpreting the final stage. Every eligible applicant could submit in Round One, but only organizations invited after that review could submit a full Round Two proposal. The Round Two close on September 14 did not reopen applications to organizations that had missed Round One.

What the three categories covered

Momentum to Modernize was intended for foundational technology projects that improve core mission operations. AWS’s examples included systems and application migration, database migration or centralization, new application development, data lakes or warehouses, containerization, serverless services, and microservices adoption. The category was suitable when modernization, reliability, security, or basic cloud capability was a necessary step toward better service delivery. A strong proposal would explain what is difficult or costly in the current environment, what would change, and how beneficiaries or staff would experience the improvement.

Go Further, Faster was for organizations with a cloud foundation and a plan to use more advanced capabilities against a significant mission or operational problem. AWS named artificial intelligence, machine learning, deep learning, high-performance computing, and large-scale data projects among possible workloads. The category called for an explanation of how existing data and security practices would support the work and how the project could produce a scaled, repeatable result. Simply naming a modern technology would not establish category fit; the proposal needed to make the path from that technology to an organizational outcome understandable.

Pathfinder targeted projects at the frontier of artificial intelligence, including generative AI, agentic AI, and autonomous systems. In this track, frontier AI had to be a core workload during the grant term, rather than a minor feature added to a conventional modernization project. AWS described Pathfinder as a fit for organizations with a strong data practice and projects already in planning. The guidelines emphasized the need for a sound data foundation, a strategic role for AI in the solution, and an implementation approach that could turn the work into a repeatable mission capability. Projects with an AI component that did not meet Pathfinder’s criteria could be a better match for Go Further, Faster.

How the 2026-2027 application worked

The public Round One portal opened on March 19, 2026 and closed at 11:59 p.m. Eastern Time on June 5, 2026. AWS said late applications would not be accepted. Applicants used the web form linked from the Imagine Grant program page, selected one category, and submitted one project. AWS planned to notify Round One applicants by July 14 about their status and whether they had advanced. Round Two opened August 10 and closed September 14 for invitees only. The official calendar listed results communication in mid-November and public announcement of winners on December 1.

The Round One form asked for organizational identity and contact information, recent revenue and IT budget ranges, mission area, AWS account and prior application status, and project information. It asked applicants to provide a short project overview, describe the project and its mission relationship, explain intended outcomes and why the project was timely, identify its development stage, and describe how it would be supported over the long term. Pathfinder applicants also answered questions about their organization’s current use of data and the AI services they proposed to integrate.

The technical portion asked for a high-level design, required technical skills and resources, potential implementation partner needs, and the current infrastructure environment. The form also asked how AWS fit the intended work. Applicants had to complete certifications and consent steps and agree to the program’s terms. AWS instructed applicants not to include confidential material or third-party information they lacked permission to use. Round Two applicants received separate full-proposal instructions at notification; the public Round One form was not a substitute for that invite-only process.

What reviewers considered

AWS listed innovation and uniqueness, mission-critical impact, defined outcomes and milestones, appropriate AWS services, sustainability, completeness, and submission in the requested format by the deadline as evaluation factors. For applicants preparing a similar project in the future, those criteria point to a practical proposal structure: establish the service problem, provide a credible baseline, specify what will change, map technical work to milestones, explain how the organization will operate and fund the result over time, and identify the relevant staff or implementation partners.

The project description should make outcomes measurable without pretending to know future results. A nonprofit might state a baseline processing time, a target service capacity, or a reduction in manual work if it can support those figures. It should distinguish direct outputs, such as a migrated database or a tested case-management workflow, from mission outcomes, such as faster referrals or wider access to a service. AWS’s criteria include both the technical details and the mission effect, so neither can stand in for the other.

Category choice should follow the project’s actual readiness. A legacy migration, application rebuild, or data foundation project generally belongs closer to Momentum to Modernize. An organization with established cloud and data capabilities pursuing advanced analytics, AI, or high-performance computing for a repeatable program may fit Go Further, Faster. A proposal for Pathfinder needed frontier AI to be central and required a credible data practice and project plan. The award’s larger maximum did not make it the appropriate selection for every applicant.

Planning after the closed cycle

This page does not announce an upcoming application window. A nonprofit considering the program later should verify the next cycle’s dates, eligibility, award limits, application questions, and terms directly with AWS when those materials appear. The 2026-2027 guidelines are useful for understanding how that cycle was structured, but they should not be treated as instructions for a future round without checking for revisions.

In the meantime, an organization can preserve useful planning work without assuming it will be eligible or selected. Record the legal applicant name and current 501(c) status, identify a proposal contact and project lead, and decide which entity would own the resulting work. Document the current service problem and the people affected. Build an outcome measure and a credible baseline. Describe the technical environment, data sources, security needs, operating costs, and skills required to maintain the project. If an external partner will help, define its role and what the nonprofit itself will own after the implementation period.

For a potential Pathfinder project, teams should be able to explain what data informs decisions today, how data quality and governance will support the AI workload, why generative, agentic, or autonomous capability is necessary, and how people will supervise or evaluate its use. For other categories, applicants should show that modernization or advanced cloud services address a specific operational or mission need. These preparation steps make a future application more concrete, but they do not imply that a new cycle is open.

AWS’s FAQ also directs organizations that are not ready for the grant toward its separate Nonprofit Credit Program. That is a different offering with its own eligibility and terms; its credits should not be confused with the Imagine Grant’s award packages. Check the current AWS nonprofit program pages for those details.

Official sources

• AWS Imagine Grant program page: current cycle status, U.S. categories, award packages, eligibility, and program resources.
• AWS Imagine Grant FAQ: eligibility, annual timeline, selection criteria, and Round Two process.
• 2026 U.S. proposal guidelines: official guideline landing page and downloadable application materials for the archived cycle.

The main AWS program page is the best place to check for a new announcement. Until AWS publishes a later cycle, this listing remains an archive of the 2026-2027 opportunity with its public deadline recorded as June 5, 2026.