Complete our quick 5-question survey to help us improve our content.

  1. Service manual
  2. Communities
  3. Technology community (technical architecture)

The cross-government technical architecture community exists to:

  • share knowledge and information about technical architecture for government services
  • discuss and challenge the way technical architecture works for government services
  • bring together people from across government with an interest in technical architecture

Who the community is for

You might be interested in this community if you’re involved in any aspect of technical architecture, for example:

  • choosing technology (eg languages, frameworks or software) for a service
  • giving technology advice and being the technical voice in conversations about service design
  • making a service secure
  • testing the security and performance of a service

You don’t need to be a technical architect to join.

Join the community


Join the UK government Slack, which has several technology-related channels (you can create a Slack account using your government email address).

Training and events

The community holds regular:

  • cross-government architecture lunches
  • cross-government architecture drinks

These alternate on a monthly basis.

You can find information about meetups in the technical architects Google group.


The technology at GDS blog discusses how GDS builds, assembles and runs its software.

Technical architecture in the Service Manual

These guides show what we currently believe to be best practice for technical architecture in government:

Help us keep the Service Manual up to date by:

  • contributing to community discussions
  • telling us if something is wrong or out of date using the feedback link at the top of each guide
Last update:

Removed link to technical architects Google group, which no longer exists.

  1. Added guide to 'Moving away from legacy systems'.

  2. Guidance first published