Product
Problem definition, product scope, positioning, early-access model, and customer use cases.
Software architect & developer
I design and build software. For more than thirty years, that has meant understanding the business, choosing the right architecture, and staying close to the code.
Based in Florence, Italy.
Founder of devFlorence. Creator of Diaktor.

Current focus
I work with organizations through devFlorence and develop Diaktor, my own messaging product. Both keep architecture close to implementation.
Senior-led software development for dedicated applications, integrations, and reactive platforms shaped around real business processes.
Secure, Matrix-compatible real-time communication deployed as an elastic serverless platform in the customer’s AWS account.
Selected experience
Product leadership, AWS serverless architecture, Java engineering, Matrix federation, and complete product delivery.
Senior architecture and development in an international team building a Java and Quarkus Matrix server on AWS.
Architecture and development of a Java, Quarkus, Kafka, and Kubernetes log aggregation platform.
Designed, led, and evolved the Tuscany Region's European Social Fund system with Java web technologies across more than a decade.
From Linux hosting and CGI/Perl to Java-based banking and booking applications, healthcare systems, and enterprise Java consulting and training.
Featured product · Diaktor
Diaktor is where product decisions, distributed architecture, cryptography, interoperability, infrastructure, UX, and technical positioning meet in one system.
Visit diaktor.netProblem definition, product scope, positioning, early-access model, and customer use cases.
Event flows, federation, security boundaries, AWS services, and operational trade-offs.
Java backend, web client, infrastructure, tests, documentation, and production discipline.
UX, visual identity, technical diagrams, product website, and buyer-facing communication.
Engineering approach
Tools and runtimes change. The difficult work remains understanding the problem, choosing the right boundaries, removing unnecessary scope, and staying accountable for what reaches production.
Model the process and its constraints before choosing patterns or platforms.
Technical direction remains grounded in implementation, tests, and operational reality.
Keep continuity from discovery and architecture through delivery and production.
Use AI to accelerate exploration and execution without outsourcing judgment or accountability.
The devFlorence model
devFlorence is the studio through which I work directly with organizations that need senior architecture and hands-on delivery without agency layers.
Explore the studioFull record