Docs
Everything you need to ship on Foundry: previews, builds, cloud access and releases.
Point Foundry at a repository URL and we build a disposable preview. The fetcher reads your manifest server-side from the workspace network:
- POST /api/previews — JSON body with repo_url; authenticated manifest endpoints can add method and headers.
- The web form on the Previews page — same fetcher, with a preview of the response.
Fetch policy: http/https sources only. Redirects are followed. Fetch outcomes are kept per preview.
Builds run with the build-runner role. Credentials are fetched at run time from the instance metadata service (IMDSv2 — v1 requests are refused); the role's session document is what your tooling should configure.
aws --endpoint-url $FOUNDRY_CLOUD s3 ls
Staging images are published to the internal registry by the pipeline identity. Promotion to the watched tag goes through the deploy agent's trigger (fleet ops token); the agent rolls verified digests out within its poll interval. Production promotion goes through signing and the release docket.