osFoundry / Platform
Deployments
Every build, every deploy, every rollback. Status pulses, logs stream live.
What it is
Deployments is the Code & Build view in osFoundry that turns shipping into something you can actually watch. Every build, every deploy, and every rollback shows up as a record with a live status indicator, so instead of guessing whether your last push made it out, you see it move from queued to building to live. Status pulses on the entries that are still in flight, and the moment a step runs, its logs stream into the panel line by line rather than appearing only after the job finishes.
Because osFoundry runs on your desktop and connects to your own infrastructure and keys, Deployments sits next to the code, apps, and agents it ships from instead of behind a separate CI dashboard in someone else's cloud. When a deploy goes wrong, you don't dig through a web console to reconstruct what happened. You open the run, read the streamed logs where it broke, and roll back to a known-good version from the same list. Each deploy stays in the history, so a rollback is picking a previous build rather than reverse-engineering one.
This matters because the slow part of shipping is usually not the deploy itself, it's the not-knowing. A pulsing status and a live log feed collapse the gap between "I pressed deploy" and "I know what it did." Kept in one local-first workspace with no per-seat fees and no reseller markup on the compute underneath, the build-deploy-rollback loop lives where the rest of your work already is.
Key capabilities
- See every build, deploy, and rollback as a tracked record with its own status and timeline
- Live status pulses on in-flight runs so you know at a glance what is still building or shipping
- Logs stream line by line as each step executes, not dumped only after the job ends
- Roll back by selecting a previous known-good build from the deploy history, no manual reconstruction
- Runs on your desktop against your own keys and infrastructure, no per-seat fees or reseller markup
Use cases
- Solo developer: pushes a change and watches the build move to live in real time instead of refreshing a separate CI page
- On-call engineer: a deploy breaks in production, so they read the streamed logs at the failure point and roll back to the last good build from the same list
- Small team shipping an internal app: keeps the whole build-deploy-rollback history in one local workspace next to the code and agents that produced it
Frequently asked questions
Can I roll back a bad deploy?
Yes. Every deploy is kept as a record in the history, so rolling back means selecting a previous known-good build rather than rebuilding or reconstructing one by hand.
Do I see logs while a deploy is running, or only after it finishes?
While it runs. Logs stream in line by line as each step executes, and the status indicator pulses on runs that are still in flight, so you can watch progress instead of waiting for a final dump.
Where does the build and deploy actually run?
osFoundry is a bring-your-own-key desktop workspace, so Deployments works against your own infrastructure and keys. You pay for the underlying compute directly with no reseller markup, and there are no per-seat fees.