Our customers make the software that powers warfighting

Providing a suite of development and management services for the Defense Intelligence Information Enterprise that enables users to build valued software faster and more securely

Multiple Environments. Cross Domain.

Frequently Asked Questions


  • What are the "DI2E DevTools"?
  • 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 support software development life-cycle activities by providing:

    • Issue tracking
    • Project collaboration
    • Documentation and design artifact hosting

    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
  • Is there a cost or fee for using the DevTools or having an account?
  • The DI2E DevTools are available at no cost to any Intel-related project in the DoD or IC.
  • Who uses DI2E?
  • Every major command, service, and agency in DoD and the Intelligence Community. We support thousands of software development and project management groups. Some are actively conducting agile software development, while some are less agile. Many teams use DI2E because their work involves many different organizations and it is impossible/impractical for them to allow distributed access; DI2E enables this collaboration.
  • How does DI2E provide continuous integration support?
  • Here is an example of how DI2E tools provide continuous integration using the general flow of Plan → Code → Build → Test → Deploy (repeat):

    • Plan: We have the Atlassian tool suite with includes JIRA for issue tracking and management. Confluence hosts project wikis for communication and documentation. These project spaces are not open to the internet.
    • Code: We don't provide a cloud-based IDE, but we do provide source code management – Bitbucket is our most popular SCM tool as it provides Git functionality and we also have a subversion server
    • Build: We provide a Jenkins server to perform builds on. We have multiple managed build agents that perform builds for the majority of projects and can also run builds inside of docker containers if needed (example for this would be if you wanted to build with specific versions of OS tools or libraries you can create/specify a docker image for Jenkins to use and that will make sure that your build environment is consistent and portable from your developer workstations to our managed build nodes)
    • Test: In addition to any unit tests inside of your code we provide a SonarQube server that can identify issues and show test coverage regression.We host a Fortify SSC (Software Security Center) server. Customers can upload fortify scans to this server for reporting purposes. To make use of that your project would need to purchase a Fortify license.
    • Deploy: We offer artifact deployment servers, Sonatype Nexus 2 and Nexus 3 for projects to deploy their artifacts to. This includes development and released versions ranging from maven jars to nodejs packages, yum, and docker images.
  • On which network fabrics can I find DI2E DevTools?
  • The US-Only DI2E DevTools and Coalition DevTools are currently available on the open Internet. The Secret DevTools is available on SIPRNet and a similar environment is offered by our parent organization on JWICS.
  • Can DI2E host my application and/or can my project use DI2E's cloud services for hosting?
  • DI2E does not provide PaaS or IaaS services that allow projects to host their services or applications. The DevTools suite does allows projects to store build artifacts and binaries but does not allow any run-time hosting of them.

DI2E Projects

  • What is a DI2E Project?
  • DI2E uses a concept of 'projects' to determine resource and permissions separation within our hosted tools. Generally a project is directly related to a program of record although programs can have many different DI2E projects depending on their use-cases and needs. Each project within DI2E has a unique project key. The project key is used throughout all of the tools and also for specifying permissions.
  • What kinds of projects are allowed?
  • DI2E DevTools provides Hosted Projects that will be used either for development, sustainment, or support for a Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) capability by a DoD or Intelligence Community organization.
  • Are all DI2E projects visible and shareable?
  • A key goal of the DI2E Framework is to provide an open and public environment in order to promote collaboration and interaction which may result in reuse and shared best practices with other DI2E users. DI2E users have the ability to control privacy and access to their tools and content. However, by default, all projects are setup to be open/shareable to the DI2E community. DI2E helps projects move toward being more open and visible, and encourages all programs to promote the DI2E ideals of open architecture, open development, sharing and reuse, starting as early in the development life cycle as possible. However, each DI2E project can set its own visibility / sharing / permissions in each DevTool.

    All DI2E users have the ability to read general information about any project's name, description, and points of contact. This permits DI2E users to reach out and collaborate where it makes sense.

  • How can I request a DI2E project?
  • We use Jira to receive and process new project requests. Please consider these choices carefully when requesting your team project:

    • Project Name/Description. These are the most important sections which are typically not filled completely or clearly. Spell out acronyms and write a Project Name and Description that anyone or most can understand. All projects, whether public or private, are visible to entire community. Everyone can view basic information (e.g., project name, description, and POCs), so clear titles and descriptions are helpful.
    • Hosted Project Access. This field indicates the level of access for other DI2E users. The three options are the following:
      1. "All DI2E Account Holders." This is fully accessible by all DI2E users and is the default setting. Requesting to be private is by exception.
      2. "Some Project Information is shared with all DI2E account holders." The intent for this option is some information is public and some areas are private. The areas that are private could include new individuals who request access via the project owner.
      3. "Private." Project is not accessible to other DI2E users. However, like option two above, a DI2E user can still contact the project approver and request access or to engage in general collaboration.

    With these choices in mind users NEW to DI2E, can request a new project here: Submit a Project Request

    An existing DI2E user can request a new project here: Create a Project Request

