PHP / Full-Stack Developer · Latvia

I build web systems
that do the work.

Full-stack PHP developer with 10+ years across e-commerce, high-load data systems, REST integrations, production servers, and AI-assisted delivery.

See selected work ↓+371 29323395 ↗
~/platformPRODUCTION READY
01$ docker compose up --build -d
02✓ Network platform_default created
03✓ Container api healthy
04✓ Container web started
05$ █
Selected work

Built for the real world.

Practical systems, measurable improvements, and clean handoffs.

/01
>_

M79 e-commerce platform

Built the M79 Store from the ground up: product flows, wholesaler feeds, payments, REST APIs, and optimized relational data.

PHP / PhalconMySQLPostgreSQL
View live surface ↗
/02
>_

Biļešu Paradīze

Shipped Laravel features for a high-traffic ticketing experience, including city discovery pages, registration flows, and country-code phone dropdowns.

LaravelVue / NuxtMS SQL
View live surface ↗
/03
>_

AI-assisted delivery

Use Junie and structured AI workflows to move from requirements to production faster while keeping architecture, quality, and outcomes in my hands.

JunieMake.comREST APIs
Core toolkit

From API to AI workflow.

01Backend

PHP · Laravel · Phalcon · Yii2 · REST APIs · JSON

02Frontend

JavaScript · Vue.js · Nuxt · HTML5 · CSS3

03Data

PostgreSQL · MySQL · Microsoft SQL Server · analytics

04Infrastructure

Linux · Apache · Nginx · Docker · Git · production maintenance

05AI & automation

Junie · Make.com scenarios · AI-assisted development · systems integration

How I work

From first brief to reliable release.

Clear decisions, visible progress, and systems that stay maintainable after handoff.

01

Frame the problem

I turn the brief into a clear technical direction: user flows, data boundaries, integrations, and the smallest useful first release.

02

Build the system

I shape the backend, interface, and infrastructure together so the product is coherent from API contract to production workflow.

03

Ship with confidence

I verify the important paths, document the handoff, and leave behind a release that is observable, repeatable, and ready to evolve.