What Is DoD ESI?

September 8, 2026

The DoD Enterprise Software Initiative (ESI) is the Department of Defense's program for buying commercial software and software maintenance at enterprise scale. It negotiates Enterprise Software Agreements (ESAs) with software publishers and their resellers, and DoD buyers are required by regulation to check ESI before sourcing commercial software any other way.

‍

If you sell software or cybersecurity products to DoD, ESI is the layer sitting between your product and the buyer. It is also the least-documented major vehicle in federal IT, the top search results are a 2016 slide deck, a 2020 vendor blog post, and raw regulation text.

‍

This guide covers what ESI actually is, whether using it is genuinely mandatory (the answer is more specific than most sources say), who holds the agreements today, how a software company gets on one, and what changed in 2026, because a lot did.

‍

One naming note up front. Following Executive Order 14347, "Department of War" is now used as a secondary name for the department, and esi.mil has rebranded to DoW ESI. The DFARS still says "DoD Enterprise Software Initiative." You'll see both. They are the same program.

‍

What is the DoD Enterprise Software Initiative?

DFARS 208.7401 defines ESI as "an initiative led by the DoD Chief Information Officer to develop processes for DoD-wide software asset management."

‍

In practice, ESI does three things:

Negotiates enterprise-wide agreements with software publishers, so DoD isn't buying the same product at hundreds of different prices
Standardizes terms and conditions, not just price — including licensing terms that affect cloud portability and interoperability
Maintains a catalog at esi.mil that DoD buyers are directed to check first

‍

Per its own site, ESI is "an official DoD initiative sponsored by the DoD Chief Information Officer (CIO)" that exists "to lead in the establishment and management of enterprise COTS IT agreements, assets, and policies," lowering total cost of ownership across DoD, the Coast Guard, and the Intelligence Community. It's generally dated to 1998.

‍

Ownership sits with the DoD/DoW CIO — not DISA, not a service program office, though the Navy plays an outsized executing role. Most ESAs are awarded through NIWC Pacific in San Diego.

‍

What is an Enterprise Software Agreement (ESA)?

An ESA is the contract vehicle ESI creates. DFARS 208.7401 defines it broadly: "an agreement or a contract that is used to acquire designated commercial software or related commercial software services such as software maintenance."

‍

So the common shorthand — "ESAs are BPAs against GSA Schedules" — is a fair generalization but wrong as an absolute. Some ESAs ride SEWP, meaning ESI layers on top of a GWAC rather than competing with it.

‍

That's the key mental model: ESI is not a contract vehicle in the way SEWP or a GSA Schedule is. It's a sourcing program that uses those vehicles. A GSA Schedule is the underlying IDIQ. A BPA is an ordering arrangement placed against it. A GWAC is a governmentwide IDIQ. ESI is the DoD program that builds agreements on top of all three.

‍

Is DoD ESI mandatory?

Not exactly and the precise answer matters, because "mandatory" is what most sources say and it isn't quite right.

‍

DFARS 208.7402(a) says departments and agencies "shall fulfill requirements for commercial software and commercial software services... in accordance with the DoD Enterprise Software Initiative." But the same paragraph ends with a sentence almost every summary omits:

‍

"ESI does not dictate the products or services to be acquired."

‍

The actual obligation is a process, spelled out in PGI 208.7403:

The requiring official checks DoD inventory first — existing enterprise licenses and DoD-wide maintenance agreements. If it's there, they use it.
If the software isn't in inventory and isn't on an ESA, they "may fulfill the requirement by other means."
If it is on an ESA, they review the ESA's terms, conditions, and pricing.
If the ESA "represent[s] the best value to the Government," they must buy through it.
If the ESA is not best value, the Software Product Manager (SPM) gets 3 working days to update the agreement, commit to a date, or decline. If the SPM doesn't respond in 3 days, or won't fix it within 90 days, the buyer can go elsewhere.
A designated management official can formally waive the ESA requirement, with rationale provided to the SPM.

