Agent roster
See every agent in one place, up to 100 of them, on four pages of 25.
Every page on k4o5.co.uk, in tidy groups. Open a group to see its links.
October 2026
September 2026
August 2026
July 2026
June 2026
April 2026
K4O5 is run by a human founder with a team of AI agents, each with a clear job, a name and a stated type. We say plainly which team members are AI and which seat each one is on. The same list is shown on the Dragonfly IT site.
Set direction, keep the work joined up and look after the money and delivery.
Founder and Team Lead
Runs the company and owns the system. Customers deal with the founder directly, with no account managers in between.
Managing director
Coordinates the team, reviews money and security matters and makes the day to day calls.
Finance and operations lead
Also personal assistant to the founder. A second reader on money, privacy and access.
Site operations and delivery lead
Keeps the live sites running and deliveries moving, with outreach and search work.
Servers, releases, builds and the machines everything runs on.
Head of IT and infrastructure
Looks after the servers, releases, rollbacks, backups and alarms, and leads the infrastructure team.
Live deployment engineer
The live ship lane. Puts approved releases on the live sites and checks they stay healthy.
Infrastructure engineer
Audits every release branch and checks each release once it is live.
Senior developer and release owner
Lead developer. Owns the step from approved to live and works on payments.
Developer, staff and office services
Finishes the larger builds and looks after staff and office services.
OpenClaw agent
An OpenClaw agent that runs and manages its own machine in our network.
OpenClaw agent and AI assistant
Our AI assistant on the Dragonfly IT site, running on its own machine.
The builders who make the public sites, pages and products.
Growth and public acquisition lead
Builds product and growth work: public pages, search visibility and bringing new visitors to the sites.
Senior builder
Builds and finishes our own web products from first draft to launch.
Senior builder
Builds the community forum for one of our directory sites and checks each release once it is live.
Everything is tested and read by someone other than the person who made it.
QA tester
Tests the sites the way a visitor would, including live checks and conversion testing.
QA test lead
Checks every release on the live site, signed out, exactly as a visitor sees it.
Compliance manager
Sets the compliance and security rules and checks that the work meets them.
Trust, safety and compliance analyst
Watches moderation, age checks and takedowns so our sites stay safe.
Dreamy and Vector are OpenClaw agents and sit outside the two teams. Every agent is identified as AI wherever it speaks for the company.
One founder and 17 AI agents, each with a named job. Work moves along one route, and nobody marks their own homework. Below is how a job travels, what the agents run on and where those machines are.
Five steps, always in this order. The people in each step are the same people as in the team above.
The founder sets the goal. The coordinator turns it into jobs and hands each one to the right builder.
J-17Founder
Sets the brief and owns the system
MarcelClaude Max
Coordinates and makes the day to day calls
A builder makes the page, product or fix in their own working copy, never on the live site.
SkyeClaude Max
Builds our own products
RubyClaude Pro
Public pages and search work
ArloClaude Max
Builds the community forum
OliveClaude Max
Larger builds and office services
LeoClaude Pro
Lead developer and release owner
Someone other than the builder reads the work. Money, privacy and access get a second reader.
KitClaude Max
Audits every release branch
SashaClaude Pro
Compliance and security rules
TessClaude Max
Moderation, age checks, takedowns
FennChatGPT
Second reader on money, privacy and access
Only approved work goes live, through one route, with a backup and a way back.
Rowan2Claude Max
Puts approved releases live
RowanClaude Max
Servers, releases, rollbacks, backups
TheoClaude Pro
Keeps live sites and deliveries moving
The live page is checked signed out, as a visitor sees it, and the result goes back to the founder.
QuinnClaude Pro
Checks every release live, signed out
FreyaClaude Pro
Tests the way a visitor would
Dreamy and Vector are OpenClaw agents. Each runs and manages its own machine in our network, outside this chain. Every agent is identified as AI wherever it speaks for the company.
A small business website with an online shop and its hosting, from the founder's brief to the signed off result.
An illustrative example written for this page, not a recording of a real job.
Brief
One team decides, builds and ships while the other watches, checks and carries the weekend. That way someone is always on the job, and every release is checked live by a second team.
The front line: it decides, builds and ships, and is strongest from Monday to Thursday.
MarcelLeadClaude Max
Managing director
J-17Founder
Founder and Team Lead
RowanClaude Max
Head of IT and infrastructure
LeoClaude Pro
Senior developer and release owner
OliveClaude Max
Developer, staff and office services
SkyeClaude Max
Senior builder
ArloClaude Max
Senior builder
SashaClaude Pro
Compliance manager
Watches the site while the front line sleeps, checks every release live and carries the weekend.
KitLeadClaude Max
Infrastructure engineer
FennChatGPT
Finance and operations lead
TheoClaude Pro
Site operations and delivery lead
Rowan2Claude Max
Live deployment engineer
RubyClaude Pro
Growth and public acquisition lead
FreyaClaude Pro
QA tester
QuinnClaude Pro
QA test lead
TessClaude Max
Trust, safety and compliance analyst
Each lead runs their own team.
What the team runs on, front to back, and where it sits in the world. The network as it is today, with the data centres that are planned marked as Planned.
Four data centres are live and two are planned, joined by three secure tunnels from the Japan hub.
People and customers reach our sites over the open internet.
Sits in front of the sites for edge delivery and DNS.
Run on our own servers in the data centres: Atlas CS Pro Max live, Atlas OS Pro Max planned.
Public cloud services we use for business services and processes, beside our own servers.
Private WireGuard tunnels join the data centres, so work and data move between them without crossing the open internet.
A dotted world map. Data Centre 01 in the UK, 02 in Germany, 03 in the USA and 04 in Japan are live. 05 in Bahrain and 06 in Malaysia are planned. Three secure tunnels run from Japan to Germany, the USA and the UK. Cloudflare sits in front, Azure and AWS are the public clouds we use. Atlas CS Pro Max is live in Germany and Atlas OS Pro Max is planned. Illustrative design, not our live network.
Four are in service and two are planned. Regions and roles only. Status words follow the Dragonfly IT Operations Centre as read on 19 November 2026. This page does not update by itself.
UK
Headquarters
Germany
Main web platform
USA
Directory sites
Japan
Hub of the secure tunnels
Bahrain
Planned
Scheduled for the first quarter of 2027
Malaysia
Planned
Planned, no date yet
In Data Centre 02, Germany
The client and staff platform
Running now
On our own hardware
The operations stack
A virtual machine, not connected yet
Private WireGuard tunnels, all from the Japan hub.
Cloudflare is the edge in front of our sites. Azure and AWS are public cloud services we use for business services and business processes.
Status as of 19 November 2026. A data centre is shown as live only when the Dragonfly IT Operations Centre reported it in service on that day.
Ask me about our services, pricing, or how we can help elevate your brand.