Most sectors choose their AI work by value. This one chooses it by what the marking on the document allows. Long before an architecture diagram exists, a releasability tag, an accreditation boundary and a mandated response format have ruled on what may be attempted, who may read the result, and what shape it arrives in. Program leads open with what AI could do for the mission. The security officer asks something prior: which of these jobs survives contact with the rules we already work under? Five came back often enough from defense, intelligence and federal buyers to count as this sector's own. For the cross-sector view, visit the cross-industry catalog.
AI Use Cases in Defense, Intelligence and Federal Government:
The Five Jobs This Sector Actually Described
The jobs this sector brought to us in its own words, the rule that binds each one, and where our own software stops on each.
Five jobs carry this sector, and no two are blocked by the same thing. Detecting government bids and responding in the required federal format. Getting fresh data into an air-gapped environment with no open connection. Releasing the same corpus at different levels to different outside parties. Using AI on classified material inside a SCIF or in theatre. Turning fragmentary reporting into a cited intelligence product. A different page owns each of those five rules, which is why this is the only place the set is visible as one sector's operating reality.
Where Iternal stops on this set. AirgapAI is built for classified and CUI-marked work and runs with no outside connection, but Iternal is not certified for export-control regimes such as ITAR, and accreditation belongs to your system rather than to a component inside it, so our software can only be a piece of a compliant solution. AirgapAI 2.0 is single-dataset driven and only one dataset can be searched at a time, which is precisely the mechanism the multi-level release job turns on. And a reasonably powered local machine runs about a year behind what the data center can do, which is the answer to an analyst asking why not just use the strongest model available.
Three things decide whether this works in your environment. Who owns the refresh loop for a disconnected data set, because the software does not notice that source material changed. How a releasability tier maps onto a data set, because that mapping is the separation. And what a citation looks like today, because an untraceable intelligence product is not a product.
A job on this list is a description of work, not a delivered system. What follows is the set and the rule behind each job. These are jobs rather than a tool shortlist. For more information on what a regulated data class permits, visit the regulated data classes page.
Who Described This Work
The sector here is not a market-sizing exercise. It is separate organizations that described their own work to us: a service branch, defense primes, systems integrators, a federal research contractor, and a foreign government.
Secure offline AI inside a SCIF. Deployed teams working through periods when comms go dark. A fragmentary order turned into a cited briefing. Carrier strike group architectures. Submarine crews. Automated detection of public solicitations, answered in a format the government mandates. Releasing a document to allied partners while restricting parts of it from other members of the same alliance. None of that is a generic enterprise use case with a defense label attached.
The Five Jobs This Sector Described
The table is the work as this sector described it to us in our own conversations, not an independent survey of the sector — read it that way. One cell in the last column is empty on purpose: we hold no statement about our software there, and a plausible guess is worse than a visible gap.
| The job | Who described it | What binds it | Where AirgapAI stops on this job |
|---|---|---|---|
| Detect government bids and respond in the required federal format | Proposal, bid and capture team | Output must match a mandated form, template or standard | Not recorded. No statement in our conversations covers AirgapAI against a mandated federal response format. Left explicitly empty rather than guessed. |
| Get fresh data into an air-gapped environment with no open connection | IT architect, AI architect or infrastructure lead | Air-gapped or fully disconnected environment | A data set does not update itself: offline, the app has no awareness that source content changed, and model currency is left to the customer. |
| Release the same corpus at different levels to different outside parties | Security, compliance and risk lead | Export-controlled or release-restricted material | AirgapAI 2.0 is single-dataset driven, and only one dataset can be searched at a time. |
| Use AI on classified material inside a SCIF or in theatre | Intelligence and defense analyst | Classified or CUI material inside an accredited facility | Iternal is not certified for export-control regimes such as ITAR. Accreditation attaches to your system rather than to a component, so our software can only be a piece of a compliant solution. |
| Turn fragmentary reporting into a cited intelligence product | Intelligence and defense analyst | Every answer must cite a verifiable source | Changing the output format of citations is limited by the AI model, so clickable source links cannot be delivered today. |
Five jobs, four roles, five different rules — and nobody in that second column can approve the next row alone. That is why sector AI programs stall.
What Makes Each Job Sector-Specific
Sectors differ on one axis that matters: the document in play, and what it costs when that document is wrong.
Detect government bids and respond in the required federal format
The document is the response itself, in the form the solicitation or the prime dictates. Get the substance right and the form wrong and the bid is rejected on form rather than content — the most expensive kind of no, because nobody read the answer. Buyers described solicitations scattered across government portals with no APIs and no workable format, and manual public-sector bids that take a month. Our record holds nothing about our own software against a mandated federal template, so treat that as a question rather than a claim: hand it your form and see what returns. For more information visit the proposals and RFP page.
Get fresh data into an air-gapped environment with no open connection
The document is the disconnected corpus, and the consequence is an analyst answering confidently from stale material. Nothing flags staleness. Iternal states the mechanism plainly: a data set does not update automatically because, running offline, the app has no awareness that source content changed; nothing triggers a re-vectorize when a watched directory changes; and AirgapAI does not update local models itself. Read that as a staffing requirement — somebody owns the refresh, on a schedule, or the corpus quietly ages.
Release the same corpus at different levels to different outside parties
The document is the releasability tag, and the consequence is material reaching a partner it was restricted from. Here our limit and the requirement meet on one mechanism. AirgapAI 2.0 is single-dataset driven and only one dataset can be searched at a time, so each release level becomes its own data set and separation comes from construction rather than from a setting a misconfiguration could undo. That is also the ceiling: one question cannot reach across two levels, and the tagging that decides membership stays a human editorial job.
Use AI on classified material inside a SCIF or in theatre
The material is classified and CUI-marked inside an accredited facility, and one paragraph in one document can change it from unclassified to top secret. That is a buyer's sentence, and it explains why this sector treats tool selection as incident avoidance. AirgapAI is built for classified and CUI-marked work and runs with no outside connection, but Iternal is not certified for export-control regimes such as ITAR, and accreditation attaches to the system as assessed: our software sits inside somebody else's boundary and can only be a piece of a compliant solution. Anyone calling a product compliant on its own has skipped the part where your authorizing official signs. For more information visit the security review page.
Turn fragmentary reporting into a cited intelligence product
The document is source reporting turned into something a commander acts on, and the consequence is a product whose citation cannot be checked. An analyst who cannot follow a citation back is left trusting a machine. Iternal is direct about the ceiling: changing the output format of citations is limited by the AI model, so clickable source links cannot be delivered today, and the current question-and-answer style assistant cannot list sources in the source box or link into video without moving to a different model. Verification stays a manual step — budget the minutes. For more information visit the traceable answers page.
What to Settle Before a Pilot
The gap between a recorded property and your own environment closes with written answers, not with a longer demonstration:
-
Which of our releasability levels becomes its own data set, and who owns the tagging that decides what belongs in each one?How one-data-set-at-a-time maps onto your real release tiers.
-
In our accreditation package, which controls does Iternal software satisfy and which ones must our own environment carry?The boundary between component and accredited system, on the document your authorizing official reads.
-
Who refreshes a disconnected data set, on what schedule, and by what route does new material reach the machine?The standing job the software does not do for itself, staffed instead of assumed.
What Is Not Sector-Specific
This sector also runs work that looks identical in a bank or a factory. Those jobs are real here but are not specific to the sector, because nothing about them changes when the badge does. Each has its own page:
- Decompose an inbound RFP into its questions and draft each answer: the proposals and RFP page.
- Keep each team's documents out of every other team's answers: the access control page.
- Keep working on a plane, at sea or anywhere with no signal at all: the disconnected operation page.
- Expose a bounded, grounded assistant to an outside audience: the traceable answers page.
Why Not Just Use the Strongest Model Available
An analyst asks this in nearly every conversation, and Iternal answers without decoration: a reasonably powered local machine runs about a year behind what the data center can do. Local models sit closer to the general assistant quality of a couple of years ago than to a top-tier model in a large data center, and on device the product cannot do everything the data center side can, because local compute is the ceiling.
That trade reads differently here than anywhere else. In a commercial enterprise the choice is a strong hosted model against a slightly weaker local one. Inside an accredited facility the hosted model is not on the menu at any price, so the comparison is a capable local assistant against none at all — beside which a year of model lag is a rounding error. For more information visit the frontier gap page.
Where the Model Came From Is a Selection Rule Here
Buyers raised one constraint that rarely appears in commercial evaluations, and they raised it flatly: models of Chinese origin are not appropriate for a defense program to use. The reasoning was specific rather than reflexive — a poison pill could sit in the code such a model generates, invisible to the team running it — and it holds even where the excluded model is the strongest available.
So model selection here is a documented decision, not a default. Record the origin of every loaded model, name who signs it off, and check again at each refresh, because refreshes are how an unapproved model quietly arrives. No model list belongs here; support is a moving target that one page owns. For more information visit the supported models page.
What Would Have to Be True Here
Each job clears one gate before anything else about it matters. This is a routing table and nothing more: the gate is named, the page that settles it is linked, and nothing from those pages is repeated here. A summarized permission decision is how people end up quoting the wrong version.
- Output must match a mandated form, template or standard — the proposals and RFP page.
- An air-gapped or fully disconnected environment — the disconnected operation page.
- Export-controlled or release-restricted material — the regulated data classes page.
- Classified or CUI material inside an accredited facility — the security review page.
- Every answer must cite a verifiable source — the traceable answers page.
One gate sits outside that table, because it is decided by an authorization package rather than by a job: whether a hosted service may be used by a federal program at all. For more information visit the FedRAMP AI page.
What a Catalog Does Not Prove
A catalog is not a demonstration. Finding your sector on a list shows that somebody described this work to us and nothing more; it is not evidence that a system has been built and run for the sector. For most jobs above, our record holds the description and no published outcome.
Our own failures sit in the same file as everything else, so here they are. Iternal has not been able to offer genuinely different demonstrations by sector, only different wording around the same one. A long internal list of use cases, and the attempts to filter it by sector, did not work for the partners it was built for. More than once, the exact scenario a prospect asked to see had nothing built behind it and we walked through an earlier one instead. Assume that gap sits behind any sector list a software company publishes. The repair either way: run the job you need, on your own material.
Where to Go Next
One of the five has a deep workflow page of its own — bid and proposal production, on the proposals and RFP page. The other four have none, and saying so beats inventing a link: their gates route through the section above, and the neighboring workflows sit in our manual document-work pages.
- Choosing which of these jobs to pilot first, and scoring the candidates — see the use-case selection method.
- Comparing named tools and running a structured selection across them — see the tool-selection page.
- How government buying rules, quotes and funding cycles shape the purchase — see the procurement and contract page.
FAQ: AI in Defense, Intelligence and Federal Work
Five recur across this sector: detecting government bids and responding in the required federal format, getting fresh data into an air-gapped environment with no open connection, releasing the same corpus at different levels to different outside parties, using AI on classified material inside a SCIF or in theatre, and turning fragmentary reporting into a cited intelligence product.
That call belongs to the authorizing official for the accredited system, not to a software company. AirgapAI is built for classified and CUI-marked work and runs with no outside connection, but accreditation attaches to the system as assessed, so our software is a component inside somebody else's accreditation boundary rather than a compliance answer on its own.
Your program does, and no software certificate transfers it: Iternal is not certified for export-control regimes such as ITAR. AirgapAI is built for ITAR- and CUI-scoped work and processes entirely inside your boundary with no outside connection, which is what keeps technical data out of a cloud round trip. What a deployment may carry is still decided by your own assessment of the whole system, and our software can only be a piece of it — better settled now than discovered in a security review.
AirgapAI 2.0 is single-dataset driven and only one dataset can be searched at a time, so each release level becomes its own data set and separation comes from construction rather than from a setting. That is also the ceiling: one question cannot span two levels, and the tagging that decides membership stays a human job.
It points the analyst at the source and stops short of a clickable one. Changing the output format of citations is limited by the AI model, so clickable source links cannot be delivered today, and the current question-and-answer style assistant cannot list sources in the source box or link into video without a different model.
Because inside an accredited facility it is not on the menu. A reasonably powered local machine runs about a year behind what the data center can do, and on device the product cannot do everything the data center side can. So the real comparison here is a capable local assistant against no assistant at all.
Start With the Job, Not the Platform
Pick the one job here that would change a week of somebody's work, name the rule it has to clear, and test it on material you already hold. That sequence answers what a sector list never can: whether the work survives your own rules.