18F: Digital service delivery

cloud.gov is now FedRAMP Authorized for use by federal agencies

By Britta Gustafson , James Hupp , Bret Mogilefsky , Will Slack on February 2, 2017

We’re delighted to announce that cloud.gov is now FedRAMP Authorized, which enables agencies to quickly transition their web-based services to efficient and easy-to-use cloud hosting. FedRAMP Authorized status marks completion of a comprehensive security and compliance assessment that enables federal agencies to start using cloud.gov with significantly reduced effort. cloud.gov is a government-customized hosting platform that takes care of technical infrastructure and security compliance requirements.

Facts about publishing open source code in government

By Britta Gustafson , Will Slack on August 8, 2016

We’ve put together a list of facts and references that will help you build the case for open source development in your team or agency and bust myths about using public code repositories. This post is based on our experiences at the federal level, but we hope it’s helpful for anyone working in government.

open source tools you can use

cloud.gov is full steam ahead on its FedRAMP assessment process

By Bret Mogilefsky , Diego Lapiduz , Britta Gustafson on July 18, 2016

Here at 18F on the cloud.gov team, we’re working toward getting cloud.gov assessed as FedRAMP compliant, with lots of interesting progress — so here’s an update, including our FedRAMP Ready status!

cloud.gov platforms devops

Take our code: 34 reusable projects from 18F

By Britta Gustafson on April 6, 2016

We encourage you to adapt 18F open source projects for your work and personal purposes, whether you’re a fellow federal employee or outside government. We’ve put together a list of some 18F repositories that might be especially useful to you.

tools you can use open source

18F's New Year's resolution: Be even more open

By Melody Kramer , Britta Gustafson on January 7, 2016

We've been thinking a lot lately about our role within the open source community, and it's our 2016 resolution to increase the number of non-employee contributors to our projects, including: contributors with little previous experience with open source, and contributors to documentation, bug filing, and other non-coding work.

open source how we work