The Infrastructure team helps 18F navigate the “federal compliance architecture.” This work applies to much more than technology: it applies to our entire operation, including how we work inside the law, how we secure our systems, how we collect data from the public, and how we spend money.

While Team Ops focuses on what would normally be considered the “back office” — financial matters, procurement, and space operations — Infrastructure focuses on our digital infrastructure and development methodologies. Both teams work closely together, and there are many areas in which we have joint ownership.

The Director of Infrastructure, Noah Kunin, goes into more depth in his class, but the summary is that we have three rules:

  1. If you don’t see us doing something already, and you can’t find express authorization to do it, please ask first. We promise to get you an answer very quickly.
  2. Either everyone in the public can participate, or no one can. You alone cannot decide why Person A has access to something but not Person B.
  3. You cannot spend a single penny, create the expectation that a penny will be spent, or cause a penny to be spent, unless Congress has appropriated the funds.

18F Infrastructure’s work is closely related to your Ethics and Legal training. The difference is that the Infrastructure team is mainly concerned about the behavior of systems we use or build, while that ethics/legal training (and the broader GSA legal team) focuses on what you as a person can and cannot do.

If you have any questions, you can find us on Slack in #infrastructure, #pra, and #research.

Joining the Infrastructure Team

Welcome to the 18F Infrastructure team — we’re happy you’re here! We’ve compiled a set of helpful tips to get you started. We’ll update this guide as we receive feedback, so don’t be shy to share your thoughts.

Who we are

Members of the Infrastructure team bridge multiple disciplines: software development, system administration, operations, and security. The team supports, informs and glues together the activities of every team within 18F. For more information, see this full list of skills by staff member.

If you are technical, you may also want to take a look at the Engineering onboarding page.

Leads and management

See the org chart.

What we do

The Infrastructure team provides guidance and support for the entire lifecycle of product development at 18F.

  • Platform as a Service. helps 18F quickly and easily develop projects and designs on a full-featured self-service platform.
  • Security & Compliance. See the Compliance Toolkit.
  • Infrastructure as a Service. Provide a straightforward option for customer agencies to buy Amazon Web Services as part of an IAA with 18F.
  • Production Support.
  • Tools & Communication. We manage the core tools that 18F depends on for communication and collaboration.

How we work


  • Daily Standup
  • Bi-Weekly Leadership Sync
  • Bi-Weekly Sprint Retrospective & Planning

Communication channels

  • Slack channels:

    • #infrastructure - Escalate general operational issues to our attention.
    • #g-devops - Discuss DevOps as a capability and skillset.
    • #devops-public - A public channel to discuss DevOps topics with a broad community of public and private sector technologists.
  • Mailing lists:

    • - This is the alias used to distribute status messages and notices relating to most Infrastructure-managed services.
  • GitHub repo - Open an issue to formalize a request for changes or assistance from our team.


Here are some common tools we use, how we use them, and how you can get access to them. If you can’t find the information you need in the chart below, get in touch with your lead; they’ll be able to point you in the right direction.


Stuff we maintain