Heptio
Heptio was a Seattle-based cloud-native software company founded in 2016 by Craig McLuckie and Joe Beda, two of the original co-creators of Kubernetes, to help enterprises adopt and operate Kubernetes. It built a suite of widely used open-source Kubernetes tools including Ark (later renamed Velero) for backup and restore, Sonobuoy for conformance testing, Contour as an Envoy-based ingress controller, ksonnet, and Gimbal. Heptio was acquired by VMware in November 2018 and folded into the VMware Tanzu portfolio; the company brand was retired and most of its open-source projects were migrated from the github.com/heptio organization to github.com/vmware-tanzu. This profile is preserved as a historical/defunct-company record in the API Evangelist network.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Heptio the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Heptio scores 7.4/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Heptio
Each block below is one kind of artifact we hold for Heptio. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Heptio — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/heptio · machine-readable index on apis.io