TEAM
The team is growing: it has expanded over the past year and keeps taking on people. More than 60 years in the web between us.
The people whose work you saw in the portfolio are the ones who work on your project. We don’t outsource projects and we don’t swap in juniors once the contract is signed.
The least experienced person on the team has 5 years behind them. The most experienced, 20.
01.
Development
7 Employees
02.
Design
4 Employees
03.
Management
3 Employees
04.
Marketing
3 Employees
Exactly these people, design every project in the studio
PRIMARY
LUNO TEAM
FOUNDER | ARCHITECT
Rodion
10 years of experience
Designs the architecture of every studio project. Decides how the system is built inside and whether it will survive the growth of the business. - System architecture; - Fullstack; - System design;
DEVELOPMENT TEAM LEAD
Kirill
10 years of experience
Holds the studio’s engineering bar: what goes to production is his call. Designs systems that do not fall apart when there are ten times more users. - Load - Data - Automation
LEAD ENGINEER
Alexey
5 years of experience
Turns business logic into a working product — from the client dashboard to an admin panel where everything is managed without a developer. - Product logic - Integrations - Engineering
INFRASTRUCTURE TECH LEAD
Evgeny
23 years of combined experience
Builds the infrastructure the studio’s projects live on: servers, deploys, monitoring, backups. After launch a project is not left on its own — Evgeny keeps it available, quick to respond and able to take the load on peak days. - DevOps - Security - Fault tolerance
ART DIRECTOR
Ivan
7 years of experience
Owns the studio’s visual language: how every project looks and why exactly that way. Builds a design system rather than a set of pretty screens — a mockup has to survive development and not fall apart on the second page. - Visual language - Design systems - Identity
STRATEGY & MARKETING
Yaroslav
15 years of experience
Makes sure the site brings in clients instead of simply existing. - Positioning - Conversion - Content structure
PROCESS OF
DEVELOPMENT
The same order for any project: a website, a store, a CRM, an app, AI. The scale changes, the discipline does not.
Out of six steps, only two are yours.
from you: one conversation
THE TASK
Tell us what you want in your own words. Got an idea — great, no idea — also great: we are the ones who ask the right questions.
01
from you: approve the plan
ARCHITECTURE
We write the brief and design the system. You get a plan where every decision and its price makes sense, not a number pulled out of thin air.
02
from you: pick a direction
DESIGN
Several iterations for your project. You pick the direction — we take it from there.
03
from you: nothing
DEVELOPMENT
A daily work log and a code review on every change. You can see what was done and how long it took.
04
from you: nothing
LAUNCH
Testing, migration onto the infrastructure, configuration, integrations.
05
from you: write when you need to
SUPPORT
The project stays on our servers and under our watch. Improvements, updates, monitoring.
06
FAQ
Answers to the most popular questions
The same people you see on this page. The founder designs the architecture, the team lead runs development, the art director does the design, the infrastructure lead handles the servers and the launch. The line-up depends on the task: a landing page does not need the whole set, a store with a CRM does.
No. Everything is done inside the studio: system design, design, code, infrastructure. We do not hand projects to third parties and we do not swap in juniors once the contract is signed — the experience on the cards above runs from 7 to 20 years, and those are the people who actually do the work.
At the start, the founder — who also designs the architecture, so you explain the task straight to the person who will be solving it. After that the person running the project by stages and deadlines joins in. There are no layers you have to pass your wishes through.
The project is not tied to one person. Review goes through the team lead, documentation and access live in a shared perimeter, and the code is written so another developer can pick it up. A change of hands may shift the deadline, but it will not stop the work.
For the projects we take on, no. A team with 7+ years behind it assembles a system faster than a large department with sign-offs: a marketplace with its own CRM, a complex client dashboard, five payment systems, bonus systems and a ticket system took us 30 days. The team grows with the load, but we do not lower the hiring bar for speed.
TELL USABOUT THE TASK
Twenty minutes on a call and you have a plan: what the project is made of, how much time and money it will take.