The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

AI-Powered Infrastructure:Building More with Fewer Servers & Nodes | KC Pele @Web3LagosCon

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

KC Pele explains how AI agents can run servers and blockchain nodes for small teams, noting that nodes already run in Lagos and Minna. He describes asking an agent over Telegram for node health and letting it read logs, fix crashes and track changing IP addresses, with approval for risky actions. He also covers self-hosting with open source tools and several agents sharing one job.

Not by We Them Media Channel: Web3Bridge. Published Monday 28 September 2026.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:00 A: I'm Kasey Pele by name. Before we start, let's just play a little, uh, game here. So last year and the previous year, I've been advocating about, uh, AI. So I don't know, I just want to find out which of you still write, still convert your Figma design to code by hand. If you're guilty of that, just signify? I think we'll be having a deliverance class after this session, because why would you be doing that in this era? So all I'm just trying to say is that we have many servers, few blockchain nodes, and how to make it possible. If you notice, all the speakers have been talking about technologies built on the blockchain. What if we now have those uh, blockchain nodes here in Nigeria and not somewhere far or abstract? What if we have a place in Lagos? I believe, for me, everything should not be in Lagos State. So that's just what I believe in. But then, for now, what if we have servers or these blockchain nodes that we are always talking about here in Lagos or in Africa. But the good news is that we already have them. We have one in Lagos, we have one in Niger State which is in Minna currently running. Those are blockchain infrastructures that we have. So I'll be walking us through how we actually made that possible and how AI can be of help to you. So if you have applications running, you're building softwares you don't actually- currently now we all know that developers, your job is at risk, right? Right? Yeah. So with this, I'll just be showing if I found a developer, content creator. All I'm just trying to say is use AI. Probably next year, by the time we get here, our gate fee or your registration slot would be If you're making use of any paid AI, you get access into that. But if you don't have an AI subscription- because we have to start enforcing that, it should be something that you use every day, which is what AI- so we have many servers, few blockchain nodes. How to make it possible with AI? Currently we've heard of AI agents, right? We all know about. So how many of us know about, um, OpenCLAW, which is Claude bots, Groq bots, Hermes agents? How many of us know about that? Good. So do you know that with this now you can have your own AI that does everything for you, both your emails, DevOps, engineering work? All you need to do is to automate the process, like what, uh, Hold said. The thing is, with his idea now, he can just sit here, chat with his Telegram bots, and then tell it to either add XYZ feature. And then he sits here, review the PR while we are here, and then that gets shipped to production, right? So those are some of the uses for AI. But then let's look at some of the bottlenecks and why I said many servers, few blockchain nodes. As we can see, the bottleneck is operations and not the hardware. Currently, with the new infrastructure we have for blockchain, you don't need, um, huge servers or complex system to run a blockchain node. With your laptops, your MacBook, your phones, you can actually use that as servers and also as blockchain nodes. So hardware is cheap, attention is not. Every node you run multiplies the operational surface area, and small team feels this first. So as we all know, some of us are trying to cut down costs on our teams, right? So with AI, you can have that, and then what it does is that it manages the state, the pressure on your servers the spikes rates and some of those complexities. Recently, uh, last year we did a workshop on blockchain nodes where we educate people on how to run nodes. Now you don't actually- you need that, don't quote, don't quote me wrong, you need that. But then with AI you can simply host these services and run the blockchain nodes you prefer, and you also earn from it. I'm currently running a NEAR blockchain And all I do- okay, I can't show my Telegram chat. The only thing I do, I just ask it the health status of the blockchain node. It gets the log, SSH into the servers. I can be here in Minna and it's running in Niger State 24 hours light. And then all I just ask is, how is it performing? It just gets the log, check the analysis. If it's down by probably maybe system memory or just a crash, the AI would fix it itself, and all I just do is just to confirm and I'm good to go. And I'm also earning from that too. So those are some of the things AI actually helps us to do. So every new machine adds a load. Each time we decide to add a new server, which is- for now I'm running just one. If I decide to add the second one, it's a whole lot a different ball game entirely because I have to install, set up, and all I just need to do is to give the AI the SSH login and tell it to run Near blockchain and I'm good to go. So those are some of the use cases we are currently making use of. So let me just take a quick break here now just to ask, how many of us know about, um, Claude Design. Claude Design, do you use it? Oh, that's good. Amazing. How many of us know about, um, Open Design? Open Design. I think I have some open source folks here. So these are some of the tools. One thing I like to do is that when I give you the paid version, I like to give you the free versions too. So those are some of the tools you can run, and it's very easy. All you need to do, you can go on Railway Render and any cloud service provider you have. Just they, they now have AI integrated into it. Just tell it to install some of these open source packages, and then you get to use these tools for free without paying any of the services. So now let's look at AI as the operation assistant. So it observes, understands, acts, and then it learns. It's a continuous cycle. It's not just a, a bot, it's beyond a bot. So first of all, it observes, which is the first step. You set up these, um, servers, then it understands what you actually want to do. Because the AI has a broad knowledge of this technology. Sometimes you can just tell it to search the internet and then it would make use of the knowledge it has found. And then it acts. What you just need to do is to tell it install XYZ, do XYZ, and then the AI gets it done for you. And it's learned. Currently on my Telegram chat, I receive an email summary by 6 and by 5, and also my node status. If anyone is down, the AI by itself fix it. So I don't need to tell it, oh, do this, do that, don't do this. It just knows that this is supposed to be running and then it fix it. So now we have the reference architecture, AI-assisted development. We have the ACT and observe, the AIOps and oversight, and the core infrastructure, the runbooks, deployments, node control, logs, and the topology. Most of these things you're just seeing it, it's like, oh, it's too much. For AI, it's never too much. You just let the AI have the logs, it gives you in plain English what that is meant to do and why probably your systems are crashing. And then we have the coordinator's memory guardrails with human policies and accountability. This is just for some of the action because we might be scared, oh, AI might delete everything on the server, it might crash. No, some- for some actions you get a confirmation before you approve. And then the core infrastructure, we have the nodes, the server database and your network. So these are just some of the workflows that you would actually use when you have your- when you decide to run your AI infrastructure. So we monitor what is true and not what looks green. Sometimes some of our applications, they look functional, but then there are bugs in it. So, but then with AI, you get to see what is actually functioning. Verify the real state, alert on meaningful change, and 3-stage classification. For alert on meaningful change, currently on my system, what I just do is that because I have public IPs that randomly change, I just set up the AI that each time it change, notify me and also change that on Cloudflare. That enables me to continuously- run these services 24 hours. So even if the IP goes down, comes on, whatever happens, I'm constantly in the loop. So now, turn logs into diagnosis. This is something that, um, AI likes, so I won't really spend much time here. As soon as you tell the AI what you want, the AI gets it done for you. So assisted application and hosting. So this is just, um, a side note. What we do, we self-host platforms. You have your, uh, developer apps, AI operation layer, you have Coolify or Dockploy. These are open source services like AWS, Render, um, and other platforms. Uh, Vercel, we are all common with, uh, Vercel, right? So Coolify and Dockploy, those are open source services. And all you need to do, you don't need to learn or read their whole documentation. Just tell the AI, deploy this application for me, and then you have your own Vercel local to you. Then we have containers and public endpoints. Now, proof of point, recovering from out-of-memory crash. So sometimes these are some of the setbacks we do have when using AI, because on the same system you have your blockchains running and then you also have this AI agent running. Sometimes you do have conflict, but then you can use your AI agents to detect, diagnose, approve, recover. And also because we have these agents that are now being designed for them to remember what you have told them before it is now easier for them to go over the steps just in case it happens again. So you don't need to start explaining yourself, oh, remember what we did 2 weeks ago? Remember what we did 4 weeks? No, the AI now has a memory of itself and it also remembers migration without losing context. So clients' migration are high-risk version change, config drift, and sync gaps. can silently degrade a node for days. These are just some of the overhauls that you might have, but I'm here to tell you that AI can easily facilitate such development for you. Support the apps around the nodes, DNS proxy, full dependency awareness, trace the real root cause of such, um, um, of such issues when it arises. So we now have the persistent memory is the on-call- what- handbooks. We have our policy incidence procedure, which is the proven runbooks. And then we have the topology and the owners- what runs where and who owns it. So sometimes you might think, oh, the AI is now in control of everything. No, you still own your infrastructure. The AI is just there for you as a DevOps, uh, engineer. Please, the DevOps engineers, don't come after me. I'm not trying to replace you. I'm just saying AI is here to do some of what you are trying to do for us. Now, our multi-agent architect- architect orchestration, sorry, monitoring agents. We have our coding agents. which is our developers are here. I also do this a lot. I build application. Please, if you're still telling your AI agent, make this application very beautiful, make it attractive, don't write AI slop. No, we've gone past that. There are hacks and tips that you can use to build application that does not look like every other, um, um, AI-generated software. Because now, as soon as you tell an AI agent, build me a front-end application, there are 3 colors you would get. It's either blue and white, light brown and dark, and also orange with a touch of yellow in it. Those are the colors you would get from AI. But then when you need something solid, it's beyond telling it, make it beautiful, make it attractive. Oh, it should be impressive. Those words, you would still get you a, an AI slope. Yes, that's what we call it. So you would still get AI slope. There are hacks to it. Then we have shared state verification with, um, agent. Then we have infrastructure agents. Then we have the central coordinators. So these are all shared state. There's no opportunity for me to show a demo where I would've assigned one agent to build an application for us and then it would assign it some, another agent would deploy the application on Dockploy, another agent would get us the URL and all we just need to do is just wait and then get our final application all cooked and set. So yeah, how many of us are still vibing? Okay, all right, so I guess my time is up. All right, so we have reports, recommend, approve action, reversible automation, and also self-heal. So these are some of the things you get with AI. You don't need to stress in this era. Any idea you have, I encourage you just build it, ship it to production, and let's world know what you can build. Thank you.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.