kapranov.dev

Websites, bots and services built to fit, not from a template

Built end to end: interface, server side, database and deployment on a real server.

Discuss a project →reply within one business day
websitestelegram botsmini appsadmin panelsintegrations

services

What you can order

Websites and stores

Storefront, catalogue, cart and order handling. Fast loading and a proper look on a phone by default, not as a paid extra.

Telegram bots and Mini Apps

Orders, bookings and notifications right inside the messenger. One shared database with the site, not a separate system living its own life.

Client area and admin panel

A panel where the owner changes prices, texts and photos themselves. No developer involved and no fee for every edit.

Fixes and support

The project already exists but something is broken, slow or missing. Reading someone else’s code and carrying it forward.

tools

What it runs on

The work spans every layer at once, from the interface down to the server. Below is what each layer gives you in practice and what it is built with.

Backend

Rules and calculations live on the server, so they cannot be bypassed from the browser.

  • TypeScript
  • NestJS
  • REST API
  • auth and sessions
  • input validation

Data and cache

Enquiries, catalogue and texts sit in a real database and survive a restart.

  • PostgreSQL
  • Prisma
  • schema and migrations
  • Redis
  • backups

Interface

Pages are served ready-made, so they load fast even on a weak connection.

  • TypeScript
  • Next.js
  • React
  • Tailwind CSS
  • server rendering
  • responsive layout

Telegram

A second way into the same system: orders and alerts where the client already is.

  • Bot API
  • webhooks
  • enquiry alerts
  • Mini Apps

Server and delivery

Hosting stays under control and shipping an update takes no manual steps.

  • Docker
  • Linux VPS
  • Caddy
  • TLS
  • GitHub Actions

how it works

Clear at every step

Scoping the task

A short conversation about what is needed and why. The outcome is a list of what gets built, and separately what does not.

Estimate and timeline

Agreed before the work starts and not revised along the way. Two rounds of revisions are included. Further ones are quoted hourly, separately and upfront: the amount is known before the work starts, not after.

Development

A working version is available by link from the first week. You can look and say “not this” early, not at the end.

Launch and handover

Domain, server, access and source code are registered to the client. Support afterwards is optional, not a requirement.

questions

What people usually ask

What do you need from me to start?

A short conversation about the task. After that: texts, photos and access, if the project already lives somewhere. The exact list comes after scoping, not as a twenty-page brief.

What have you already built?

The closest sample is the site you are reading. It is built end to end: interface, server side, database, admin panel, deployment and automated checks on every change. That is more honest than screenshots in a portfolio: speed, behaviour on a phone and how fast content updates can be verified right now rather than taken on trust. Anything closer to your task is worth discussing directly.

What if I do not like the result?

A working version is available by link from the first week, so “not this” shows up early rather than on delivery day. Two rounds of revisions are included; further ones are quoted separately and upfront.

Who keeps the domain, server and code?

You do. Domain and server are registered to you and the source code is handed over with the project. There is no lock-in: the work can be continued by anyone.

Will I be able to change prices and texts myself?

Yes, that is what the admin panel is for. Prices, texts, photos and products change without a developer and without a fee for every edit.

What happens after launch?

The project runs on its own. Support is optional rather than required: it is a separate arrangement, not a condition for the site to keep working.

contacts

Tell me what needs building

A couple of sentences about the task and the deadline will do. You will get questions to the point and a price range in return.

Message on Telegram

Or by email ilya@kapranov.dev

reply within one business day

If you would rather not message directly, describe the task here and I will reply the way you prefer.