Skip to content

About

About

One engineer, the whole path, and a rule against claiming anything that cannot be checked.

ODIN337 is a one-engineer studio. I take a project end to end: the interface, the code, the infrastructure, and everything that happens after launch. There is no handoff between the person who designs a screen and the person accountable for it in production, because they are the same person.

That has a cost and a benefit. The cost is throughput: I run few projects at a time, and a large product needing several teams is not something one engineer should be sold. The benefit is coherence — the decision about how a component behaves is made by the person who will be fixing it at four in the morning, and it gets made differently for that reason.

This site is the main argument. It is built under the same rules as client work: static delivery, no gratuitous JavaScript, personal data held on a server in Russia, legal documents written for this specific processing arrangement rather than copied from a template. All of it is checkable in a browser — and checking it before the conversation is encouraged.

Principles

  • Checkable, not claimed

    No «increased conversion by 40 %» without a link that lets you re-run the check. The case studies publish the problem, the approach and the stack; a number appears only where it comes with the instruction for reproducing it yourself.

  • Less code in the browser

    A page is static by default. JavaScript is added where behaviour genuinely requires it and nowhere else — every kilobyte in the bundle is downloaded by someone on a mobile connection. Heavy graphics run only on hardware that can carry them, and switch themselves down when the frame rate drops.

  • Law is part of the architecture

    Russian data-protection law is answered by where the data sits, not by a paragraph in the footer. Submissions from this site are written to a database in Russia before any other processing, the documents name every processor individually, and analytics does not load until it is allowed to. Client projects get the same arrangement.

  • You keep everything

    The repository, the domains, the cloud accounts and the credentials are in the client's name from day one rather than migrated «later». No project is held hostage: if the engagement ends, you take away a running system, not a source archive with no keys to it.

How the work runs

  1. Conversation

    An hour to understand the problem, the constraints and the deadline. It ends with a range and a straight answer about whether the thing is worth building in the shape proposed. Free, and commits you to nothing.

  2. Estimate and contract

    Scope, stages, timings and a fixed price per stage — in writing, before anything starts. Each stage is paid before it begins, so either side can stop at any boundary without an argument about what has already been done.

  3. Delivery in stages

    Every stage ends with a running build at its own address, not with screenshots. Revisions within the agreed scope are part of the stage; a change of scope is a new stage with its own estimate, and that is said at the time rather than discovered on the invoice.

  4. Launch and handover

    Production, monitoring, documentation and credentials on the client's side. After that either support under a separate agreement, or you run it yourself: the system is built so that the second option is genuinely available.

Stack

Frontend

  • TypeScript
  • React
  • Next.js
  • Tailwind CSS
  • WebGL / Three.js
  • GSAP

Backend

  • Node.js
  • Fastify
  • PostgreSQL
  • Redis
  • Prisma
  • Zod

Infrastructure

  • Docker
  • Caddy
  • GitHub Actions
  • Linux VPS
  • PostgreSQL
  • Yandex Cloud

Mobile

  • React Native
  • Expo

Registration

Contracting party
Individual entrepreneur (ИП) Roshchupko Danila Vyacheslavovich (Рощупко Данила Вячеславович)
INN (tax ID)
772648810450
Tax regime
Sole proprietor on the professional-income tax regime (НПД). Not subject to VAT; invoices are issued without VAT, and every payment is receipted.
Working languages
Russian, English
Time zone
Moscow, UTC+3. Working hours are 10:00–19:00 on weekdays, in that zone.
Payments
Roubles — by invoice from the registered entrepreneur. Foreign-currency engagements by arrangement; settlement details are issued with the invoice.
How personal data is handled
Discuss a project