Looking for closure partners | wrapping up my async OS project
Hey everyone,
I’m writing this as a final note under my new Indie Hackers account.
Some of you might remember me as "Koni", the person who had been sharing async OS experiments and system design updates for months.
That account was restricted recently, so I’m closing this project from here instead.
After six months of building and testing an async operating system for sales and workflow automation, I’ve decided to wrap it up.
The project has reached its natural endpoint, and I’m stepping back from further development.
If anyone wants to fork, reference, or learn from the system’s structure before I archive it, feel free to reach out.
I’ll share access materials for a short time before the full shutdown.
It’s been a long journey of testing resilience, rhythm, and human connection through async work.
Thank you to everyone who supported, questioned, and contributed along the way.
📩 If you’re genuinely curious about the system or want to discuss what I learned through this process, you can reach me here:
[email protected]
Really appreciate the honesty and reflection in this — wrapping up a project after months of experimentation takes clarity and courage, and sharing the learnings publicly is generous.
Async systems (especially ones focused on workflow and sales automation) really hinge on how signals and rhythms are surfaced to users instead of relying on meetings or synchronous alignment — that’s not an easy problem to crack.
I’m curious — as you’re archiving this work, what’s one surprise lesson you’d pass on to someone building an async-focused platform next (something you didn’t expect when you started)? That kind of learning often matters far more than the tech itself.