EverCV now covers 110 signal sources — including Kubernetes, Helm, dbt, and Octopus Deploy

When I started building EverCV, the first integrations were obvious: GitHub, Jira, Linear, Slack. The tools every engineer mentions in a job interview. Commit history, ticket throughput, PRs merged.

But platform engineers don't land their best work in tickets. They ship infrastructure. A Kubernetes deployment that brings a service to 99.95% availability doesn't live in your GitHub commit history — it lives in a rollout log nobody saves.

Today EverCV adds eight new signal sources to close that gap.

What's new: sources 103-110

Container and Kubernetes

Kubernetes deployments. EverCV watches your k8s cluster's Deployment resources and records when the Available condition is met. A successful rollout — service A scaled from 2 to 8 replicas, or a new image pushed to prod — is now a dated work signal in your CV.

Helm chart releases. Helm stores release history as Kubernetes secrets. EverCV reads the modifiedAt annotation and records each chart deployment: nightdesk/agent v1.4.2 → production. If you maintain a set of Helm charts for internal services, that work now shows up.

AWS ECS deployments. ECS service updates that reach PRIMARY status are now tracked. For teams running containerized workloads on ECS — especially common in AWS-first shops — this closes a gap that even CodeBuild couldn't cover.

Infrastructure as Code

AWS CloudFormation stack deploys. CREATE_COMPLETE and UPDATE_COMPLETE stack events are now signal sources. Stack deploys are some of the highest-stakes infrastructure work an engineer does — and they were invisible to every CV tool until now.

Data Engineering

dbt Cloud job runs. dbt Cloud's successful pipeline runs are now EverCV signals. If you're shipping data transformations daily — 30 models, 500 tests, 3-minute run — that's engineering work. It belongs in your CV.

Prefect Cloud flow runs. Prefect workflow completions round out the data engineering picture. Combined with dbt, EverCV can now produce a coherent picture of a data engineer's daily output.

Code Quality

SonarQube quality gate passes. When a project clears SonarQube's quality gate — test coverage above threshold, zero new critical issues — EverCV records it. Code review work that results in a gate pass is now attributable.

Release Management

Octopus Deploy. For teams deploying Windows services, .NET applications, or multi-environment pipelines via Octopus, this closes the last major deployment gap. Octopus doesn't talk to GitHub or Jira; it talks to your servers. Now EverCV talks to Octopus.

Why these eight

Platform engineers and SREs consistently told me the same thing when I showed them early EverCV demos: "That's great for app developers, but my best work is invisible."

A cloud infrastructure migration isn't a PR. A Kubernetes cluster upgrade isn't a Jira ticket. Running an incident postmortem isn't a commit. These are the kinds of projects that make the difference between a senior engineer and a staff engineer, and they disappear from CVs within two years of being done.

EverCV's approach: if a tool emits a dated event that indicates work was done, that event becomes a CV signal. The 8 new integrations added tonight follow that rule precisely.

The full picture at 110

The integrations now span:

| Category | Sources | |---|---| | Code (VCS) | GitHub, GitLab, Bitbucket (PRs, commits, reviews, discussions) | | Tickets / PM | Jira, Linear, Shortcut, Asana, ClickUp, Trello, Monday, Azure DevOps, YouTrack, Wrike, Todoist, Coda | | CI/CD | GitHub Actions, GitLab CI, CircleCI, Buildkite, Travis CI, Jenkins, CodeBuild, Cloud Build, Heroku CI, Argo CD, Deno Deploy, Railway, Cloudflare Pages/Workers, Terraform Cloud | | Container / k8s | Kubernetes, Helm, AWS ECS | | IaC | AWS CloudFormation, Pulumi, Terraform Cloud | | Releases | GitHub/GitLab/Sentry Releases, npm, PyPI, Docker Hub, GitHub Packages | | Deployments | Vercel, Netlify, Render, Heroku, Fly.io, PlanetScale, Supabase, AWS Lambda, LaunchDarkly, Retool | | Data Pipelines | dbt Cloud, Prefect Cloud | | Code Quality | SonarQube | | Release Management | Octopus Deploy | | Time Tracking | ConnectWise, Autotask, Harvest, Toggl, Clockify, Tempo | | Incidents | PagerDuty, Sentry, Opsgenie, Incident.io, Datadog, Bugsnag, Rollbar, New Relic, Intercom, Statuspage | | Support | Freshdesk, Zendesk | | Observability | Datadog, Grafana, Snyk | | Docs & Content | Confluence, Notion, dev.to, Stack Overflow, Loom, Figma, Postman, Miro, Hashnode | | No-code | Airtable, Zapier, Make, Retool |

That's 110 sources across 60+ platforms. The CI/CD and deployment categories are particularly deep now — if your team deploys software, EverCV almost certainly already speaks the language of how you ship.

What's next

EverCV is in closed beta. If you're a platform engineer, SRE, or data engineer who wants to stop losing track of your best work, get early access.

The launch branch is waiting on domain registration and SAM deploy. If this resonates, the Show HN post goes live the moment the domain is live.