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
GxP Software Development
GxP software development seen from the builder's side: how a development team produces validation evidence inside its delivery pipeline, from requirement traceability and risk-based testing to change control and release records. The guide maps data integrity controls to 21 CFR Part 11 and EU GMP Annex 11 and includes a RACI that leaves validation with the client's QA.
Software Used by Pharmaceutical Companies
Pharmaceutical companies run a different class of software at each stage of the value chain, from lab notebooks and EDC to safety databases and batch records. Our reading of this map is that most stages run on commercial systems each company validates for its own use, with custom work around them.
E2B R3
E2B R3 is the ICH format for moving individual case safety reports between safety databases as HL7 version 3 XML. The guide explains what changed from R2 and how a message is built, then compares FDA and EMA requirements and closes with an implementation checklist for engineering teams.
Ludo Architecture Deep Dive: Building a High-Throughput Web3 Reputation Engine
A technical account of Ludo's Web3 reputation platform, covering transaction ingestion, project analysis, search, cross-chain identity and the delivery infrastructure behind its dual-engine architecture.
Upgradeable vs Immutable Smart Contracts: How to Choose
Choose between fixed implementation, governed upgrades and migration from product requirements. Use a scenario matrix and permission register to record who can change the system and what remains unavailable.
Build Operate Transfer
Build operate transfer hands a vendor-built engineering team to the client, but for a team that is itself situated in Kyiv the EU and UK rules that move staff automatically do not apply. This guide explains how consent, a share purchase or Article 36-1 of the Labor Code decides who employs each engineer and how to keep the IP chain intact.
Last updated: