Who writes your code
Lendvis builds complex IT products, ready for heavy load from users around the world.
We came up through competitions, and it turned out to be a useful habit: you get the brief an hour before the deadline and everything still has to run — deployment included.
Then came production. An 80,000-line online store: a Next.js storefront over a FastAPI backend, payments through YooKassa, inventory in MoySklad, CRM, Yandex Delivery. The job was not to make it pretty. The job was to get through the peak season without going down.
A campus meal system for a thousand people: the QR pass works with no internet, an ECDSA signature is verified on the spot, and a double-spend guard catches replays. The client is one Kotlin Multiplatform codebase running on Android and iOS. Alongside that, smart contracts for companies we cannot name.
And a separate line of work: code written by someone else. Projects where the author left, the documentation never existed, and all anyone knows is that it “crashes sometimes”. We go in on purpose.
- Where
- Samara, working remotely
- Languages
- Russian and English
- Fields
- Web, mobile, blockchain, backends, support, 1C
- Open code
- Seven repositories with live demos
- Terms
- Contract and NDA, staged payments
What we hold to
Cause over symptom
A symptom takes an hour to hide and comes back next week. We look for the line that started it, even when it lives in someone else’s module.
Show, do not tell
We do not send a slide deck with logos. We send a link you can open and a repository you can read — before the work starts and every day it runs.
Straight answers
If a deadline is about to slip, you hear it from us early — not on delivery day. Bad news is cheaper the sooner it lands.
Tell us what needs building
Two paragraphs is enough. Back comes a timeline, a couple of options, and a straight “this is not a job for us” when that is the honest answer.