Felipe de Almeida
Software Engineer & Architect · Engineering Leader
I build distributed systems, developer platforms, and cloud infrastructure.
You're one of 0 people here right now — and this page is a live distributed system, streaming presence, geolocation, and events in real time.
- .NET 10
- SignalR
- RabbitMQ
- Redis
- PostgreSQL
- OpenTelemetry
- React 19
- Docker
- Terraform
what i solve
How can I help you?
I don't sell technology. I fix the process that today only moves when someone remembers to do it by hand.
Your team spends the day doing work a machine would do.
An order arrives on WhatsApp and someone retypes it into the system. Monday's report gets assembled by hand. The reconciliation nobody has time for. That becomes a routine that runs on its own, on schedule, without forgetting.
- today
- someone retypes it, every Monday
- after
- runs on its own, on schedule
examples
- The WhatsApp order entering the system on its own
- Monday's report ready on Sunday night
- A nightly reconciliation across two databases that reports only what disagreed
behind it: Queues and workers, scheduling, API and webhook integrations, end-to-end automated testing.
Someone on your team spends the day filling in a spreadsheet.
The spreadsheet can stay — it just doesn't need to be filled in by hand. The data is born where it already happens and arrives there on its own. From there it becomes a dashboard that updates itself, that you can filter and cross on the spot, and that acts when a number crosses a limit you set.
a dashboard that updates itself
examples
- A closed sale landing on the dashboard the moment it happens
- Cash position updating itself instead of closing on the 5th
- Stock below minimum alerting whoever buys, with nobody watching
behind it: Continuous ingestion from the source tool's API, data modelling and aggregation, interactive dashboard, and trigger rules firing a webhook, queue or notification.
You want AI in what the company already does, not in a demo.
An assistant that answers on top of your documents and your data, respecting who is allowed to see what. And, where it makes sense, your team getting things done from inside Claude or ChatGPT.
an answer with the source cited
examples
- “How much is left on the X contract?” answered without opening the system
- An internal policy answered from the document that already exists, with the source cited
- A ticket opened, classified and routed straight from an email
behind it: An MCP server over the system, identity and permissions resolved per user, an indexed company knowledge base.
The idea hasn't left the drawing board yet.
You know what you want to build and you need someone to build it — and then to lead the team that keeps building. From the first prototype worth showing a customer to the team that runs on its own.
an MVP live and a team running it
examples
- An MVP live in weeks, to validate with real customers
- The first engineer hired and onboarded
- The architecture decision taken now that doesn't trap you a year from now
behind it: 12+ years in .NET and React, event-driven architecture, Head of Technology for teams of 3 to 13.
live proof
Watch it happen
A live slice of the same system behind this page: real visitors, real locations, streaming in as they happen.
Live locations
Live activity
No events yet.
Ask about me