Build it as if we run it
Whoever writes the code thinks about who gets paged at 3 a.m. We design for the on-call engineer, even when that engineer will be yours.
Kamurj means “bridge” in Armenian, and a bridge is judged by one thing: what it carries. So instead of our history, here is how we think, what we put first and what we never trade away.
Same as Dubai. No daylight saving
A screen that looks fine and falls over at 10,000 users is not done.
We would rather build it properly than patch the quick one three times.
“Fast” means a response time. “Stable” means an error rate.
A risk you hear about in week one is a decision. In week ten it is a delay.
Proven tools for money, health and identity. Experiments go where they cannot hurt.
Yerevan is UTC+4. Your stand-up is our stand-up.
Whoever writes the code thinks about who gets paged at 3 a.m. We design for the on-call engineer, even when that engineer will be yours.
We cut features before we cut quality. The first release does fewer things and does them under real load.
A monolith that is easy to change beats microservices nobody can trace. We add moving parts only when a measured limit forces us to.
Opinions about performance end with a benchmark. Every report you get has response times, error rates and cost per month.
Secrets stay out of code, roles are checked on the server and personal data is visible only to whoever needs it. We plan for the audit before the first line.
Code, tests, infrastructure and runbooks live in your repositories from day one. Your team can take the keys on any day without calling us.