Skip to content
Available for new projects

Enterprise software in .NET,engineered to last.

I’m Fjodor, a full-stack developer specialised in .NET and Blazor. I design ERP systems, B2B platforms and backend services for fashion and manufacturing companies — with architecture, security and code quality at the core.

always up to date
.NET 10
by design
Multi-tenant
response time
24–48h
Portrait of Fjodor, full-stack .NET developer, in a navy jacket with arms crossed

The stack I build with

  • C#
  • .NET 10
  • Blazor
  • ASP.NET Core
  • EF Core
  • SQL Server
  • PostgreSQL
  • .NET MAUI
  • DevExpress
  • Polly
  • xUnit
  • Docker
  • Clean Architecture
  • CQRS

01What I do

From data model to interface, one standard of quality.

I work across the full lifecycle of business software: domain analysis, architecture, development, release and long-term evolution.

  • Custom ERP and business systems

    Modular Blazor systems with metadata-driven UI, generated grids and complex flows such as fashion size × colour matrices.

    • Blazor Server
    • DevExpress
    • Multi-tenancy
    • Metadata-driven UI
  • APIs and backend services

    ASP.NET Core and EF Core with Clean Architecture and CQRS: testable, idempotent and resilient services.

  • Modernisation

    Evolving existing systems towards modern .NET, reducing technical debt and cognitive complexity.

  • Application security

    Audits, vulnerability remediation, nonce-based Content Security Policy and identity management.

  • Quality and reliability

    Automated tests, Polly resilience pipelines, SonarQube static analysis and CI/CD.

  • Web and mobile apps

    Installable Blazor WebAssembly PWAs and cross-platform native apps with .NET MAUI.

02How I design

Clean architecture, because software changes.

The domain at the centre, dependencies pointing inwards, replaceable infrastructure. That is what keeps business software maintainable for years, not months.

  • Domain-first

    Explicit, isolated business rules, modelled with DDD together with domain experts.

  • Testable by construction

    Inverted dependencies and clear boundaries: every use case is verified without a database or UI.

  • Secure by default

    Multi-tenancy with data isolation, strict CSPs and compliance with quality standards.

  • Ready to evolve

    CQRS and independent modules: new features without rewriting existing ones.

Clean Architecture: Presentation → Infrastructure → Application → Domain PresentationInfrastructureApplicationDomainentities · rules
Presentation → Infrastructure → Application → Domain

03Case studies

Featured projects

A selection of systems I designed and built, from enterprise software to personal apps.

All projects
012025 — presentFashion and apparel

Modular ERP for B2B fashion

Full-stack developer

Enterprise business system for the fashion and apparel industry — orders on size × colour matrices, master data, multi-tenancy and metadata-driven UI.

Key points

  • Modular three-layer architecture with metadata-generated grids
  • Multi-tenancy with per-company isolation and schema-based organisation
  • Custom SVG sprite icon system with a conversion pipeline
  • Blazor Server
  • .NET 10
  • EF Core
  • SQL Server
  • DevExpress
#Enterprise#Frontend#BackendRead the case study
022024Marketing and communication

Email campaign engine

Backend developer

ASP.NET Core service for high-volume campaign delivery — template pre-rendering, SMTP connection pooling, idempotency and resilience.

  • ASP.NET Core
  • .NET 10
  • Polly
  • Channel<T>
  • xUnit
#BackendRead the case study
032026Bespoke tailoring

SaaS for bespoke tailoring

Full-stack developer

Multi-tenant platform to manage tailoring orders and measurements, with identity, security audits and on-premise or cloud deployment.

  • ASP.NET Core MVC
  • EF Core
  • SQL Server
  • PostgreSQL
#SaaS#BackendRead the case study

Industries

Vertical experience where precision is not optional.

  • Fashion and apparel
  • Manufacturing
  • Bespoke tailoring
  • Retail and loyalty

04Method

A clear process, from first meeting to release.

  1. 01

    Discovery

    I learn the domain, processes and constraints. Together we set goals and priorities.

  2. 02

    Architecture

    Data model, module boundaries and technical decisions documented before any code is written.

  3. 03

    Iterative delivery

    Incremental releases, automated tests and continuous review: you see progress every week.

  4. 04

    Release and evolution

    On-premise or cloud deployment, monitoring and ongoing evolutionary maintenance.

Start a project

Have a .NET project in mind?

Whether it’s a new business system or evolving an existing one, tell me what you need: I’ll get back to you within 24–48 hours.