osFoundry / Platform
App version history
Every deploy is a versioned snapshot. Rollback in one click — code, schema, secrets all together.
What it is
App version history in osFoundry treats every deploy as a complete, immutable snapshot rather than a loose set of file changes. When you ship a version of an app or backend, osFoundry captures the code, the database schema, and the secrets configuration as one bundle and stamps it with a version. Nothing is deployed in pieces, so nothing can drift out of sync: the schema a build expects and the secrets it reads are pinned to the same snapshot as the code that uses them.
Because each version is a coherent whole, rollback is a single click. You pick a previous snapshot and osFoundry restores that exact state — code, schema, and secrets together — instead of asking you to hand-revert a migration in one place and a config value in another. This is the failure mode versioning usually leaves open: the code reverts but the database is still on the new schema, or a rotated secret no longer matches. Snapshotting all three together closes that gap, which is what makes a one-click rollback trustworthy under pressure.
This lives inside osFoundry's Apps & Backend surface, part of the same BYOK desktop workspace where you run chat, agents, code, and data. There are no per-seat fees and no reseller markup on the models you connect; version history is simply how deploys are recorded so that shipping a change and undoing it are both safe, ordinary actions rather than events.
Key capabilities
- Every deploy is saved as an immutable, versioned snapshot instead of an in-place overwrite
- Each snapshot bundles code, database schema, and secrets so the three never drift apart
- Roll back to any previous version in one click, restoring all three together
- Browse the full deploy history to see what shipped when and compare versions
- Part of osFoundry's Apps & Backend surface — no per-seat fees, bring your own keys
Use cases
- Solo builder: ships a schema change that breaks production and rolls back to the last working snapshot in one click, code and database together
- Small team: reviews the deploy history to see exactly which version introduced a regression before deciding what to fix
- Agent developer: iterates fast on a backend, knowing every deploy is a restore point they can return to without hand-reverting migrations or secrets
Frequently asked questions
What exactly gets captured in each app version?
Each deploy snapshots three things as one unit: your application code, the database schema, and the secrets configuration. They are versioned together, so a given snapshot always represents a consistent, deployable state rather than partially updated pieces.
Does rolling back also revert my database schema and secrets, or just the code?
All three. A rollback restores the full snapshot — code, schema, and secrets — so you don't end up with new-schema code running against an old database or a rotated secret that no longer matches. That's the point of bundling them into one version.
Where does app version history fit in osFoundry?
It's part of the Apps & Backend surface in the osFoundry desktop workspace, alongside chat, agents, code, knowledge, and data. Versioning is built into how deploys work, so every ship is recorded and every previous version stays available to roll back to.