The Defense Intelligence Information Enterprise (DI2E) is driven, championed and funded out of the Office of the Undersecretary of Defense for Intelligence (OUSD(I)) as the unifying construct between Department of Defense (DoD) and Intelligence Community (IC) intelligence activities. The portfolio of programs and efforts formally under the DI2E umbrella includes the Distributed Common Ground System (DCGS) Family of Systems (FoS), Combatant Command (COCOM) Joint Intelligence Operations Centers (JIOC), and US Battlefield Information Collection and Exploitation Systems (US BICES).

In 2012, a memorandum was signed out by Michael Vickers giving the National Reconnaisance Office (NRO) lead acquisition authority to drive the framework which structures DI2E activities. The DI2E Framework, which includes the DI2E Reference Architecture, DI2E Developer Tools, DI2E Clearinghouse, and DI2E Storefront is thus executed out of NRO.

The DI2E Developer Tools provide an open development environment for the defense and intelligence community, offering a full suite of popular, widely used development tools.  Project teams are able to establish cross-team efforts to support development, integration, and test needs.  The tools provide documentation and design artifact hosting, issue tracking, and project collaboration, and support software development lifecycle activities.  Aligning with Office of Acquisition, Technology, and Logistics (AT&L) Open Systems Architecture guidance, the DI2E Developer Tools provide ready access and accessibility to government-owned capabilities.  It has the following immediate benefits:

  • Reduce routine procurement of closed development environments on a costly contract-by-contract basis; infrastructure avoidance
  • Cross-program developer coordination; start to reduce stove-pipes
  • Promote development in the open, vice in a closed ecosystem
  • Government developed code on government resources

In adherence with ITAR restrictions, all users of the DI2E Developer Tools are required to have US citizenship. This requirement is necessary for both the user access to the Developer Tools as well as the access DI2E DevCloud VMs. Accounts can be requested at and projects at

We support a growing number software development and project management groups. Some are actively conducting agile software development, while some are less agile. Our suite of tools can be seen at  Many teams use DI2E because their work involves many different DoD organizations and it is impossible/impractical for them to allow distributed access; DI2E enables this collaboration.

Since there are many efforts that sit on the peripheral of DI2E efforts, we allow any DoD effort to set up a project at no cost as long as they are willing to open up their project to the bigger community and support the movement toward being more open and visible with their efforts. As we continue to mature within the DI2E community, we aim to further promote the DI2E ideals of open architecture, open development, sharing and reuse, starting as early in the development life cycle as possible. As such, we are slowly maturing to be able to add additional gates into our DI2E Developer Tools onboarding process to encourage such sharing. Therefore, we strongly encourage programs to allow the broader community full read access to your project. In the near term, we plan to officially make that a requirement, managed only by exception.

With regard to network fabrics where we reside, we are currently only on the unclassified network. We are planning to have a presence on the SIPR and JWICS fabric as well, but wish to plan smartly for this.  We are currently in planning discussions with other community members who provide similar capabilities, and working to resource this appropriately.

For additional environment details, please reference the DI2E Developers Environment Wiki (DI2E account required).

For other specific questions or information needs, please follow up with

Need a DI2E Account 

Please follow these instructions.