Skip to content Português

Affonso Xavier

Software Engineer · Full Stack

I'm not just a programmer — I'm a problem solver who happens to use code for it.

I build custom systems, from the first sketch to what runs in production — for teams that have outgrown the spreadsheet. I ship solo and fast, orchestrating AI agents, and I work well on a team too.

  • 3→1devs on the team, and delivery sped up instead of stalling
  • 250+daily users on the product I built myself
  • 5→2 dayscycle time, through CI/CD and automation
  • 10+ yearsbuilding for the web, since 2010
  • Open to a role or contract work
  • Remote
  • Manaus, Brazil (UTC−4 — full-day overlap with US Eastern)
  • Full-time, contract or project
Let's talk → See projects ↓

About

The work I'm proudest of is Tupã: a Backend as a Service I designed and build on my own, from architecture to packaging — a runtime resource orchestrator and a dynamic REST API framework, with CI/CD, observability and an SDLC automated by AI agents. It is not a side project: it is an ambitious product covering SaaS, and it is close to shipping. tupa.dev. I use Clean Architecture, DDD and SOLID because holding a system this size on your own is only possible with well-drawn boundaries and tests that let you sleep at night.

Since 2024 I have been the technical owner of a CRM at Obliviate — microservices architecture, TypeScript API, Angular SPA, payment integration and end-to-end tests — making the architecture calls, reporting directly to the founder and looking after the team. Over the course of the contract the team shrank from three developers to one, and delivery did not drop: it sped up. I automated the process from scratch and deploys went from biweekly to twice a week, with change lead time falling from days to hours. It is the most direct proof I have that the pace does not depend on headcount — and, before that, that I know how to deliver on a team.

A non-linear path, and that is exactly where this way of working comes from: I started with PHP and MySQL in 2010, spent six years as a graphic designer at a federal court without ever stopping programming — I kept Baú Arcano running through that whole period, solo, end to end: three web tools for tabletop RPG that reached 250+ daily users and made the press. Design taught me to think about the person using it before thinking about code — today that shows up in interfaces and in API design, and it is the same discipline behind Baú Arcano's successor, Inner Circle, also solo and AI-orchestrated.

What I am looking for: shipping end to end, on my own, with a focus on orchestrating AI agents — and I work well on a team when that is what the team needs. That holds for a full-time role just as much as for hiring this kind of delivery as a service.

Projects

Two cases with measured outcomes. What I built, against which problem, and what changed because of it.

  • Tupã

    Personal product · 2025 – present
    Challenge
    Build a Backend as a Service the size of a real product on my own — from architecture to packaging — and keep the delivery pace without a team.
    Solution
    A Bun/TypeScript monorepo whose domain is shared between the local backend and a multi-tenant SaaS server. A single resource contract makes it possible to add a database, cache or connection without touching the orchestrator core, and REST APIs are generated from the resource declaration. Around that: CI/CD with GitHub Actions, observability with OpenTelemetry, and process automation with Claude Code + MCP — with mandatory human review before merge.
    Outcome
    ~80% less CRUD boilerplate and cycle time down from 5 days to 2, with DORA Metrics collected to prove it — not estimate it.

    Bun · TypeScript · Angular · Tauri · MongoDB · Redis · PASETO · OpenTelemetry · Clean Architecture · DDD

    ↗ tupa.dev

  • Inner Circle

    Personal product · Baú Arcano evolving into a game · in progress
    Challenge
    Baú Arcano (2015–2018) had to serve a tabletop RPG community growing faster than one person had hours for.
    Solution
    Three web tools I built solo, end to end — real-time collaborative dice tables, a procedural name generator and a community-fed database with moderation. I am now evolving those tools — which succeeded on their own, before any graphical layer — into a game: a browser-based text RPG with real-time chat in the hubs, rebuilt solo and AI-orchestrated. The API is close to done, and the planned next step is a graphical version in Godot/Unity using ECS.
    Outcome
    Reached 250+ daily users and made the press — public evidence of a solo product with people actually using it.

    Real-time · Multi-user collaboration · Content moderation · Solo + AI

    ↗ Mapinguá Nerd, Feb 2016 — press coverage (Portuguese)
Want this kind of delivery on your team or as a service? Let’s talk →

How I work

Three formats, depending on the problem — and the scope adapts to what you have. The first conversation costs nothing and commits you to nothing.

  • Fixed-scope project

    Scope, timeline and deliverable agreed before anything starts. Fits when what needs building is already clear — a system, an integration, a migration.

  • Part-time allocation

    Set days per week inside your team, with the delivery pipeline set up by me. Fits when demand is continuous and you would rather not hire full-time.

  • Focused consulting

    Architecture, code review, or standing up CI/CD and observability. Fits when the team already exists and what is missing is a technical call or a process.

I do not work with a single package. The starting point is what you need to solve first, within what fits right now: we can begin with a small slice that already delivers value, grow in stages as the return shows up, and keep only a monthly support and evolution plan once it is live. A large project and a small one start from the same conversation.

Send me a message describing the problem in plain business terms — no technical spec, no fixed budget needed. I reply with my read of it, the format that fits, and a possible path in stages.

What people say

  • When the team dropped to one person, I expected delivery to stall. The opposite happened: we started shipping weekly, and I stopped having to watch the process closely.

    [Name][Role], Obliviate

  • I picked the project up after him and did not have to rewrite anything to understand it. Decisions documented, tests covering what matters, pipeline already in place.

    [Name][Role], [Company]

Contact

Got a project or a role in mind? Reach out — I reply fast.

© 2026 Affonso Xavier