Two people, eleven years, six products.
We’ve been building things together since before we knew what we were doing. Now we build the thing that takes care of what you built.
We met as Computer Engineering undergrads.
And started building together almost immediately. We’ve never really stopped.
Six products shipped, together.
One of them, VideoConnectLab, was acquired by its pilot enterprise customer. Every one of them taught us where things break after you hand them off.
Ship It, from Prague and Istanbul.
The two of us write all the code. No third engineer, no layers between you and the people responsible.
Giyas Bayrak
Builds the AI systems: the engine that figures out what’s wrong with an app, and the one that writes the proposed fixes.
“If we can’t explain a fix in plain words, it isn’t ready.”
Abdullah Jiroudi
Builds the infrastructure: deployment, orchestration, and keeping each customer’s app in its own separate space.
“Your app should be steadier in our hands than it was on your laptop.”
Three rules we hold ourselves to
- 1
No merge button on our side.
Every fix is a proposal you review. We can't change your app on our own, and that's by design.
- 2
Bad news comes first.
If a check can't run on your app, you hear it before the scan starts, not after.
- 3
We're clear about where our checks end.
Some things stay outside our list, payment math among them. You always know exactly what we looked at and what we didn't.
Where we are right now
We’re building the MVP now. Ship It isn’t launched and has no revenue yet. We’ve talked with 15 prospective users, and 10 of them already have a repo waiting for the first deploys.
Be one of the first deploys.
10 repos are already queued for the first deploys. Yours can be next.