About QCGO

QCGO is a cloud engineering publication built by and for platform engineers. We cover the infrastructure layer that production systems actually run on — not the marketing layer that cloud vendors talk about.

Our contributors operate multi-cloud environments, manage Kubernetes clusters at scale, and have opinions about Terraform module structure that they can back up with incident reports. We write about architecture decisions that survive contact with real traffic.

Founded in 2023, we publish long-form technical guides, architecture walkthroughs, and operational playbooks drawn from production environments.

Editorial Focus

Cloud ArchitectureMulti-region design, well-architected frameworks, cost optimization across AWS, GCP, Azure

Container OrchestrationKubernetes operations, service mesh, cluster management, resource scheduling

ServerlessLambda/Cloud Functions, event-driven architecture, cold start optimization

Infrastructure as CodeTerraform, Pulumi, CloudFormation, state management, module design

SRE PracticesSLO engineering, incident response, reliability tooling, capacity planning

Platform EngineeringInternal developer platforms, self-service infrastructure, golden paths

Editorial Standards

Every guide includes architecture diagrams, configuration examples, and cost implications where relevant. We test configurations before publishing them, and we version-pin our examples so they don't break six months later.

We don't publish sponsored content. Tool recommendations come from operational experience, not vendor relationships. When a managed service isn't worth the markup, we'll say so.

Contributing

We welcome guest contributions from engineers operating cloud infrastructure in production. If you've designed a system that handles real traffic, solved a scaling problem, or migrated something without an outage, we want to publish that. Contact our editorial team for contributor guidelines.