--- title: "Docker Verified Publisher Apps Are Now Self-Serve" url: https://daily.dev/posts/docker-verified-publisher-apps-are-now-self-serve-fckt3m4up source_url: https://www.docker.com/blog/docker-verified-publisher-applications-are-now-self-serve type: article source: "Docker" published: 2026-08-20T17:02:40.733Z updated: 2026-08-20T17:03:07.394Z tags: ["security", "docker", "containers"] reading_time: 4 upvotes: 1 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Docker Verified Publisher Apps Are Now Self-Serve **[Docker](https://daily.dev/sources/docker)** · 4 min read · 1 upvotes · 0 comments ## Summary Docker's Verified Publisher (DVP) program is now self-serve, letting software vendors apply directly through Docker Hub instead of going through the sales team. Applications are still manually reviewed by Docker, but onboarding is faster and simpler. Two pricing plans are available depending on growth needs. Verified publishers get a badge, priority search ranking, and analytics showing pull trends and which companies are using their content. The program now also covers non-image content like MCP servers, models, sandboxes, and agents, giving one consistent verification badge across all content types on Hub. Docker notes that pulling from verified publishers is one part of good security hygiene, alongside pinning digests, checking signatures, and scanning for CVEs. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I apply to become a Docker Verified Publisher now? Vendors can apply directly through Docker Hub's Explore page instead of contacting the sales team, which was previously required. Docker's team still manually reviews every application, but the process is now self-serve with a faster, lower-friction path. Once approved, applicants choose between two pricing plans and receive a checkout link. _daily.dev surfaces platform changes like this so teams evaluating container distribution options stay current._ ### What content types does the Docker Verified Publisher badge cover besides container images? The Docker Verified Publisher badge now applies uniformly across every content type on Docker Hub, not just container images. This includes MCP servers, models, sandboxes, and agents, giving publishers one review and one badge that carries across whatever they distribute next as Hub expands into supporting the broader agentic software stack. _daily.dev helps developers track how distribution platforms like Docker Hub evolve for agentic tooling._ ### Is pulling images only from Docker Verified Publishers enough to secure my container supply chain? No, publisher verification confirms who published the content but should be paired with other practices: reviewing the specific artifact pulled, pinning to digests rather than mutable tags, verifying provenance and signatures at the image level, and checking for CVEs. Verified status is one link in the trust chain, not a complete security guarantee. _daily.dev keeps container security practices like image pinning and provenance checks in view for engineers._ ## Similar posts on daily.dev - [Enhancing Trust in the MCP Ecosystem](https://daily.dev/posts/enhancing-trust-in-the-mcp-ecosystem-d7r6az0jw) · Docker · 3 upvotes · 0 comments - [Make zero CVEs your new default](https://daily.dev/posts/make-zero-cves-your-new-default-dk7ir7jif) · Docker · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#docker](https://daily.dev/tags/docker), [#containers](https://daily.dev/tags/containers) [View this post on daily.dev](https://daily.dev/posts/docker-verified-publisher-apps-are-now-self-serve-fckt3m4up)