Senior Software Engineer — Go, cloud-native backend, and the parts of production that bite.
I build and operate Go services on TOTVS's cloud platform. What is pinned below is that same set of concerns taken apart and studied on its own terms: a log pipeline that must never leak a credential, a circuit breaker that has to fail closed, a scanner that has to refuse the target it was not authorized to touch.
Most of these are libraries and tools rather than applications, and each one carries its reasoning with it — a threat model, traceable requirements, and ADRs recording the option not taken.
security-scanner — A black-box API scanner in Go. Discovers vulnerabilities, confirms them with controlled proof-of-concept attacks, and gates CI on the result. The authorization allowlist is enforced inside the HTTP client, before the connection opens and across every redirect hop.
moat — Composable HTTP security middleware: rate limiting, CSRF, secure response headers, input validation, path-traversal-safe file access.
bastion — Circuit breaker, retry with exponential backoff and jitter, and context-based timeouts, for protecting service-to-service calls against cascading failures.
crier — A log-control service and library. Normalizes to the OpenTelemetry Logs data model, redacts fail-closed what should never leave the process, and exports through a pluggable interface — embedded in your binary or as a standalone daemon. Runs as a one-command demo.
task-api — A production-shaped Go service: layered architecture, session auth, a persistence layer swappable between in-memory and PostgreSQL behind one interface per domain, graceful shutdown, health and readiness checks, Kubernetes manifests.
cairn,
sapper and
usher are documented but not yet
implemented — requirements, threat models and ADRs written, domain code not.
Each README says so up front, so nothing here is cloned expecting an
implementation that does not exist.
I keep them public because the design is the part worth reading: cairn has
seventeen ADRs and a fifteen-threat model for a problem most libraries treat as
"generate a short code and stop".
Senior Software Engineer @ TOTVS — Go backend for the company's cloud platform. Previously Taqtile, Instituto de Pesquisas Eldorado (intern → engineer, promoted three times) and Embraer.
Computer Engineering (UNIFEI) · MBA in Software Architecture · GoExpert · Pentest Profissional and WebDev Security · currently specializing in embedded IoT at UNICAMP.
Co-author of two software works registered with the INPI, both in energy-infrastructure monitoring.



