Niki
A multi-tenant platform for the administration of Italian nonprofits. It manages members, volunteers, board terms, assemblies and Third Sector compliance.
Live demoSelected projects
A multi-tenant platform for the administration of Italian nonprofits. It manages members, volunteers, board terms, assemblies and Third Sector compliance.
Live demoMy fork of an open-source, self-hosted resume builder. I added a refine chat that tailors one application, a flow that sends new facts back to the profile, visual theme settings and server backups. I built it with AI coding tools.
Original projectA native planner for Mac, iPhone and iPad. It puts your tasks around your fixed commitments. Each day, you record your energy level, and the planner sets the tasks to match it.
A tool to learn languages. Paste a text, and a local LLM adds information to the words that you do not know. Then review these words with spaced repetition.
A list of social media and messaging domains in hosts format, for Pi-hole and other DNS filters. Use it to block social media on a network.
Experience
I owned the backend and cloud of two in-house products: Pupau, an AI agent platform, and Baghera, an HR platform. I was also the only backend engineer on 5+ client projects, and on call.
TypeScript · NestJS · Java · Python · GCP · Kubernetes · PostgreSQL · Kafka
I built REST APIs and microservices on Microsoft Azure for public transport clients. I led dependency security audits with Snyk on 4+ production codebases (Java dependency trees and Docker base images). The client teams adopted my prioritized remediation reports.
Java · Spring Boot · Angular · Azure · PostgreSQL
I was the contact person for ~50 volunteers, members and board members. I helped create the volunteer HR area, which did not exist before: intake interviews, training, recognition and growth paths with one-to-one follow-up. Volunteers moving into board roles went from ~2 to ~6 a year. I built a referral network with 7 Turin Third Sector organizations, including Arci and ACMOS, and it is still active.
I set up the workspace, knowledge base and documentation, and managed accounts for ~50 users with documented onboarding and offboarding. I met the non-technical volunteers one by one, and active use of the tools went from ~5 to ~30 volunteers in 12 months. I also ran a full GDPR and Third Sector compliance review and handed it to my successor.
I managed the ~€7,500 annual budget and built a treasury team, which did not exist before, then trained the volunteers who took it over. With the board, I co-wrote the yearly funding applications to Politecnico di Torino (up to ~€10,000) and kept audit-ready records for the funds.
Why I build
I grew up inside systems that had already failed the people in them. So I don't get excited about new tools. I ask who they're for, who gets left out, and who pays.
New things land on a world that's already there. Where work burns people out, it burns them out faster. Where a few already hold the opportunities, they keep more of them. Where care is left to unpaid people, they carry more of it.
I studied chemistry before computer engineering, and Le Châtelier's principle still shapes how I think. Disturb a system and it pushes back to the same balance. Speed it up and it just gets there faster. The only way to a different balance is to change the conditions it lives in. That's the work: not absorbing whatever happens to us, but changing what happens next, together. See it in practice ↓
Software engineer · Nonprofit operations · Mental health advocate
Turin, Italy
Le Châtelier in practice
In chemistry, a system at equilibrium pushes back against anything you do to it. Add more, take some away, squeeze it: under the same conditions it returns to the same balance, the equilibrium constant. A catalyst only gets it there faster. Only a change in the conditions, like the temperature of a reaction, moves the balance itself. Pick a disturbance and watch both happen.
At equilibrium
Atoms turn into each other at the same rate both ways, so the amounts stay level. That balance is set by the conditions. Pick a disturbance.
A product team ships an AI assistant that answers customers’ questions from the company’s own documents.
AI is a catalyst: it gets a team to the balance it already had, only faster. Change the balance first.
A critical vulnerability lands in a dependency, or a credential leaks.
Locking everything down after a leak is push-back. Making the safe path the easy one is a new condition.
A foundation opens a grant call with a short deadline.
Bending the project to fit the call is push-back. Starting from the need changes the conditions.
Two people in a group clash over how something should be done, and the work stalls.
Taking sides is push-back. A shared way to resolve conflict, that everyone knows, is a new condition.
A volunteer group moves its chats, files and sign-ups into one shared platform.
A new tool on old habits settles back into the old habits. Change where the work lives, not just the tool.
Don’t fight the push-back. Change the conditions.
06 Ideas · this page
Someone says it could be different
Who care is for, who work serves, who gets a say. This page is one of those voices.
The system pushes back
Left alone, things settle back where they were.
So I change the conditions
And this time it holds
An idea on its own gets pushed back like anything else. It lasts when it changes the conditions: who decides, who gets paid, who’s in the room.
In 1978, Italy closed its psychiatric hospitals with the Basaglia law. It held in Trieste, where Franco Basaglia’s team had spent years building community mental health centres to replace them. Where nobody built those services, the reform stalled. The law was the disturbance. The centres changed the conditions.
If this resonates, let’s talk. No project needed, just a conversation :) Say hello ↓
Technology, people, or neither
A project, a question, or just a chat with someone new. Some of my favourite people started as a random message, or a random encounter.
Don’t know how to start? Let’s break the ice.
How do you squeeze the toothpaste: from the end, or from the middle?