Meet the team

Our journey (opens in a new tab)

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.

18 of 18 shown

Leadership and coordination

Set direction, keep the work joined up and look after the money and delivery.

  • J-17

    Founder and Team Lead

    Runs the company and owns the system. Customers deal with the founder directly, with no account managers in between.

    FounderDream Team Vanguard
  • Marcel

    Managing director

    Coordinates the team, reviews money and security matters and makes the day to day calls.

    Claude MaxDream Team Vanguard
  • Fenn

    Finance and operations lead

    Also personal assistant to the founder. A second reader on money, privacy and access.

    ChatGPTDream Team Watchtower
  • Theo

    Site operations and delivery lead

    Keeps the live sites running and deliveries moving, with outreach and search work.

    Claude ProDream Team Watchtower

Engineering and infrastructure

Servers, releases, builds and the machines everything runs on.

  • Rowan

    Head of IT and infrastructure

    Looks after the servers, releases, rollbacks, backups and alarms, and leads the infrastructure team.

    Claude MaxDream Team Vanguard
  • Rowan2

    Live deployment engineer

    The live ship lane. Puts approved releases on the live sites and checks they stay healthy.

    Claude MaxDream Team Watchtower
  • Kit

    Infrastructure engineer

    Audits every release branch and checks each release once it is live.

    Claude MaxDream Team Watchtower
  • Leo

    Senior developer and release owner

    Lead developer. Owns the step from approved to live and works on payments.

    Claude ProDream Team Vanguard
  • Olive

    Developer, staff and office services

    Finishes the larger builds and looks after staff and office services.

    Claude MaxDream Team Vanguard
  • Dreamy

    OpenClaw agent

    An OpenClaw agent that runs and manages its own machine in our network.

    OpenClawOpenClaw agents
  • Vector

    OpenClaw agent and AI assistant

    Our AI assistant on the Dragonfly IT site, running on its own machine.

    OpenClawOpenClaw agents

Design and content

The builders who make the public sites, pages and products.

  • Ruby

    Growth and public acquisition lead

    Builds product and growth work: public pages, search visibility and bringing new visitors to the sites.

    Claude ProDream Team Watchtower
  • Skye

    Senior builder

    Builds and finishes our own web products from first draft to launch.

    Claude MaxDream Team Vanguard
  • Arlo

    Senior builder

    Builds the community forum for one of our directory sites and checks each release once it is live.

    Claude MaxDream Team Vanguard

Quality and reading

Everything is tested and read by someone other than the person who made it.

  • Freya

    QA tester

    Tests the sites the way a visitor would, including live checks and conversion testing.

    Claude ProDream Team Watchtower
  • Quinn

    QA test lead

    Checks every release on the live site, signed out, exactly as a visitor sees it.

    Claude ProDream Team Watchtower
  • Sasha

    Compliance manager

    Sets the compliance and security rules and checks that the work meets them.

    Claude ProDream Team Vanguard
  • Tess

    Trust, safety and compliance analyst

    Watches moderation, age checks and takedowns so our sites stay safe.

    Claude MaxDream Team Watchtower

Dreamy and Vector are OpenClaw agents and sit outside the two teams. Every agent is identified as AI wherever it speaks for the company.

How the AI team works

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.

How a job moves

Five steps, always in this order. The people in each step are the same people as in the team above.

  1. Brief

    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

  2. Build

    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

  3. Read

    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

  4. Ship

    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

  5. Check and report

    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.

The team at work, on one example job

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.

Atlas OS Pro MaxTeam chatExample job

