Founder & engineering leadership
Dmytro Nasyrov
Founder and CTO Pharos Production
Founder of Pharos Production, PhD in Artificial Intelligence and lecturer at Igor Sikorsky Kyiv Polytechnic Institute.
About
Dmytro Nasyrov is the founder and CTO of Pharos Production, a software development and AI engineering company since 2013. With 23 years of engineering experience and a PhD in Artificial Intelligence, he leads engineering culture at Pharos and lectures at Igor Sikorsky Kyiv Polytechnic Institute.
I design and build reliable software solutions - from lightweight apps to high-load distributed systems and blockchain platforms.
PhD in Artificial Intelligence, MSc in Computer Science (with honors), MSc in Electronics & Precision Mechanics.
Education and credentials
- PhD in Artificial Intelligence
- Lecturer, Igor Sikorsky Kyiv Polytechnic Institute
- Alumnus, Igor Sikorsky Kyiv Polytechnic Institute
Areas of expertise
- Artificial Intelligence - LLM integration, RAG, agents, ML platforms
- Blockchain protocols - DeFi, NFT, smart contracts, dApps
- FinTech platforms - payments, compliance, RegTech
- Custom software development - web, mobile, enterprise
- DevOps and cloud architecture
- Engineering leadership - strategy, technical due diligence
Career timeline
-
Founder and CTO, Pharos Production
Software development and AI engineering. 90+ engineers, 110+ apps for 200+ clients across 28 industries. Aligned with ISO 27001, SOC 2, HIPAA, PCI DSS and GDPR frameworks.
-
Lecturer, Igor Sikorsky Kyiv Polytechnic Institute
Teaching engineering at Ukraine's leading technical university.
Ideas from practice
Articles by Dmytro Nasyrov
NIS2 Compliance Outsourcing
NIS2 contains no prohibition on outsourcing any security measure, so the real question is which parts of Article 21 the market can supply and which acts sit with management bodies under Article 20 and the implementing regulation rather than with a provider. A decision guide for an entity whose scope is already settled, covering the supply chain duty that buying anything creates and the evidence a supervisory authority asks the entity, not the vendor, to produce.
Hotel Channel Manager Integration
Hotel channel manager integration as a catalog of failure modes: ARI drift, overbooking from inventory races, rate and room mapping errors, reservation desync and the certification gates standing between a connector and a live OTA channel.
EUDI Wallet Data Deletion
A wallet user taps erase and what reaches you is a GDPR Article 17 request. This is the boundary between the wallet's machinery and the controller's own obligations, the one-month clock the recital's word immediate does not shorten, and the refusal path most build estimates miss.
EUDI Wallet SCA
A wallet-presented SCA Attestation is an OpenID4VP presentation carrying transactional data, and TS12 states that its verified jti claim serves as the Authentication Code PSD2 requires for electronic payments. This guide walks a payment service through the processing order: reading type metadata, signing and encrypting the request, surviving the locale check, verifying the Key Binding JWT and gating on the amr array. Written throughout as a second acceptance path alongside an existing implementation, never as a replacement for one.
AI Travel Agent Development
AI travel agent development for an OTA, TMC or booking platform: what a tool-calling agent can and cannot book today, how it stays grounded on live inventory, the guardrails a mis-booking risk requires and an evaluation protocol before launch.
MiCA White Paper Requirements
The crypto-asset white paper under MiCA Title II is a disclosure document nobody approves and whose content the offeror is solely responsible for. This guide sets out who must draw one up and who is exempt from precisely which obligations, what Annex I forces into the document, the Inline XBRL format rule and its application date, and the notification, publication, modification and withdrawal clocks that run around it.
Last updated: