Skip to content
Ricklayer
RUEN

Studio

Ricklayer

Ricklayer launched as a studio in 2025, and the team has worked together for more than five years. Before the studio we spent years building projects together: client websites, trade automation, bots, game servers and platforms with daily sales.

Over time it became clear that we keep covering the whole path of a product ourselves: from the mockup and database schema to the server, security and search. That is how the studio came about: five people, each responsible for their own layer, building the product together.

Studio
since 2025
Team together
more than 5 years
On the team
tech lead, designer, developer, ML engineer, DevOps
In production
Kvart, EloStore and many projects under NDA
What we do
product, interface, code, servers, security, SEO
Languages
Russian and English

What inspired us

How a bricklayer works

A crooked course cannot be fixed later: it ends up inside the wall.

The name comes from bricklayer. We have always liked how a good bricklayer works: lay a course, check it with a level and a plumb line, and only then start the next one.

A product works the same way. The database schema, access rights, deploys and security sit at the base, and a mistake there ends up deep inside. So every layer gets checked before the next one goes on top: the build, the tests, a live request to the server, and before a deploy two clean rounds of checks in a row.

The same image runs through the design: the 3D on the site is made of matte black ceramic with metal edges, like tiles that add up to a whole.

How we work

Rules we stick to

We write them into every project's rules and check against them on every task.

  1. 01Threats before codeA short threat model across 12 classes, from input parsing to alerts. Classes that do not apply are named out loud.
  2. 02Checked means runBuild, types, tests, a live server response. Two clean check rounds in a row, otherwise the work is not shown.
  3. 03We test the testsWe break our own code and watch the test fail. A test that stays green checks nothing.
  4. 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.
  5. 05Decisions on record303 decision records across two projects: why, what, threats, how it was verified.
  6. 06Lose nothingA backup before anything irreversible, rollback in one command, irreversible production changes only with explicit consent.