Mohz · IOX — via VPN — Venha Pra Nuvem

Technical leadership of crowdfunding platforms in a regulated environment (Mohz and IOX)

Apr 2026 — Present

Technical direction of the Mohz and IOX crowdfunding platforms: architecture, engineering governance and traceability in regulated fintech.

  • Azure DevOps
  • SonarCloud
  • Husky
  • CI/CD
  • Multicloud
  • Observability

Context

Crowdfunding platforms — Mohz and IOX — run via VPN — Venha Pra Nuvem, operating simultaneously within a larger portfolio of digital products.

Risk at stake

Crowdfunding involves third-party money and regulatory obligations: an integration failure, incomplete traceability or a poorly managed promotion between environments affects investors and issuers, not just the system.

Architectural decisions

What was decided, and why it was the defensible decision

Each decision below carries an alternative that was discarded. That is the point where architecture stops being a technical preference and becomes risk control.

  1. Backlog hierarchy used as a technical traceability layer

    The Epic → Feature → User Story → Task hierarchy in Azure DevOps was treated as an audit structure, not a process formality. Every commit is linked to the work item that originated it, so the reason behind any change in production can be reconstructed without relying on the memory of whoever made it.

  2. Automating the path from commit to pull request

    The engineering cycle was automated with Husky, AI and Azure DevOps: branch and commit standardization, work-item linking, quality validation and pull request creation. Compliance became a consequence of the workflow instead of depending on individual discipline — which is the first thing to give way under deadline pressure.

  3. Quality gate placed before human review

    SonarCloud as a precondition for every pull request, with test and coverage standards defined in writing. Code review now discusses design and decisions instead of spending attention on what the tool detects on its own.

  4. Environment promotion with preflight checks and records

    No promotion between environments without a prior check and a record of what was promoted, by whom and from which work item. In a regulated domain, being able to reconstruct the history of a change matters as much as the change itself.

Role

Leading the squad and the technical direction: architecture, observability, security and modernization discussed with product, QA, infrastructure and the client. Investigation of incidents and integration failures, with Sprint Reviews and Plannings used to turn technical findings into backlog priorities.

Perceived impact

A standardized, auditable engineering cycle, with changes traceable from work item to production and a shorter distance between what is planned and what actually ships.

  • End-to-end change traceability
  • Auditable engineering governance
  • Technical direction in day-to-day operation

Environment

Regulated fintech, multiple platforms operating simultaneously, a multicloud context and direct interaction with management, product and the client.

Schedule a technical conversation to define architecture and evolution

We start from your current context to define the next cycle with technical clarity and safe execution.