We do not build demos: our agents run in production, inside our own products, every day. We know what it takes for them to be useful, bounded and safe.
documented procedures our agents know how to apply
35
MCP tools exposed by 4fly to AI agents
20
AI designers in production at Wilogo
Figures as of 30 September 2026, taken from our own operations.
Our agents in production
Three agents, three jobs, one method.
Anna
AI host and assistant
A voice for the LeBisou community, and a day-to-day assistant.
Anna welcomes new members and hosts the chat of LeBisou, a community of over 135,000 members. The same agent also assists management by SMS and by phone: taking messages, reminders and outreach.
A defined personality and strict content guardrails
Every interaction is logged and auditable
Several channels: real-time chat, SMS, voice call
Escalation to a human whenever the situation requires it
An AI colleague for the tech team, with deliberately limited rights.
Alfred lives in Slack. You mention him to query the cloud infrastructure and databases: he answers briefly, with evidence. He was cloned from a general-purpose agent whose skills we kept, but not its authority.
Read-only access to the cloud (AWS) and databases
Credentials, state and container isolated from the rest of the system
Any change needs human approval, once per batch
Answers only authorised people, on explicit mention
Slack
AWS IAM
Moindre privilège
Docker
Lecture seule
Hermes
General-purpose engineering agent
An agent that builds, ships and monitors our products.
Hermes works from Discord: it writes and tests code, drives CI, deploys, watches servers, handles emails and publishes content. This very website was designed, translated and put online by it in one morning, under the supervision of Eddy Fayet.
More than 40 scheduled tasks, from backups to monitoring
A library of about 190 procedures that capture every lesson learned
Browser, terminal, databases and APIs driven end to end
Sensitive decisions submitted for human approval
Claude
Hermes Agent
Discord
CI/CD
Cron
Our method
What separates an agent that helps from an agent that worries you.
Least privilege
We clone an agent's skills, never its authority. Each agent gets its own credentials, limited to its scope.
Human in the loop
Free to read, approval to write. Irreversible or financial decisions are validated by a person.
Isolation
One agent, one container, one state. A mistake in one agent does not spread to the others.
Traceability
A log of every interaction and action: you can always explain what an agent did, and why.
Controlled costs
The right model for the right task: small models for triage, top-tier models for anything the customer sees.
AI inside our products
Beyond agents, AI is built into each of our products, wherever it serves a use case.
An MCP server for 4fly
35 tools expose bookings, flights, members and maintenance to AI agents. Authentication follows each conversation, so the agent inherits the member's rights, nothing more.
From first idea to production, with the same standards as our own products.
Scoping and audit
Spot the tasks where an agent creates value, and those where it must never act alone.
Agent deployment
Slack, Discord, SMS, voice or web: an agent installed where your teams work, with its own personality and scope.
MCP integration
Expose your tools and data to agents safely, with authentication and per-user rights.
Governance and security
Cloud rights, isolation, logging, human approvals: the part that lets you sleep at night.
Technologies
Claude (Anthropic)
OpenAI
Gemini
OpenRouter
MCP
Hermes Agent
Slack
Discord
Twilio
Docker
AWS IAM
PostgreSQL
Node.js
Python
Frequently asked questions
What is an AI agent?
An AI agent is an assistant that does more than answer: it uses tools (databases, email, browser, APIs) to complete a task, with defined rights and scope.
Can an AI agent act safely on my systems?
Yes, provided it is framed properly: minimal rights, free to read and approval to write, isolation and logging. This is the method we apply to our own agents.
Which AI models do you use?
We pick the model per task (Claude, OpenAI, Gemini…) and use routing that keeps cost proportional to value.
Where should we start?
With a narrow, measurable, low-risk use case. A first useful agent goes live on a simple scope, then grows once trust is established.