DI2E Accounts

  • Who can get a DI2E user account?
  • DI2E supports three primary environments:
    • US Only: In adherence with International Traffic in Arms Regulations (ITAR) restrictions, all users of the US-Only DI2E DevTools are required to have US citizenship. This requirement is necessary for both the user access to the DevTools as well as the access DI2E-hosted Jenkins build nodes.
    • Coalition: The Coalition DI2E DevTools environment allows users from the United States, Australia, Canada, Great Britain, and New Zealand.
    • Secret: All users of the SIPRNet DI2E DevTools environment are required to have US citizenship.
  • How can I get a DI2E account?
  • All users of the US-Only DI2E DevTools are required to have US citizenship. We can immediately validate your citizenship electronically if you hold a DoD Common Access Card (CAC) or DoD External Certificate Authority (ECA) certificate. Cleared DoD employees and contractors can pass their citizenship information to us electronically using JPAS. Users with access to JWICS email can provide electronic proof of citizenship via JWICS. Finally, we accept appointments for users that need to validate their citizenship using government-issued documents. Choose the first possible option:

    If you have a DoD Common Access Card (CAC) or ECA certificate click here to create an account automatically.

    If you hold a DoD clearance, click here for instructions on passing your citizenship information via JPAS.

    If you have access to SIPRNet or JWICS email, click here for instructions on passing your citizenship information via JWICS email.

    If you have a passport or US birth certificate, click here for instructions re: scheduling an appointment.

Production Workloads (Virtual Machines)

  • Does DI2E provide infrastructure for hosting websites or applications?
  • Not at this time. DI2E provides virtual machines (Jenkins build nodes) that can be used to build and test software, but does not provide general purpose virtual machines or other hosting capabilities that would allow projects to deploy a website or application that external users could reach. Project teams need to acquire their own production hosting solutions.

Controlled Unclassified Information (CUI) / International Traffic in Arms Regulations (ITAR)

  • How do the DI2E DevTools meet the technical safeguards outlined in the DoD Instructions and NRO Directives to handle Controlled Unclassified Information (CUI) or subject to International Traffic in Arms Regulations (ITAR) information?
  • Answer: see this page.
  • How can DI2E user teams properly mark and protect information that may be Controlled Unclassified Information (CUI) or subject to International Traffic in Arms Regulations (ITAR) policies?
  • Answer: see this page.

Security / Accreditation

  • Are the DI2E DevTools Accredited?
  • Yes, DI2E DevTools is accredited by a US government organization. Our accreditation documentation, including our signed authorization letter may be found here (DI2E login/account required). Please contact DI2E Security.

Programmatic Support

  • I have additional programmatic questions. Who should I contact?
  • Please contact Greg (GM) Contreras.

Technical Support

  • How can I reach DI2E technical support?
  • DI2E Dev Tools support is available during business hours (8am-5pm), U.S. East Coast time. Response and resolution times are based on the availability of support staff.

    US-only DevTools

    Coalition DevTools

Contact Us

Interested in learning more? Start the conversation by emailing us at info@di2e.net.

Email Us

Need technical support? DevTools support is available during business hours (8am-5pm), U.S. East Coast time. Response and resolution times are based on the availability of support staff.