osFoundry / Platform
Build artefacts
Every build produces signed artefacts — versioned, downloadable, retained for as long as you need.
What it is
Build artefacts are the concrete outputs osFoundry keeps every time it builds something for you — an app, a container image, or compiled code from a project. Instead of a build being a one-time event that vanishes when the log scrolls away, each run leaves behind a durable, named record: the thing that was produced, tied to the exact version it came from. That artefact is what you download, hand off, roll back to, or deploy again later.
Inside osFoundry the flow is straightforward. You trigger a build from a project or app in your workspace, the build runs, and on success it emits a signed artefact. Signed means the artefact carries a cryptographic signature so you can verify it is the exact output osFoundry produced and that it has not been altered since. Versioned means each build is a distinct entry rather than overwriting the last, so you always know which source state a given artefact corresponds to and can go back to an earlier one. Downloadable means the artefact is a real file you can pull out of the workspace — to run elsewhere, archive, or pass to a teammate. Retention is under your control: artefacts are kept for as long as you need them, not silently expired on someone else's schedule.
This matters because a build is only useful if you can trust and reproduce what it made. osFoundry is a bring-your-own-key, local-first workspace with no per-seat fees, so build artefacts fit the same model — your builds and their outputs stay in your workspace rather than being locked behind a vendor's proprietary registry, and signing plus versioning give you a verifiable chain from source to shipped output. It puts chat, agents, apps, code, and their build outputs in one place, so the artefact from a build is right next to the project that produced it.
Key capabilities
- Every successful build emits a signed artefact you can cryptographically verify was produced by osFoundry and left unaltered
- Artefacts are versioned per build, so each output maps to a known source state and earlier versions stay available to roll back to
- Download any artefact as a real file to run elsewhere, archive, or hand to a teammate
- Retention is yours to set — artefacts are kept for as long as you need them, not expired on a vendor schedule
- Builds and their outputs live in your local-first, BYOK workspace alongside the projects that produced them, with no per-seat fees
Use cases
- Developer shipping an app: build once, verify the signature, download the exact artefact, and deploy it knowing it matches the source it came from
- Team lead handling a rollback: return to a prior versioned artefact instead of rebuilding from scratch when a new release misbehaves
- Solo builder keeping records: retain artefacts long-term as a downloadable history of what was released and when
Frequently asked questions
What does it mean that build artefacts are signed?
Each artefact carries a cryptographic signature, so you can confirm it is the exact output osFoundry produced during that build and that it has not been tampered with afterward. It gives you a verifiable link between the source you built and the file you ship.
How long are build artefacts kept?
For as long as you need them. Retention is under your control rather than fixed to a vendor's expiry schedule, so you can keep artefacts around for audit, rollback, or archival for however long that matters to you.
Can I download a build artefact and use it outside osFoundry?
Yes. Every artefact is a real, downloadable file. You can pull it out of your workspace to run elsewhere, archive it, or pass it to a teammate — it is not locked to a proprietary registry.