‍

The accurate framing: DoD buyers must check ESI first and must use an ESA when it represents best value, but ESI doesn't dictate which product they buy, and there's a documented waiver path.

‍

For a software vendor, that distinction is the whole ballgame. Being on an ESA doesn't guarantee you orders. It puts you inside the default path, and forces anyone who wants to buy a competitor's product to justify stepping outside it.

‍

One exception where it really is mandatory: the Army. AFARS 5139.101-90 states that Army purchasers "must satisfy their IT requirements by utilizing the Joint and Enterprise License Agreements (J/ELA), DoD Enterprise Software Initiative (ESI) agreements, and/or CHESS contracts first, regardless of dollar value or financial appropriation." Going outside requires a Statement of Non-Availability from CHESS plus Army DCS G-6 approval. That's a materially harder gate than the DFARS waiver. (Note CHESS is currently rebranding to "Digital Market.")

‍

Who actually holds ESI agreements?

Publishers you'd expect are covered — Microsoft, Oracle, SAP, Cisco, Splunk, Fortinet, Palo Alto Networks, Elastic, Dynatrace, Trellix, Appian, Cloudera, Sonatype, CloudBees, ZeroFox, HCLSoftware, and others.

‍

But here is the fact almost nobody writes down, and it's the most important one for anyone in the channel:

‍

In most cases, the ESA holder is a reseller, not the publisher.

Appian's ESI BPAs were awarded to Carahsoft, Groundswell, and TD SYNNEX Public Sector. Appian holds nothing directly.
SAP/SAP NS2's agreement (N66001-19-A-0010) is held by Carahsoft.
Trellix's SEWP Agency Catalog runs through five authorized resellers — Augustus Schell, Carahsoft, Federal Government Systems, Paragon Micro, and Federal Resources. Four of the five are small businesses.
Microsoft flows through GovConnection, and its ITAM agreement through immixGroup/Arrow.

‍

The publisher gets reach. The reseller holds the paper. Orders are placed against the ESA under FAR 8.4 / DFARS 208.4 procedures for Schedule BPAs, or SEWP procedures for catalog agreements and where an ESA has multiple award holders, buyers compete quotes among them.

‍

Eligible buyers are broader than DoD alone: DoD components worldwide, the Intelligence Community, the U.S. Coast Guard, and FAR Part 51 authorized contractors.

‍

How does a software company get on a DoD ESI agreement?

There is no standing open on-ramp, and no published unsolicited proposal path. This is the honest answer, and it's why the question is so hard to research.

‍

ESAs are demand-driven and government-initiated. The ESI Working Group identifies where DoD is already spending heavily on a product, builds a business case, and then runs a competition — or, where justified, makes a direct award. The two largest 2026 agreements were explicitly spend-consolidation plays, not vendor-initiated.

‍

When ESI does compete an agreement, it looks like normal federal contracting. Appian's was competed on GSA eBuy: 990 vendors solicited, three responses, three awards.

‍

That number is worth sitting with. Three responses out of 990. Participation in these competitions is thinner than the volume of DoD software spend would suggest.

‍

Practically, a software company's path in looks like this:

‍

Get on the substrate first. ESAs are built on GSA MAS and SEWP. If you're not on one of those, you can't be on the agreement that rides it.

‍

Build demonstrable DoD spend. ESI aggregates existing demand. An ESA follows an installed base; it rarely creates one.

‍

Work your Component's SPM. PGI 208.7401 defines the Software Product Manager as "the Government official who manages an enterprise software agreement." The Army's SPM is CHESS by regulation; SECNAV oversees SPMs department-wide. Contacts are on esi.mil.

‍

Or attach to an existing ESA holder. Given that most agreements are held by resellers, the faster route for many publishers is a partnership with a Carahsoft, TD SYNNEX, or immixGroup that already holds the vehicle — rather than pursuing your own agreement.

‍