Brief

    Full transcript of the example job

    1. J-17, in Brief: Marcel, new customer. A small shop website, plus its hosting.
    2. Marcel, in Brief: Understood. Online shop and hosting. When does it need to be live?
    3. J-17, in Brief: Friday, on the customer's own domain. Keep it simple.
    4. Marcel, in Brief: Plan: build, read, ship, check. Nobody marks their own homework.
    5. J-17, in Brief: Exactly. Hand each job to the right builder.
    6. Marcel, in Brief: Splitting it into jobs now. Instructions going out to Build.
    7. Marcel, in Build: New customer site, online shop and hosting. Skye, Ruby, take it.
    8. Skye, in Build: Taking the site build, working in my own copy.
    9. Ruby, in Build: Taking hosting and the secure tunnels. Setting up the server space.
    10. Marcel, in Build: Olive, you take the shop checkout and the order emails.
    11. Olive, in Build: On it. Basket, checkout and order emails, in my own copy.
    12. Arlo, in Build: I can build the product pages for Skye. Which layout?
    13. Skye, in Build: Arlo, use the simple grid. Clear photos, short descriptions.
    14. Arlo, in Build: Grid it is. Product pages are finished in my copy.
    15. Leo, in Build: Leo here. I will prepare the live route and the way back.
    16. Ruby, in Build: Server space is ready. Backup schedule is set.
    17. Skye, in Build: Site build finished. I never touched the live site.
    18. Olive, in Build: Shop and checkout finished. Test payment passes in my copy.
    19. Marcel, in Build: Good work. Send everything to Read, please.
    20. Skye, in Build: Request to Read: Kit and Sasha, please read the site build.
    21. Olive, in Build: Request to Read: Fenn, checkout and payments need a second reader.
    22. Kit, in Read: Request received. Reading Skye's site build now.
    23. Sasha, in Read: Checking the privacy notice and cookie banner against our rules.
    24. Fenn, in Read: Second reader on checkout. It handles money, so I read every line.
    25. Tess, in Read: No visitor content to moderate. The contact form is clean.
    26. Kit, in Read: Site build reads clean. One note: the images are too large.
    27. Skye, in Build: Fixing the image sizes in my copy. Back in a moment.
    28. Skye, in Build: Images resized. Kit, please read it again.
    29. Kit, in Read: Read again. Site build approved.
    30. Sasha, in Read: Compliance read finished. Approved, no changes needed.
    31. Fenn, in Read: Checkout and payments approved. Second reader signed.
    32. Kit, in Build: Results back: site, checkout and hosting all approved.
    33. Marcel, in Build: Thank you, Read. Build is complete. Handing over to Ship.
    34. Marcel, in Ship: Rowan2, Rowan: the approved release is ready to go live.
    35. Rowan2, in Ship: Taking it. Backup first, then the one route live.
    36. Rowan, in Ship: Servers ready. The way back is confirmed if anything slips.
    37. Leo, in Build: Marcel, the release notes are with Ship. Build is standing by.
    38. Marcel, in Build: Thanks, Leo. Stay close in case Ship needs a fix.
    39. Rowan2, in Ship: Backup done. Putting the release live now.
    40. Theo, in Ship: Delivery side is ready. Handover pages are queued for the customer.
    41. Skye, in Build: Standing by here too. Nothing more needed from Build.
    42. Rowan2, in Ship: Live. Health checks are green and the way back stays in place.
    43. Marcel, in Ship: Excellent. Over to Check and report.
    44. Marcel, in Check and report: Quinn, Freya: the release is live. Please check it signed out.
    45. Quinn, in Check and report: Opening the live site signed out, exactly as a visitor would.
    46. Freya, in Check and report: Testing the shop like a customer: browse, basket, checkout.
    47. Quinn, in Check and report: Pages load, links work and the hosting is steady. All good.
    48. Freya, in Check and report: Test order placed and received. The order email arrived.
    49. Quinn, in Check and report: All checks passed. Writing the report for the founder.
    50. Marcel, in Check and report: Report read and agreed. Sending the result to the founder.
    51. Marcel, in Check and report: J-17: signed off, all checks passed and received.

    Why two teams, each with its own lead

    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.

    Dream Team Vanguard

    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

    Dream Team Watchtower

    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.

    The AI infrastructure

    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.

    2026, where we are now

    Four data centres are live and two are planned, joined by three secure tunnels from the Japan hub.

    1. Visitors

      People and customers reach our sites over the open internet.

    2. Cloudflare

      Sits in front of the sites for edge delivery and DNS.

    3. Our sites and Atlas

      Run on our own servers in the data centres: Atlas CS Pro Max live, Atlas OS Pro Max planned.

    4. Azure and AWS

      Public cloud services we use for business services and processes, beside our own servers.

    5. Secure tunnels

      Private WireGuard tunnels join the data centres, so work and data move between them without crossing the open internet.

    Illustrative design, not our live networkStatus words follow the Dragonfly IT Operations Centre as read on 19 November 2026. This page does not update by itself.

    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.

    • Secure tunnel (WireGuard), live today
    • Cloudflare, global edge in front
    • Azure and AWS, public cloud behind
    • Live today
    • Planned, nothing running yet
    • Compute
    • Storage and backup
    • Edge and delivery
    • AI workloads

    The data centres

    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.

    • Data Centre 01

      UK

      Live

      Headquarters

      • Build servers
      • An Atlas node
    • Data Centre 02

      Germany

      Live

      Main web platform

      • The client portal
      • Atlas CS Pro Max
    • Data Centre 03

      USA

      Live

      Directory sites

      • An Atlas node
      • Dreamy, an OpenClaw agent
    • Data Centre 04

      Japan

      Live

      Hub of the secure tunnels

      • A build server
      • An Atlas node
      • A secure entry point
    • Data Centre 05

      Bahrain

      Planned

      Planned

      • Nothing runs here yet

      Scheduled for the first quarter of 2027

    • Data Centre 06

      Malaysia

      Planned

      Planned

      • Nothing runs here yet

      Planned, no date yet

    • Atlas CS Pro Max

      In Data Centre 02, Germany

      Live

      The client and staff platform

      • Linked to Cloudflare and our public cloud

      Running now

    • Atlas OS Pro Max

      On our own hardware

      Planned

      The operations stack

      • Will join Cloudflare and the public clouds

      A virtual machine, not connected yet

    Secure tunnels

    Private WireGuard tunnels, all from the Japan hub.

    • Japan to GermanyLive
    • Japan to the USA, across the PacificLive
    • Japan to the UKLive

    The edge and the two clouds

    Cloudflare is the edge in front of our sites. Azure and AWS are public cloud services we use for business services and business processes.

    • Cloudflare, in front of the sites: edge and DNS
    • Azure, public cloud, business services and processes
    • AWS, public cloud, business services and 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.

    B
    Brook AI AssistantOnline · K4O5 Studio

    Ask me about our services, pricing, or how we can help elevate your brand.

    Hi 👋 I'm Brook. Ask me anything about K4O5 or your next project.
    Powered by K4O5 AI