|
| 1 | +--- |
| 2 | +title: 'How to Pick Platform Engineering Tools in 2025: Essential Guide' |
| 3 | +author: Tianzhou |
| 4 | +updated_at: 2025/02/18 09:00:00 |
| 5 | +feature_image: /content/blog/platform-engineering-tools-essential/banner.webp |
| 6 | +tags: Industry, Hidden |
| 7 | +featured: true |
| 8 | +description: Introduce the essential tools for platform engineering. Covering code hosting, CI/CD, observability, resource provisioning, and secret management. |
| 9 | +--- |
| 10 | + |
| 11 | +<HintBlock type="info"> |
| 12 | + |
| 13 | +The post is updated regularly and focuses solely on tools. It does not cover infrastructure components like Kubernetes, PostgreSQL, Kafka, Elasticsearch. It also does not cover collaboration tools like Slack, Notion, Jira, Linear. |
| 14 | + |
| 15 | +</HintBlock> |
| 16 | + |
| 17 | +Platform engineering adoption has surged in recent years. To better understand the landscape, we interviewed over 100 platform teams about their challenges and the tools they rely on. Drawing from these insights and our own experience, we have curated a list of essential platform engineering tools. This is the first of a two-part series exploring the tools that power modern platform teams: |
| 18 | + |
| 19 | +1. Platform Engineering Tools: Essential Guide (this one) |
| 20 | +1. Platform Engineering Tools: Advanced Guide (TBD) |
| 21 | + |
| 22 | +--- |
| 23 | + |
| 24 | +In this essential guide, we've selected tools that are truly fundamental to platform engineering. Our focus is on quality over cost, as we believe that when building a platform team, prioritizing best practices is key. Opting for the highest-quality tools ultimately proves to be more cost-effective in the long run. Let’s dive in. |
| 25 | + |
| 26 | +In this essential series, we will cover the following tools: |
| 27 | + |
| 28 | +- [GitHub - Code Hosting and CI/CD](#github) |
| 29 | +- [Datadog - Observability](#datadog) |
| 30 | +- [HashiCorp Terraform - Resource Provisioning](#hashicorp-terraform) |
| 31 | +- [HashiCorp Vault - Secret Management](#hashicorp-vault) |
| 32 | + |
| 33 | +## GitHub - Code Hosting and CI/CD |
| 34 | + |
| 35 | +Pros: |
| 36 | + |
| 37 | +- User familiarity (who doesn't use GitHub?). |
| 38 | +- Integrated and powerful CI/CD capabilities with GitHub Actions. |
| 39 | +- Integrated security like CodeQL, Dependabot and a wide range of 3rd party tools. |
| 40 | +- AI advancement with Copilot. |
| 41 | +- Good documentation and developer experience. |
| 42 | + |
| 43 | +Cons: |
| 44 | + |
| 45 | +- No free tier for private repositories and self-hosted option. |
| 46 | + |
| 47 | +Comments: |
| 48 | + |
| 49 | +GitLab was once the go-to choice for many platform teams, but we've observed a growing shift towards GitHub in recent years. We covered the comparison in a more [detailed post](/blog/github-vs-gitlab/). |
| 50 | + |
| 51 | +Unless you're working with a limited budget and need the self-hosted option upfront, we recommend GitHub over GitLab. |
| 52 | +That said, starting with GitLab and migrating to GitHub is still a viable path. Just keep in mind the potential challenges of becoming too reliant on GitLab CI and its API (an LLM can certainly assist the migration). |
| 53 | + |
| 54 | +## Datadog - Observability |
| 55 | + |
| 56 | +Pros: |
| 57 | + |
| 58 | +Other than the Cons below. |
| 59 | + |
| 60 | +Cons: |
| 61 | + |
| 62 | +- Expensive. |
| 63 | +- No self-hosted option. |
| 64 | + |
| 65 | +Comments: |
| 66 | + |
| 67 | +Many people have a love-hate relationship with Datadog. It's an all-in-one observability platform, but it can also be very expensive due to its per-host pricing model. But we think it's a good investment for the right team. For small-to-medium teams, infrastructure costs are typically manageable, with product-market fit being the key focus. For larger teams, there’s often more flexibility to explore alternatives or negotiate better pricing with Datadog. |
0 commit comments