Adding doc on Chainguard Catalog Starter#3060
Adding doc on Chainguard Catalog Starter#3060SharpRake wants to merge 6 commits intochainguard-dev:mainfrom
Conversation
Signed-off-by: Mark Drake <mark@chainguard.dev>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: Mark Drake <mark@chainguard.dev>
Signed-off-by: Mark Drake <mark@chainguard.dev>
|
We are no longer including Custom Assembly at all: "Users also get access to one image customized with Custom Assembly, allowing them to add extra packages or custom certificates directly into the image." "Additionally, you can use Chainguard’s Custom Assembly tool to customize one image." "These container images are also covered by" - should this be more clearly "identical to" or "the same as" "The free plan supports a single user account in the Chainguard Console for your organization. You can still integrate images into CI/CD and production using tokens, but you cannot invite other users to your organization, nor can other users pull your selected containers." Reid, Ron, Anushka and I decided to change how we refer to this restriction more clearly as "No User Management". Meaning, you don't get to add/remove users and you don't get RBAC. "Catalog Starter does not include the ability to upload and host your own custom images in Chainguard’s registry. You consume Chainguard-provided images only." - is this unnecessary since we do not have this functionality today? |
Signed-off-by: Mark Drake <mark@chainguard.dev>
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Documentation — new article
Adds a new doc explaining Chainguard Catalog Select, a free five-image trial offering for prospective customers to evaluate Chainguard Containers before committing to a paid plan.
What should this PR do?
resolves https://github.com/chainguard-dev/internal/issues/5696
Why are we making this change?
Catalog Select is a new product offering that needs documentation so prospects and internal teams have a clear, canonical reference for what it is, how it works, its limitations, and how it differs from paid plans. Without this doc, potential customers have no self-service resource to understand the offering's scope and terms.
What are the acceptance criteria?
How should this PR be tested?
Note: The two sign-up form links in the article body are currently empty (the request form and this form). These need to be filled in before the PR is ready to merge.