Studio
Ricklayer
Our studio takes a product from idea to production and owns every layer. In commercial development since 2021: from client websites and automation to platforms that sell every day.
The name comes from bricklayer: a product is built layer by layer, and every layer is laid with care. Security is not a separate phase for us but part of every task.
- Working
- since 2021
- In production
- EloStore, Kvart, Copilot
- Full cycle
- product, interface, code, servers, security, SEO
- Languages
- Russian and English
How we work
Rules that hold the bar
Our studio writes them into every project's charter and checks them on every task, not on special occasions.
- 01Threats before codeA short threat model across 12 classes, from input parsing to alerts. Classes that do not apply are named out loud.
- 02Checked means runBuild, types, tests, a live server response. Two clean check rounds in a row, otherwise the work is not shown.
- 03Tests that holdWe break our own code and watch the test fail. A test that stays green checks nothing.
- 04Real services, liveA mock built from docs only tests our reading of the docs. An integration is done when it has talked to the real service.
- 05Decisions on record127 decision records across two projects: why, what, threats, how it was verified.
- 06Lose nothingA backup before anything irreversible, rollback in one command, irreversible production changes only with explicit consent.