backend / product / shipping

Andrey Keil

Backend-focused developer building Ventus Iter inside a university accelerator. The project’s main tech stack consists of Kotlin and TypeScript.

View projects Contact GitHub

building Ventus Iter toward MVP inside a university accelerator

leading a 4-person team across web, Android, and QA

studying Applied Informatics at RSHU alongside work on a live product

open to open source projects and internship opportunities

I am a backend-focused developer with a strong interest in working with APIs and databases, developing my own subsystems, and, more recently, deployment and DevOps in general. I study Applied Informatics at RSHU and, in parallel, develop Ventus Iter inside a university accelerator. I feel most at home in projects where I have to work not only on isolated features, but on a real operating system around them: backend, APIs, deployment, CI, structure, and grounded product thinking.

01
Early technical interest

What pulled me in first was not just a specific language or tool, but the logic of systems themselves: how things work under the hood, why some setups feel solid, and how they can be made cleaner and more useful.
02
University and a larger scale

RSHU, Applied Informatics, and additional study at ITMO's Academy of Informatics and Programming turned scattered curiosity into a more serious direction: backend, workflows, infrastructure, and responsibility for delivery.
03
Practice, freelance, and discipline

Client fixes, automation, integrations, small services, and support work taught me not only how to write code, but how to bring things to a working state under constraints, deadlines, and real expectations.
04
Applied projects and backend focus

Over time I moved closer to the part of development where the whole system matters: API design, server logic, deployment, CI, and the question of how a product behaves beyond a local environment.
05
Ventus Iter and the accelerator

This is the main stage right now: I lead Ventus Iter inside a university accelerator, own backend/API, staging, and CI, work with a team, and move the project toward a real MVP rather than a good-looking idea.
06
A future product launch

The longer line ahead is not just a collection of neat projects, but an independent product with character, clear value, and a market of its own.

These three projects show my current direction best: Ventus Iter as the main product, Python bots as repeatable engineering practice, and IPD-app as an earlier MVP case.

main product / accelerator track

MVP in progress

Ventus Iter

The main project in my current focus: a product for travelers, outdoor enthusiasts, families, and people who want route decisions with weather context.

4 team members

MVP in progress

I am building Ventus Iter inside a university accelerator with a 4-person team. I own backend, API, staging deployment, and CI; beyond that, I review work, fix issues, and help hold the product together as one system. In its current repository state, this is already an honest working MVP layer: web, API, an Android auth client, local infra with a staging setup, and a path toward a fuller user journey beyond a mock-only mode.

Стек NestJS API, Next.js, Android, PostgreSQL/PostGIS, Redis, GitHub Actions

Роль backend lead, API, staging deploy, CI, review

Фокус route and weather context, product delivery, and movement toward a real MVP