ESI vs. SEWP, GSA MAS, and the software pathways

This is where vendor content tends to go wrong, so it's worth being precise.

‍

ESI vs. GSA MAS and SEWP: not competitors. Both are substrates ESI builds on. A buyer uses ESI when an ESA exists for the product, because the pricing and terms are already negotiated. They use MAS or SEWP directly when one doesn't.

‍

ESI vs. NASPO ValuePoint: no relationship. NASPO is a state-led cooperative for state and local buyers. It has no role in DoD software acquisition and isn't referenced in DFARS 208.74.

‍

ESI vs. the Software Acquisition Pathway, CSOs, and OTAs: different problem entirely. A March 2025 memo made the Software Acquisition Pathway the preferred pathway for software development components of business and weapon system programs, with CSOs and OTAs as the default solicitation approaches.

‍

The clean distinction: if you're selling a commercial off-the-shelf product, that's ESI. If DoD is paying you to build software, that's SWP/CSO/OTA. They rarely collide.

‍

ESI vs. SWFT: the Software Fast Track initiative, established by an April 2025 DoD CIO memo, reforms how DoD authorizes software — the ATO and cybersecurity track. It's not a purchasing vehicle. For a cyber vendor both matter, but they're parallel tracks: SWFT gets you authorized, ESI gets you bought.

‍

What changed in 2026?

Three things, and the first one is significant enough that most published ESI content is now out of date.

‍

New governing policy, effective July 29, 2026. DoW Instruction 8000.02, "Information Technology Category Management", cancels the July 2000 memo that had governed ESI for 26 years. It creates an IT Category Management Cross Functional Board, designates the ESI Working Group as lead implementation agent, and adds CETAs and JELAs alongside ESAs. Its central mandate: DoW components "will use enterprise capabilities before pursuing individual IT investments unless mission or cost dictate otherwise," and component heads must analyze ESA pricing and terms before buying designated software elsewhere.

‍

For vendors selling point solutions, that language raises the bar. Enterprise-first is now explicit policy.

‍

Consolidation into mega-agreements. Two 2026 awards illustrate the direction:

Dell Federal Systems — $9.7B, five years. A CETA announced May 2026 consolidating dozens of Microsoft contracts across DoW, the IC, and the Coast Guard. DoW claimed roughly $422M in annual savings.
Oracle — N66001-26-D-0020. A single-award IDIQ awarded July 2026, $3.3B base and up to $6.99B with option, made non-competitively as a direct award. (Oracle's release describes a 10-year term; the DoW announcement states a five-year ordering period.)

‍

ESI is shifting from many mid-sized publisher BPAs toward a few very large agreements. If you're a mid-market software company, that trend is worth understanding — the aggregation that creates an ESA is happening at a larger scale than it used to.

‍

The FAR overhaul touched Part 208 but left ESI intact. DFARS Class Deviation 2026-O0049, effective March 6, 2026, retains Subpart 208.74 substantially as-is — "shall" becomes "must," and the detailed procedures stay in PGI rather than being elevated into regulation. Part 208 is actively in flux, so verify against current text if you're relying on it.

‍

The friction nobody advertises

Worth knowing before you build a strategy around ESI.

‍

Restrictive licensing is a documented problem. GAO-23-106290 found that vendor licensing restrictions raised DoD costs, limited cloud provider choice, and caused interoperability problems, and recommended the DoD CIO update guidance in coordination with ESI. The recommendation remained open as of early 2026.

‍

Sole-sourcing at scale draws scrutiny. A $6.99B non-competitive direct award and a $9.7B consolidated agreement concentrate an enormous share of DoD software spend into single vehicles. That has attracted press attention and is worth watching.

‍

Incumbency compounds. Because agreements follow existing spend, ESI structurally advantages vendors who already have DoD footprint. A new entrant doesn't get an ESA and then build a base; it builds a base and may then get an ESA.

‍

An ESA is not an order. The DFARS best-value test and waiver path mean holding an agreement puts you in the default path, not at the finish line.

‍

Finding the work

Getting on an ESI agreement is a multi-year play. Seeing the opportunities that flow through ESI, CHESS, SEWP, and the ELAs is a today problem — and most of it never appears on SAM.gov.

‍

RFQs against BPAs and catalog agreements are issued through eBuy, SEWP's quote tool, and component-level systems. Award and modification data that tells you which agreements are actually producing volume sits in yet another place. For a software company trying to figure out where its product is already being bought, and by whom, that fragmentation is the actual obstacle.

‍

Govly tracks opportunities across federal vehicles including SEWP and GSA, surfaces the award history behind them, and gives publishers and their channel partners a shared workspace for the deals they're pursuing together — which matters when the vehicle is held by your reseller rather than by you.

‍

See what's moving on your vehicles →

‍

Frequently asked questions

What is DoD ESI? The DoD Enterprise Software Initiative is a Department of Defense program, led by the DoD CIO, that negotiates enterprise-wide agreements for commercial software and software maintenance. DFARS 208.7401 defines it as "an initiative led by the DoD Chief Information Officer to develop processes for DoD-wide software asset management."

‍

Is DoD ESI mandatory? Not absolutely. DFARS 208.7402 requires DoD buyers to fulfill commercial software requirements in accordance with ESI, and PGI 208.7403 requires them to check DoD inventory and existing ESAs first and to buy through an ESA when it represents best value. But the regulation states that "ESI does not dictate the products or services to be acquired," and a designated management official can waive the requirement. The Army is stricter: AFARS requires use of ESI, J/ELA, or CHESS contracts regardless of dollar value.

‍

What is an Enterprise Software Agreement (ESA)? A contract or agreement used to acquire commercial software or related services under ESI. ESAs take multiple legal forms — BPAs against GSA Schedules, multiple-award BPAs competed on eBuy, Agency Catalogs on NASA SEWP, standalone IDIQs, and CETAs.

‍

How do I get a DoD ESI agreement? There is no open on-ramp or published unsolicited proposal process. ESI initiates agreements based on aggregated DoD demand, then competes them or makes a justified direct award. Practical steps: get on GSA MAS or SEWP first, build demonstrable DoD spend, engage your component's Software Product Manager through esi.mil, or partner with a reseller that already holds an ESA.

‍

Can a reseller sell under a DoD ESI agreement? Yes — and in most cases the ESA holder is a reseller rather than the publisher. Carahsoft, TD SYNNEX Public Sector, Groundswell, immixGroup, and others hold agreements on behalf of software publishers.

‍

Is DoD ESI a contract vehicle like SEWP or GSA Schedule? No. ESI is a sourcing program that builds agreements on top of those vehicles. Some ESAs are BPAs against GSA Schedules; at least one runs as an Agency Catalog on NASA SEWP.

‍

Who can buy through DoD ESI? DoD components worldwide, the Intelligence Community, the U.S. Coast Guard, and contractors authorized under FAR Part 51.

‍

What is the difference between DoD ESI and the Software Acquisition Pathway? ESI governs buying commercial off-the-shelf software licenses and maintenance. The Software Acquisition Pathway, along with CSOs and OTAs, governs custom software development and prototyping. A COTS vendor uses ESI; a company building software for DoD uses SWP.

‍

What is Army CHESS and how does it relate to ESI? CHESS (rebranding to "Digital Market") is the Army's Software Product Manager for ESI and separately the Army's mandatory source for commercial IT. Army buyers must use J/ELA, ESI, or CHESS contracts regardless of dollar value, and going outside requires a Statement of Non-Availability.

‍

Is DoD ESI now DoW ESI? Both names are in use. Following Executive Order 14347, "Department of War" is a secondary name for the department, and esi.mil has rebranded accordingly. The DFARS still refers to the DoD Enterprise Software Initiative. Same program.

‍