IDEaS 2026: The Complete Guide to Canada's Defence Innovation Funding

IDEaS — Innovation for Defence Excellence and Security — is the Department of National Defence's flagship innovation program, and it is structurally different from almost every other federal funding lever a Canadian SME is likely to encounter. It does not write open cheques to "promising" companies. It runs a portfolio of challenges: specific defence and security problems posted by DND and the Canadian Armed Forces (CAF), against which innovators submit proposals. Selected proposals receive non-repayable contributions to develop their solution through phased technology maturation, with the most successful working their way toward potential procurement by the Crown. For founders with a dual-use technology — something that works in commercial markets but also has real defence or security relevance — IDEaS can be the bridge between a startup product and a sustained government customer relationship. For everyone else, it is a poor fit. This guide explains what IDEaS actually funds in 2026, how its five elements differ, where Competitive Projects stages sit relative to your technology readiness level, what eligibility really looks like once you go past the published checklist, the security and ITAR considerations that catch first-time applicants, how IDEaS stacks with SR&ED and IRAP, the common reasons applications fail, and what a credible pathway to follow-on defence procurement looks like.

What IDEaS is and the dual-use lens

IDEaS sits inside DND, not Innovation, Science and Economic Development Canada (ISED). That single fact explains almost everything that makes the program feel different from IRAP, SR&ED, or the regional development agency funds. IDEaS is not a horizontal program designed to support Canadian innovation broadly; it is a vertical program designed to acquire technology capability for the Canadian Armed Forces. Every dollar it spends is justified to Parliament against a defence or security outcome. Every challenge it posts comes out of a CAF or DND requirements process. Every successful project is, at minimum, a step toward a Crown procurement decision — even if procurement itself is a separate process that IDEaS does not own.

This shifts the value proposition. With IRAP, you bring a project and the program funds the technical work. With IDEaS, DND posts a problem and you bring a solution. The funding is meaningful, but the strategic prize for innovators is the relationship: getting your technology into the hands of CAF operators, generating real-world performance data inside a defence context, and building a procurement-relevant credential that opens doors at NATO allies and other Five Eyes partners. Companies that approach IDEaS as a grant program tend to underperform. Companies that approach it as a structured route into a customer relationship with DND tend to extract substantially more value than the headline contribution suggests.

The dual-use framing matters because most Canadian innovators are not, and should not become, pure defence contractors. Defence-only products have long sales cycles, narrow markets, and significant export-control friction. Dual-use technology — something with a clear commercial market that also has defence applications — lets a company use IDEaS to accelerate development and validation while building a commercial business that is not dependent on a single Crown customer. Examples of dual-use categories that recur in IDEaS challenge calls include autonomous systems, advanced sensors, communications and networking, AI/ML applied to large data sets, cyber tooling, advanced materials, energy storage and propulsion, human performance and medical technology, and space-domain capabilities. If your roadmap touches one of those areas, IDEaS is worth understanding closely. If it doesn't, the time-to-fit is usually too long to justify the application work.

The five elements

IDEaS is not a single funding mechanism. It is a portfolio of five distinct elements, each designed for a different type of innovator interaction with DND. Choosing the wrong element is one of the more common ways a credible innovator wastes an application cycle. The elements:

• Competitive Projects. The largest and most familiar element. Phased contributions tied to specific posted challenges. Innovators enter at the technology readiness level (TRL) that matches their solution and can progress through subsequent components as their work matures. This is where most of the program's dollars and most of the prototype work lives.
• Test Drives. Designed for innovators whose product is already mature and just needs DND exposure. CAF takes the technology into a real or simulated operational context and provides structured feedback. There is no contribution agreement in the IRAP sense — the value is access to a credible end-user testing environment that no commercial market can replicate.
• Contests. Open competitions on a specific, hard problem. Prize-based structure with rounds: smaller prizes for shortlisted entries, larger prizes for finalists, and contribution-style funding for selected teams to develop their solutions further. The Pop-Up City contest is a recent example, with prize rounds escalating from $10,000 per Round 1 winner through to contributions of up to $1,500,000 for finalists building a prototype.
• Sandboxes. Time-bounded events where IDEaS supplies infrastructure, subject-matter experts, and the relevant operational context, and selected innovators bring their technology in for hands-on integration and testing. Particularly useful for technologies that are hard to demonstrate without specialized facilities — underwater sensors, radio-frequency systems, autonomous platforms requiring large or controlled spaces.
• Innovation Networks. Larger, longer-horizon awards (up to roughly $3M) that fund research networks — typically academic-led consortia — tackling a strategic defence research area over multiple years. The recent Defence Innovation Secure Hubs (DISH) initiative is a higher-envelope variation, with a total funding pool announced at up to $50M.

