Krosoft now has a blog because the long stories behind software need a place to live.
Some work is visible only as a shipped feature, a maintained app, or a migration that quietly went right. What gets lost is the path: why a product survived, how a platform shift changed the choices, what old code taught us, and where stewardship mattered more than novelty.
This blog is a place for product memory: the people who kept small tools useful, the constraints that shaped real decisions, and the lessons from maintaining software across eras.
Posts will trace product lineages, explore Atlassian apps, automation, and product architecture, or document what changed after shipping. Smaller notes will preserve a decision, a lesson, or a bit of history before it becomes invisible.
Krosoft builds tools for time. Durable software is not only a matter of frameworks, APIs, or releases. It is also a matter of care, migration, judgment, and remembering why something was worth carrying forward.
As Krosoft takes shape, we want to leave a useful trail of the reasoning behind the work, so the next chapter can learn from the last.