Product · 6 min read
25 Releases for Trust: Consolidating FlowSharp (v0.70 → v0.79)
Between late July and early August we spent 25 releases on a single goal: making FlowSharp crash-proof, secure and fully auditable. Here is what changed under the hood.
Not all updates are created equal
Some updates ship new features. Others ship trust. Between late July and early August we released 25 consecutive versions, from v0.70 to v0.79, and for the first time most of the work had nothing to do with new visible functionality — it was about hardening everything running under the hood.
Few new features, a lot of attention to what actually matters once a process is live: consistency of rules, resilience to failures, verifiable security, governance with no gray areas. At FlowSharp we believe automation only works if the engine running it is reliable one hundred percent of the time, not eighty.
What you configure now holds everywhere
The first major shift is about consistency. Required fields, work-in-progress limits, response times, data dependencies: every rule declared in the designer is now enforced identically across every channel used to interact with a process — web interface, API, browser extension and AI agents.
Previously, small behavioral differences between channels could raise a fair doubt: 'does this rule really always apply, or only through the interface?'. Now the answer is simple: rules are rules, no matter how you access the process. That's a necessary foundation for teams increasingly delegating operations to external integrations or automated agents.
An engine designed to lose nothing
The second area of work targeted the resilience of the execution engine. Events that make up a process's history can no longer be lost. When two competing outcomes are possible, exactly one wins, with no ambiguous states left behind. And if something stops at the wrong moment — a restart, a timeout, a network glitch — the system automatically resumes right where it left off, with no manual intervention needed.
This kind of guarantee usually isn't visible: it doesn't show up on a screen, it doesn't make for an exciting announcement. But it's exactly what separates a tool that 'works in the demo' from one you can build business-critical processes on, day after day.
Security that's verified, not just claimed
We had FlowSharp go through independent security audits and strengthened the boundaries between workspaces, so that one organization's data can never mix with another's. Confidential data stays confidential not only on first save, but through every subsequent recalculation or reprocessing — a point that's often underestimated in automation platforms.
We also tightened protections around logs and permissions, cutting down the attack surface without adding friction for people using the platform every day. For us, security isn't a list of good intentions on a 'Trust' page — it's something that can be verified from the outside.
Real governance: no process quietly changing underneath you
A published process in FlowSharp is now immutable: once it's released, it can't be quietly altered underneath instances already running. Every historical event records the exact process version that generated it, and the audit trail has no gaps: you can always reconstruct precisely what happened, when, and under which rule.
Holding all of this together are over 7,000 automated tests run on every single release, before any change reaches customers. It's how we turn promises — 'your data is safe', 'your processes are consistent' — into something that gets mechanically checked, every single time.
Solid ground before running
Process automation only works if you can trust the engine running it. That's why, before shipping the next round of high-impact features we're already building, we chose to spend 25 releases consolidating the foundations: consistent rules across every channel, a crash-proof engine, third-party verified security, governance with no shortcuts.
It's not the flashiest part of product work, but it's what makes everything else possible. Measure, automate, grow: every step needs solid ground underneath it, and as of today FlowSharp stands on ground that's a little more solid.