Start a conversation
Menu

About

Lucas

Founder, AI and cloud architect. AI agents, cloud and security architecture.

Positioning

I run open-source AI agents on my own infrastructure every day. They read my mail, watch my systems and do the work I used to do by hand. I also build and benchmark agent tooling, so I know where these systems break, where they leak and where they genuinely save time.

Before that I spent years as a cloud and security architect. I've been the engineer debugging production at 1 am (true story). The architect redesigning a system that should never have been built that way. The lead explaining to the board why the migration will take longer than planned. I've built SOC environments, consolidated fragmented infrastructure into orchestrated clusters, and designed identity architectures across Azure, AWS and GCP. At companies with 15 people and companies with 9,000.

ataides. exists because I got tired of watching good teams lose months to bad architecture, and AI is repeating the pattern. I don't ship slides. I don't sell promises. I don't outsource the hard parts. I deploy the agents, I write the code and I own the result until your team does.

"If we take the work, we do it right. Not because someone is watching. Because we cannot do it any other way."

Kodawari, from the ataides. manifesto

Expertise

What I work with every week.

Agents on top, cloud and identity underneath, compliance running through both. Multi-cloud by necessity, not by fashion.

AI and agents

  • Hermes Agent
  • MCP
  • LLM gateways
  • RAG
  • Evaluation
  • Agent security

Platforms

  • Azure
  • AWS
  • GCP
  • Docker
  • Kubernetes
  • Terraform
  • GitOps

Security

  • Keycloak
  • Entra ID
  • Okta
  • Zero Trust
  • IAM

Compliance

  • LGPD
  • GDPR
  • ISO 27001
  • ISO 42001
  • NIST AI RMF
  • SOC 2
  • CIS

How I work

Direct, documented, handed over.

  1. You talk to the architect.

    No account manager, no rotating team. The person who scopes the work is the person who does it and the person you call when it breaks.

  2. Everything is written down.

    Decisions, diagrams, runbooks, infrastructure as code. When the engagement ends, your team runs it without me. That is the point.

  3. Security is a design input.

    Identity, permissions, network boundaries, encryption and audit evidence are part of the first diagram, not a phase after go-live. Agents get the same treatment as people.

  4. Nothing ships on a promise.

    Every agent and workflow gets a baseline, an evaluation set and a number that says whether it worked. If the pilot does not pay off, you hear it from me first.

  5. Price and scope are fixed before work starts.

    Fixed scope, time and materials with a monthly cap, or a retainer. You choose; nothing starts until it is in writing.

Manifesto

Seven principles the work is held to.

Borrowed from Japanese craft vocabulary because no English word carried the same weight. Each one is a standard I refuse to lower.

  1. Ikigai reason for being

    I build because I have to.

    Every product starts with frustration. Something is broken, fragmented or unnecessarily complex. Instead of complaining, I sit down and build the thing that should have existed already.

  2. Kaizen continuous refinement

    Ship it. Then make it better.

    Version 1.0 is not the destination. It is the first honest conversation with reality. Shipping fast never means shipping broken: every commit is intentional, every config reviewed. Urgency without recklessness.

  3. Ichigo Ichie one encounter, one opportunity

    Every deploy is permanent.

    There is no rehearsal. Every push to production is a moment that cannot be undone, so each one gets the weight it deserves. Not with fear. With intention.

  4. Ma the power of negative space

    What I remove matters most.

    The best security is the attack surface that does not exist. Every dependency is a liability, every permission a risk. I build by subtraction: fewer moving parts, smaller blast radius, less to break.

  5. Shibumi effortless elegance, quiet authority

    The work speaks first.

    The repository is the resume. The uptime is the credential. The documentation is the pitch deck. When it just works, with no asterisks, that is the only proof that matters.

  6. Shokunin the devoted craftsman

    I build for the person who reads the source.

    The engineer who checks the commit history. The architect who reads the config before approving the pull request. The operator who opens the runbook at 3 am. The joints are clean even where no one will see them.

  7. Kodawari uncompromising commitment to standards

    The standard is the standard.

    The same rigor applies to a project with twelve users and a platform with twelve thousand. The tests pass or they do not. The scan comes back clean or it does not ship. The infrastructure is documented or it is not done.

This is not a company that became serious. It was built that way.

Next step

Work with me.

Send me what you are dealing with. I answer within one business day, and I will tell you honestly whether I am the right person for it.

Start a conversation Email contact@ataides.com