pygeoapi provides an off the shelf solution for serving OGC APIs like Features, Maps, Tiles, or Environmental Data Retrieval from your organization’s existing data including GeoPackage, PostGIS, Zarr, GeoParquet, shapefiles, and many more. Pygeoapi can be deployed on its own or be integrated into existing API servers written with Flask, Starlette or Django. As such, pygeoapi offers many ways to tweak its performance depending on use case. We will begin the talk with a general introduction to pygeoapi and how it can be used to simplify OGC API deployment in your organization. We will then go over the high level internals of pygeoapi and best practices for scaling your deployment. Topics will include horizontal scaling in containerized environments, caching strategies, connection pooling, and best practices when creating your own custom provider extensions to pygeoapi.