An enterprise Platfom Tools and Technology team.

Autotelic worked with this Enterprise's internal Platform Tools & Technology (PTT) team, across multiple projects in a multi-year engagement.

Federated GraphQL API

We developed a federated GraphQL (GQL) API within the PTT tools ecosystem to consume multiple sources downstream enterprise data and expose it in a developer friendly but secure and performant way. We built developer tooling for rapid implementation of GQL APIs by internal product teams, as well as a gateway for federating those APIs across the business.

We documented best practices for the tools, preformaned internal advocacy for adoption , as well as customer consultancy and support across the broader enterprise.

Kong Gateway Pilot Project

Following a decision to adopt the Kong gateway across the enterprise, a team from Autotelic was engaged to built out a "Steel thread" architecture proof of concept connecting internal GQL APIs through the gateway, with authentication and authorization, to a frontend.

We worked with multiple internal teams and stakeholders to design and prove out a Kong-based authentication layer for their platform infrastructure. The setup paired Kong as the API gateway with Kuma as the service mesh, running on GKE, connecting to a GraphQL API utilising the federated GraphQL API tooling we had previously built.

Web Application Starter Kit

We extended an existing web application template to support micro-frontend architecture - giving teams the flexibility to split their code into independently deployable frontends while still working from a single monorepo. The goal was to enable teams to make changes to individual frontends and ship them fast, without requiring a full-scale re-deployment of the entire application.

Using Webpack module federation alongside Next.js and the existing WASK tooling, we built a new template where an application shell could seamlessly consume multiple micro-frontends, each with its own automated deployment pipeline. We architected it to be fully composable so the micro-frontends built in one WASK shell could be exposed for consumption by other WASK shell applications across the org - reducing duplication and opening the door for cross-team collaboration. Because the core framework remained Next.js, existing WASK applications already in production could convert to the new architecture via CLI tooling based on their internal timelines and requirements.

Content as a Service (CAAS)

We designed and built a structured content API that would unify Contentful-based content management across multiple spaces. The challenge was making structured content discoverable and accessible to internal teams while maintaining a clean developer experience. Building on our existing work with GQL API tooling and the federated GraphQL gateway, we architected a solution that aggregated Contentful's generated GraphQL schemas at build time, enriched them with Enterprise-specific metadata, and exposed everything through a federated graph.

The technical implementation centered on a platform GQL API service behind a federated GQL Gateway. We set up Contentful migration scripts with a GitHub Action workflow -so content model changes could be version-controlled and deployed automatically on merges to main. Following the innersource (open-source within an enterprise) model we'd helped to establish for other projects within the business, we configured internal repository visibility to enable contribution from across the org while keeping things secure. The federated architecture meant additional content providers could be plugged in down the road without rearchitecting the whole system.

To drive adoption, we leaned into GraphQL Playground as an index and discovery tool. Developers could interactively explore the schema, run pre-built queries as documentation, and quickly locate the structured content they needed. This infrastructure and tooling reduced friction and made best practice the path of least resistance for teams consuming content across the organization.

OSS Fastify open-telemetry plugin

As part of our platform work, we proposed, developed and built a Fastify plugin for OpenTelemetry which we open-sourced and still maintain: https://github.com/autotelic/fastify-opentelemetry