.svg){kind=small}
.svg)
.svg)
.svg){kind=small}
Why we even bother
This page matters to us, it's how we say: ["we're human too"]. What we stand for, what we don't, and why — it’s all here.
.svg){kind=small}
reposible
/
admin-dashboard
.png){kind=small}
Repo management idea
#1520
ruben on April 2, 2025
Was talking to you earlier: what if we rethink repo management from the ground up? Not just plug & play integrations, but also pipelines, rulesets, dependency handling … all fully open-source (even our business strategy?). Just tools we’d want to use ourselves. Feels like it could be something if we get it right.
Meet tomorrow night after work!
.png){kind=small}
👍
1
.svg)
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
Our story: Reposible began as a passion project between teammates
We talked about it often between deadlines, side projects, and long commits. And now ...
We’re building it properly. We’re fully open source, listening closely, and shipping what feels genuinely useful.
Antivision
Read on to find out what we don't want to become, and how that vision helps us building, one step at a time.
.png){kind=small}
Bert/reposible posted in 🚧 Antivision
from Bert 3 week ago
What we're not
We're not here to chase hype or pretend we're the next big thing. We're figuring it out as we grow:
- No chasing VC money like it's a sport
- No "we'll get back to you" black holes
- No building in stealth mode for a long period
- No pretending we've got it all figured out (we don't)
We build in public, learn in motion and we care more about real progress than perfect plans.
.svg){kind=small}
1
.svg){kind=small}
Comment
.svg)
.svg){kind=small}
Experiments & accidents
See how we learn the hard way.
.svg){kind=small}
Closed
Bug
.svg){kind=small}
#eac-001
ruben on May 5, 2025
We needed early devs to get the ball rolling
We launched an early access for the first 50 devs, thinking it’d be a great way to gather feedback and create some early momentum. It kind of worked … until it didn’t.
.svg){kind=small}
.png){kind=small}
Experiment
At the time, our idea was pretty simple: we offered a discounted version of our Integrations to a small group of early adopters.
It wasn’t about making money. We were just eager to see how people would perceive Reposible. Until we shared it on Reddit ...
It wasn’t about making money. We were just eager to see how people would perceive Reposible. Until we shared it on Reddit ...
Accident
One dev responded: "Feels like you're just trying to get free labor. Once you collect enough feedback, you’ll ghost."
That wasn’t the plan at all. But the more we sat with it, the more we got it: a closed group, a discount, no open-source code yet, and no public repo. That wasn't how we wanted to start.
That wasn’t the plan at all. But the more we sat with it, the more we got it: a closed group, a discount, no open-source code yet, and no public repo. That wasn't how we wanted to start.
What we changed
It kicked off a long conversation between us, so we decided:
- To open-source everything: the strategy, the code...
- No paywall until we build something you love
- We redesigned the way we talk to you
Juice worth the squeeze
Discover where we over-invest on purpose (sometimes by accident). Proof that we care a little too much.
Pixel Perfection
We spend way too long perfecting pixels, because our 5% rule won't let us sleep if something doesn't feel right.
.svg){kind=small}
.svg){kind=small}
ruben often loses sleep
Refactor Loop
We spend way too long polishing code, because our chase for quality keeps us refactoring into the pretty infinity.
bert loops in pretty infinity
If we had more time ...
We already spend too much time on pixels, plans and code. Here's where our time would go if we had more.
Spend hours listening to you
If we had more time, we'd swap keyboards for more conversations: learning from developers, catching their frustrations and sparks, and probably filling walls with sticky notes.
Pick up a new language
If we had more time, we'd dive into a new language: Mixer, maybe even Italian. Code or human, every language opens a new way of thinking.
Prototype the unnecessary
If we had more time, we'd do more playful experiments: apps no one asked for, features no one really needs and prototypes that secretly shape what we'll build next.
Questions?
Have more questions about us? Read the questions people actually asked us and learn to know us better.
How did you two meet?
.svg)
We first worked in the same team. From day one it just clicked. we were complementary, pushing each other creatively on tough problems. Design-wise it felt natural. Even after moving on to different jobs, the connection stayed. Reposible became our way to work together again, and we both enjoy that more than ever.
Why did you start Reposible in the first place?
We’ve both been entrepreneurial since we were young, always trying projects of our own. After no longer working in the same team, we realized how much we wanted to build something together. Reposible was born from that shared drive.
What do you do when you’re not working?
Bert plays soccer, spends time with his dog, and finds inspiration in all kinds of code experiments. Ruben plays basketball and has two young sons he loves to spend time with. Different lives, but the same curiosity that fuels what we build.
Where do you see Reposible in 5 years?
We hope it grows the way companies like PostHog did: starting small, open, and community-driven, but becoming the go-to toolkit in our space. We hope Reposible grows enough for us to make it our full-time work again, building together in the same team, this time for our own project.
Who’s more of a perfectionist?
We both are, just in different ways. If we had to choose, Ruben is probably 5% more perfectionist. But that balance is what makes us complementary and keeps Reposible moving forward.
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}