How Foundry products work

The source-governed lifecycle behind Foundry products.

SectionStart here

AudienceBuyers, reviewers, operators

Public safeNo private credentials

Lifecycle

A product moves from idea to source plan, package, sample/schema evidence, QA gate, marketplace or public page, API/catalog exposure, and finally buyer request or integration.

Readiness states

Preview means a product is discoverable but still needs review or evidence. Ready means the page has enough public-safe metadata, sample/schema evidence, and delivery context for evaluation. Published means the external delivery surface is available where that marketplace supports it.

Why cached artifacts matter

Public docs and pages read generated payloads. That keeps the public site fast and prevents accidental exposure of internal tools, credentials, or provider responses.