Rogério
Chiavegatti
Technology Builder since 1996. Founder of INIT4 and creator of sisteminhas.com, acessivel.ai, and other creative initiatives.
The beginning
I started working with technology in 1996, when the web was still learning to walk. There were no frameworks, no YouTube tutorials, no Stack Overflow. There was documentation, experiments, and a lot of things breaking.
That's where I learned the first important lesson: systems that work are built by people who understand what can go wrong — before it happens.
What I do
I work in different areas of technology, but almost always start in the same place: a real problem that needs to be understood before it can be solved. From there, technology is a tool — infrastructure, security, software, processes, or a product, depending on what the problem calls for.
Through INIT4, I focus primarily on compliance, information security, and IT governance, with a strong presence in the audiovisual industry. The work began with preparation for TPN — Trusted Partner Network assessments and now includes assessing, implementing, and maintaining controls aligned with security requirements and frameworks such as ISO/IEC 27001.
In practice, this covers infrastructure, networks, firewalls, access controls, backups, continuity, policies, processes, risk management, pentesting, and assessment preparation. These are parts of a single compliance operation, rather than isolated disciplines.
With Sisteminhas, I take another path: developing small, focused, functional software to solve specific problems. The aim is to avoid unnecessary complexity, excessive dependencies, and subscription models when they make no sense — favoring simple, lasting solutions that can operate independently whenever possible.
Philosophy
Complexity is a bug, not a feature
Unnecessarily complex systems fail in unnecessarily expensive ways. The right architecture is the simplest one that solves the actual problem.
Security is foundation, not a layer
Added afterward, security costs ten times more and protects half as well. It needs to be present in architecture decisions from day one.
Documentation that outlives the team
Systems that don't document their decisions are systems that depend on specific people. That's a business risk, not just an engineering one.
Real experience beats theory
Books and certifications have value, but they don't replace years of systems breaking in production at 3am. That knowledge can't be learned in a course.
Why this site
iRoger.me is where I document the technical and strategic thinking behind INIT4 and the Sisteminhas products.
This is not a tutorial blog or marketing content. It brings out the thinking that usually stays inside the heads of people who build things, so it can be useful to others doing the same.
If something here helped you make a better decision, the site has served its purpose.