The practical sorting question for a founder is which element matches the maturity of the technology and the goal of the engagement. A pre-prototype team chasing dollars to validate an idea belongs in Competitive Projects Component 1a. A team that already has a deployable system and wants CAF feedback belongs in a Test Drive or a Sandbox. A research-heavy team with academic partners belongs in Innovation Networks. Contests fit teams who like to compete on a specific posted problem with a clear path from prize money through to prototype funding. Trying to force one element to do the job of another typically produces a weak application.

Competitive Projects: Stage 1 vs Stage 2 (and the components in between)

Competitive Projects is the element most innovators end up engaging with, and its component structure is worth understanding in detail. The program uses the standard Technology Readiness Level (TRL) framework to sort projects into three components, each with its own envelope and timeline.

The simpler way to think about the structure is that Component 1 (sub-divided into 1a and 1b) is proof-of-concept work, and Component 2 is prototype development. An innovator can enter the continuum at the component matching their current TRL — you do not have to start at Component 1a and walk every step. A team that already has a TRL 6 prototype and a clear path to TRL 9 can apply directly to Component 2 against a challenge where their technology fits. Conversely, a team with a research-grade concept at TRL 2 starts at Component 1a, and progression is not automatic — each subsequent component requires a successful close-out of the previous one and, typically, a fresh evaluation against the criteria.

One observation that consistently surprises first-time applicants: the bottleneck on Component 2 is rarely technical merit. By the time a project reaches Component 2 it has usually demonstrated technical credibility. The bottleneck is execution capacity — whether the innovator's organization can deliver a multi-million-dollar program of work with real defence stakeholders to report into, real milestones to meet, and a real review framework. Innovators who can write a compelling Component 1 proposal but cannot staff and run a Component 2 program of work get filtered out at this point. Building credible Component 2 capacity is a separate problem from winning a Component 1 award, and it usually starts before the Component 2 application is filed.

Eligibility — Canadian focus, dual-use technology, and ITAR considerations

The published bar to apply to IDEaS is broad. The bar to win is narrower and is shaped by factors that often surface only deep in evaluation. Start with the formal criteria:

• The program is open to a wide range of Canadian innovators: small and medium-sized enterprises, large companies, academic institutions, non-profits, and (for several elements) individuals.
• Federal government employees, federal departments and agencies, and federal Crown corporations are not eligible to apply.
• Each challenge call has its own eligibility specifics — some are restricted to Canadian-based innovators; others (particularly some Test Drives) accept proposals from international organizations as well.
• The technology must be relevant to the specific challenge posted — "we have a good idea" is not enough. The proposal must respond to the published statement of the problem.

Beyond the published criteria, several softer eligibility factors are real even when they don't appear on a form:

• Defence relevance has to be specific, not aspirational. The strongest proposals draw a direct line from the technology to a stated DND or CAF requirement. Generic "this could be useful to defence" framing reads as a tell that the applicant has not engaged with the actual problem statement.
• Dual-use framing helps when honest. If your business has a real commercial market, say so — it signals you can sustain the work after the contribution ends and that you bring engineering muscle developed for commercial scale, not a hobbyist research effort. Faked dual-use framing (where the "commercial market" is invented to make a defence-only product sound viable) tends to read as exactly what it is.
• Canadian control and IP residency. Where does the IP sit? Where do the engineers work? Where are the corporate decision-makers? Foreign-controlled or foreign-headquartered applicants are not categorically excluded but face higher scrutiny, particularly at Component 2 and Innovation Networks scale.
• Team credibility on the defence problem. Evaluators look for evidence the team has done the homework on the problem space — not necessarily prior defence contracts (which would exclude almost every dual-use innovator), but a substantive understanding of the operational context the technology has to work in.

