Get started

This is a typical journey for building a public-facing service with an in-house development team. It assumes you're building according to the Digital Service Standard and the Service Manual.

1. Check GOV.UK PaaS is right for you

Check your project’s needs against our current features and product roadmap.

2. Get a trial account

Request an account and add other team members, if appropriate.

3. Test using the platform

Work through the ‘Quick Setup Guide’ to deploy your first static site to test your connection. Read the orientation guide for your language to understand what PaaS already does for you.

Push some sample code for your project:

  • Use the platform marketplace to request “trial plan” services such as databases
  • Bind the services to your apps with the command line, then get your app to look at environment variables so it can connect to the services.
  • Make any other similar changes to your code to fit with the “12 factor app” principles for cloud scalability
  • Read our troubleshooting documentation to help you overcome any problems
  • Raise tickets with support if needed

Consider using a CI service such as Jenkins or Travis to run the app test/deploy pipeline

4. Start preparing for going live

  • Sign Memorandum of Understanding (MOU)
  • Move onto the appropriate paid tier given the needs of your service
  • Work with Finance colleagues to set up billing arrangements
  • Engage with your Information Security/Assurance colleagues to begin the process of accreditation; we can provide the PaaS documentation if they want to review it

5. Build towards private beta

  • Set up ‘spaces’ for each of your service’s environments - integration, staging, production - and link them to your CI service
  • Configure each environment with the proper backing services; these are often small and open in integration, but high-availability and encrypted in production
  • Turn on extra instances of key apps in production to get high availability
  • Continue development, trying out backing services and app ideas on a pay-as-you-go basis
  • Add user-provided services such as logging*, file storage*, antivirus etc.
  • Add features to integrate with any legacy APIs
  • Procure a monitoring and alerting solution* and add key metrics; these will be specific to your application and can’t be provided by the platform automatically

6. Enter private beta

  • Work with your SIRO to get authority to operate your service with small amounts of production data
  • Request a URL
  • Use the platform marketplace to turn on a CDN using your trial domain name
  • Move to an appropriate paid platform support plan
  • Iterate your application support model

7. During private beta

  • Iterate your service during private beta, based on real user feedback and any incidents
  • Your accreditor should want you to arrange penetration testing at various stages throughout development; always give us a week’s notice of this
  • Reconfigure or add new backing services as needed

8. After your beta service assessment

  • Change your support plan
  • Request a new URL and re-configure the CDN

9. Enter the public beta phase with your service

  • Continue to iterate your service based on user feedback and production needs, adding other services (e.g. autoscaling) where needed
  • Pass final assessment

10. After live assessment

  • Keep your dependencies up to date
  • Be ready to redeploy if there are vulnerabilities in language runtimes

* These services may be available through the PaaS platform in the future rather than as separate procurements; please see our roadmap for more information.