acks.io works with clients. acks.io Labs builds the tools we wish we already had— experimental ideas, scrappy prototypes, and open/closed-source utilities that graduate into our daily workflow and, sometimes, into the community.
Some projects ship as open source. Others stay internal. All of them aim to remove toil and make platforms calmer, faster, and more resilient.
A focused sandbox where we prototype new developer tools, platform patterns, and incident-friendly workflows. When something proves useful, it graduates into client work at acks.io or gets released to the community.
Ideas start as tiny utilities, grow into prototypes, and—if they reduce toil—enter day-to-day delivery.
We open-source what helps the community and keep some tools private when they’re client-specific.
Demos, write-ups, and talks at meetups and conferences once things are stable enough to share.
Less theory, more removal of yak hair. If it saves hours in a week, it’s a keeper.
Filter by phase, tag, or openness.
Paper cuts and hunches from client work.
CLI or service that passes the sniff test.
Limited use in real engagements; iterate fast.
Adopted in our delivery and, sometimes, released.
Demos and stories once the dust settles.
We love co-developing with teams. If you’re in the Nordics or Europe and want to pilot a tool, reach out.