The export-control and security dimension is where well-meaning innovators most commonly trip. A few things to be aware of, with the caveat that any specific case is best addressed with qualified counsel rather than against general guidance:

• ITAR considerations are case-specific. If your technology incorporates U.S.-origin components, technical data, or know-how that is itself ITAR-controlled, your ability to develop and demonstrate the technology under a Canadian defence contribution may be constrained by U.S. export-control rules. This does not automatically disqualify the project, but it does mean the export-control posture has to be understood before the application, not discovered during it.
• Controlled Goods Program registration can become relevant at higher TRLs and when the technology touches Canada's own controlled goods list. CGP registration is its own multi-month process and should be planned around if it is going to be required for delivery.
• Security clearance is sometimes relevant, often less than founders expect. Many IDEaS interactions, particularly at earlier components and for Test Drives and Sandboxes with unclassified context, do not require cleared personnel. Other engagements — access to classified facilities, integration with classified systems, or work tied to specific operational data — do require clearances or facility security clearances on the company side. The right time to find out is during the challenge call assessment, not after award.

Application process and security gates

The IDEaS process is challenge-driven. There is no rolling open application portal in the way IRAP has the ITA channel; instead, IDEaS publishes specific challenge calls on the canada.ca/defence-ideas site, each with a posted deadline, scope, evaluation criteria, and submission template. The typical flow:

The single most important point about the process: read the challenge call as written and respond to the problem it describes. IDEaS evaluators are scoring proposals against the published criteria, not against the merits of the technology in the abstract. The most common cause of disqualification on otherwise strong technologies is a proposal that describes what the company wants to build rather than what the challenge asked for.

Stacking IDEaS with SR&ED and IRAP

This is one of the highest-value mechanical questions an IDEaS applicant has to get right. The short version: IDEaS, SR&ED, and (where applicable) IRAP can be combined on the same underlying technology work, but each program has its own rules for what counts as government assistance and how it interacts with the others. Done well, the combination materially extends the dilution-free funding base for a Canadian R&D business. Done badly, it produces an SR&ED audit finding or a contribution-agreement compliance issue.

The interaction rule that matters: any cost reimbursed by IDEaS must be subtracted from your SR&ED expenditure pool before computing the federal SR&ED tax credit. The same rule applies to IRAP, and if both programs are funding overlapping work, you cannot count the same cost against both either. In practice this means structuring the project plan so that IDEaS, IRAP (where relevant), and the SR&ED-claimable residual are tracked separately from the start of the project.

A common, workable structure for a dual-use technology company:

• IDEaS funds the defence-specific adaptation, demonstration, and CAF-facing deliverables — the work the program is actually paying for under the challenge call.
• IRAP (or a regional program) cost-shares the parallel commercial development work — the technology base that supports both markets but is being matured beyond the defence-specific contract.
• SR&ED picks up the residual eligible R&D — the technical-uncertainty-driven experimentation across the project that has not already been reimbursed by IDEaS or IRAP — and produces a refundable tax credit on the company-funded share.

The technical narrative under SR&ED's S/THERI structure (Scientific/Technological uncertainties, Hypotheses, Experimentation, Results, Iteration) should align with the milestone structure in the IDEaS contribution agreement — same underlying engineering story, told for different purposes, with the cost separation clean enough to survive a CRA review. Companies that wait until tax-filing time to figure out the netting almost always leave SR&ED dollars on the table or trigger an audit-finding question on the next review.

Common reasons applications fail

Across IDEaS rejections we see in practice, a small number of failure modes recur far more often than the rest. In rough order of frequency:

• Weak defence or dual-use thesis. The technology may be genuinely innovative, but the proposal does not connect it credibly to the challenge as written. Evaluators score against the challenge statement, not against the inherent appeal of the technology — if the connection requires the reader to do the work, the proposal fails.
• No DND-relevant outcome. Successful proposals describe a deliverable that DND or CAF can actually use, test, or evaluate at the end of the project. "We will publish a paper" or "we will have a working demo on our developer machines" is not a defence-relevant outcome. "We will deliver a prototype that the [specific CAF user community] can test against [specific operational scenario]" is.
• Mismatch between TRL and component. A team at TRL 7 applying to Component 1a because it sounds easier — or a team at TRL 2 applying to Component 2 because they want the larger contribution — gets filtered out. The components exist to fund specific levels of technology maturity; applying outside your real TRL band is read as either a misunderstanding of the program or a financial-need application disguised as a technical one.
• Execution capacity gap. The team described in the proposal cannot credibly execute the program of work proposed. This shows up most often at Component 2 scale, where a $3M–$5M project requires meaningful engineering, integration, and program-management capacity that a five-person company simply does not have on staff.
• Format and submission errors. Page-limit violations, missing required attachments, late submissions. IDEaS treats published format requirements as gating, not advisory.
• Unaddressed security or export-control posture. Late-stage discovery that ITAR-controlled components or classified-context requirements make the proposed work infeasible under the contribution as designed. The application stage is where this should be diagnosed, not after award.

