diff --git a/README.md b/README.md
index a6407ea3a..6c85c598f 100644
--- a/README.md
+++ b/README.md
@@ -38,7 +38,19 @@ Note docker-compose runs the production docker image (RAILS_ENV=production) as t
 
 ### Infrastructure
 
-The cloud infrastructure running this application is set up using the [infrastructure repository](https://github.com/communitiesuk/mhclg-data-collection-beta-infrastructure)
+This application is running on [Gov PaaS](https://www.cloud.service.gov.uk/). To deploy you need to:
+
+- Contact your organisation manager to get an account in `dluhc-core` organization and in the relevant spaces (sandbox/production).
+- Install the cloudfoundry cli https://docs.cloudfoundry.org/cf-cli/install-go-cli.html
+
+- Login <br/>
+`cf login -a api.london.cloud.service.gov.uk -u <your_username>`
+
+- Set your deployment target (sandbox/production) <br/>
+`cf target -o dluhc-core -s <deploy_environment>`
+
+- Deploy <br/>
+`cf push dluhc-core --strategy rolling`. This will use the [manifest file](manifest.yml)
 
 
 ### Single log submission
diff --git a/doc/adr/adr-004.md b/doc/adr/adr-004.md
new file mode 100644
index 000000000..998cb7872
--- /dev/null
+++ b/doc/adr/adr-004.md
@@ -0,0 +1,20 @@
+### ADR - 004: Infrastructure Switch
+
+#### Gov PaaS
+
+The application infrastructure will be moved from the initial AWS set up to Gov PaaS. The initial expectation is to have a Gov PaaS account `dluhc-core` with 2 spaces `sandbox`, `production`.
+
+Sandbox will consist of 2 small instances (512M) and 1 tiny-unencrypted-13 Postgres instance.
+
+Production infrastructure sizing will be decided at a later time and once our account has been upgraded to a paid account.
+
+The reasoning for this is:
+
+- Department policy is to use Gov PaaS whenever possible
+- DLUHC does not have a lot of internal dev ops skills/capacity so by leveraging Gov PaaS we can leverage having most of the monitoring, running, scaling and security already provided.
+- We get a simpler infrastructure setup than the AWS setup we currently have
+- All of the infrastructure we currently require is well supported on Gov PaaS
+
+One potential downside is that data replication to CDS may be slightly more complicated as adding our database to a VPC requires the Gov PaaS support team to do that on our behalf.
+
+This also means the Github repository previously used for [Infrastructure](https://github.com/communitiesuk/mhclg-data-collection-beta-infrastructure) will be archived after this change goes in as it won't be needed anymore.