.svg){kind=small}
.svg)
.svg)
.svg){kind=small}
How Reposible Began
We tell the story of how Reposible began: from two developers in an accounting firm to building an open-source suite that redefines repository management.
Read our vision
Summary
In this story, we share how Reposible was born from a simple frustration: development was moving fast, but repository management stayed stuck in complexity. We explain how we turned that pain into a visual, open-source solution that anyone can understand and use. Built on passion, clarity, and transparency, Reposible is our way to make software simpler, fairer, and more collaborative.
.svg){kind=small}
Between deadlines, tax seasons, and late-night code pushes, we met as colleagues in an accounting firm’s tech team.
We weren’t supposed to start a company together. We were just trying to make our internal tools work better. But like so many developers, we kept running into the same wall: every new project meant starting from zero.
Pipelines, rulesets, dependencies, ... they slowed us down again and again. Each time we thought, there must be a better way.
The Moment It Clicked
One evening, after another round of debugging CI/CD configs, we realized the problem wasn’t the tools themselves. Everything lived in different places, built by different people, following different rules. The simplest idea, like improving a pipeline, turned into a tangle of scripts and YAML that no one really enjoyed maintaining.
So we started sketching. Not diagrams for accountants, but for developers. We imagined what repository management could look like if it were visual, connected, and open from day one. Something you could see instead of just configure.
That sketch became the first seed of Reposible.
From Idea to Direction
We didn’t start with investors or a business plan. We started with a shared mission: to make repository management effortless. We wanted to give developers tools that worked as smoothly as modern design software: visual, intuitive, and transparent.
Every choice we made came from that belief. We went open-source so everyone could contribute. We shared our roadmap, design choices, and even our mistakes. We wanted people to see how things are built, not just what’s released.
That’s what we call our “widely open” approach. It's not just open code, but open thinking.
The First Step: Visual Pipelines
Our first milestone was clear: pipelines. If developers spend so much time setting up CI/CD, what if we made it visual? What if automation felt like designing, not configuring?
We built a drag-and-drop builder where pipelines come to life on screen. You can connect steps, monitor runs, and even export everything as clean YAML. It’s still early, but it works (and it feels different).
What Comes Next
Reposible is growing step by step, built on real feedback. We’re adding local runs, GitHub and GitLab integration, dashboards, and self-hosting options. From there, we’ll move into rulesets and governance. This way we're turning repository management into something teams actually enjoy using.
But the goal stays the same: keep it open, visual, and human.
More Than Code
Reposible isn’t just about software. It’s about the kind of work we want to do and the kind of community we want to be part of. We believe in transparency over perfection, collaboration over competition, and progress over promises.
We’re still the same two developers, now building something bigger than ourselves. And if our story resonates with you, maybe it’s the start of something we’ll build together.