The pattern across all of these is that successful applications are written for the evaluator and the challenge, not for the founder and the technology. The discipline of starting with the published challenge and working backward to the proposal — rather than starting with the company pitch and trying to bend it onto a challenge — is what separates an application cycle that produces an award from one that produces a polite decline.

Pathways to follow-on procurement

The reason a strategically-minded innovator pursues IDEaS, beyond the contribution itself, is the procurement pathway. IDEaS does not directly award procurement contracts — that is not its mandate — but it sits inside DND and produces validated technology that other parts of DND can buy. The realistic procurement pathways that flow out of a successful IDEaS engagement include:

• Innovative Solutions Canada (ISC), Public Services and Procurement Canada's broader innovation procurement program. Technology validated through IDEaS can be a strong candidate for ISC's Testing Stream or Challenge Stream, which are explicitly designed to support first procurement of innovative Canadian solutions across federal departments.
• DND program-of-record procurement. Where the technology fits an existing or emerging DND requirement, a successful IDEaS prototype can feed into a downstream PSPC-led procurement that uses the IDEaS-funded validation as supporting evidence. This is a longer-cycle path but is where the largest follow-on dollars sit.
• Other-than-competitive procurement in limited circumstances, where a single supplier has demonstrated unique capability through the IDEaS engagement and a competitive procurement is not feasible. This is the exception rather than the rule.
• Allied procurement. An IDEaS-validated technology with NATO or Five Eyes relevance can be positioned for procurement by allied defence customers, often with the Canadian validation acting as a credential that reduces evaluation friction abroad.

None of these pathways is automatic. Each requires its own engagement, its own proposal effort, and (for the federal options) its own compliance with the Government of Canada's procurement rules. But the cumulative value of running through IDEaS and then converting into procurement — for innovators who execute both stages well — tends to dwarf the headline value of the original contribution. The contribution is the means; the customer relationship is the end.

Final thoughts

IDEaS is the right program for a narrow set of Canadian innovators and the wrong program for everyone else. It is the right program if you have a dual-use technology with credible defence or security relevance, the engineering capacity to execute against a challenge call, the appetite to engage with DND as a customer over a multi-year horizon, and the operating discipline to keep IDEaS, SR&ED, and any IRAP work cleanly separated for both contribution-agreement and tax purposes. It is the wrong program if you are looking for a generic startup grant, if your technology has no real connection to a posted challenge, or if you are not prepared for the additional friction that comes with defence-context work.

For the innovators who fit, the program is unusually high-leverage. The contribution amounts are meaningful, the validation credential is hard to replicate through any other Canadian funding lever, and the procurement pathways — pursued thoughtfully — can produce a sustained Crown customer relationship that materially changes the company's trajectory. For everyone else, the application work is better invested elsewhere — IRAP, SR&ED, regional development agencies, or the federal sectoral programs that match the company's actual market.

The practical first step for any innovator considering IDEaS is also the simplest: read the current funding opportunities listed at canada.ca/defence-ideas, identify the specific challenges that map to your technology, and assess whether the published evaluation criteria favour what you actually have. If the answer is yes, the application work is worth doing. If the answer is no, save the cycles and revisit when a better-fit challenge gets posted — IDEaS publishes new calls throughout the year.

IDEaS is one of several Canadian innovation funding programs — SR&ED, IRAP, Scale AI, FedDev, CanExport, and the provincial streams all play roles depending on stage and sector. Use our Grant Finder to compare IDEaS against SR&ED, IRAP, and the federal grants we cover before committing a quarter to defence-channel applications.