Wait, is it possible?
Yes.
It's possible.
You made it to week three, day one.
You've made it to the biggest week of the course.
You've made it to the finale week.
This is going to be huge.
This.
This is the week where.
Where you earn the right to put on your black belt with N810.
You are going to become a pro.
We're going to be doing some serious stuff.
We're going to be amplifying your business.
It's all about to happen.
So what is week three all about?
Week three is about getting advanced.
Week three we're going to we're going to do some self-hosting stuff today.
We're going to do advanced integrations.
We're going to look at MCP, such a hot topic and then context engineering and Subagents.
It's about getting more sophisticated with what we build as workflows and then and then a capstone project
to look at ways that you could be not just automating a business, not just accelerating your business,
but actually amplifying your business, able to do much greater things than were previously possible.
Being being able to truly differentiate your business or your client's business through the use of n-r10.
Well, there's no time to dawdle.
Let's dig straight in.
We're not going to any recaps this time.
We're going to get straight to action.
Cloud versus self-hosted.
So far we have been doing everything on cloud at I o and it was very quick to get started.
Right.
It was really simple.
And similarly it takes care of all the maintenance for us, upgrading the versions, keeping things
up to date, keeping things running.
It's all handled on their cloud, on their hardware, by any one of the things that we were doing a
lot last week was, was webhooks, where third parties call it in to our infrastructure, and if we're
running on the cloud, then that's really easy because Nan has URLs that they provided us with.
You remember that the test and production, and we could just give them to a third party and it could
call into Nan.
And Nan gave us a long webhook and took care of the fact that there had to be forwarded in to our instance.
It was just all handled where webhooks can get a bit messy otherwise.
And OAuth integrations, the harder kind of integrations were actually relatively easy with things like
Google Sheets and Gmail.
There was just something to click on and authenticate, and we were done.
And I'd said that OAuth is really hard, and you might be thinking, oh, it's not that hard.
Well, that's because we're running on net and cloud, and it's taking care of a lot of the heavy lifting
for us.
But there are some downsides of course.
First of all, there's the subscription pricing.
We've been on the free plan, or at least I have the free trial, which is like a 14 day or something,
and it runs out and then you have to pay.
And there's various plans, of course.
And the lowest one is, I think, $20 or £20 a month.
Uh, and it has uh, has some constraints in terms of what you can do.
And then you can tick up to higher paying plans.
And of course there's a bit less control.
It's not like you're running everything yourself.
So there are some constraints on what you can and can't do, and also privacy for people that want to
keep all the data on their computers and be completely in control of everything when it comes to privacy.
Well, you're not doing that.
You're running your software on any infrastructure.
And of course, no surprise at all the positives of running locally, yourself or self-hosting is the
sort of flip of that.
Uh, it's it's free, uh, but it's at least under the fair code license.
Remember, I spoke about that at the very beginning.
A license.
That means that you can run it for free.
You can you can sell your services to others.
What you can't do is directly compete with and sell the product itself to somebody else.
And that's totally fair enough, I get that.
I hope you do too.
And that's what they call the fair code license.
It's you've got total control and flexibility.
If you're self-hosting, it means you're installing the open source software yourself or the fair code
software yourself and you're running it.
You can do what you want with it.
It's it's yours.
And of course, privacy is big.
You're running the code.
Of course, you might still be calling out to third parties, but maybe you'll be running them locally
as well, so it gives you much more control of your data.
But the obviously the it's harder, it's harder.
The setup is more time consuming as we're about to see.
Maintenance is more tricky.
And the webhooks webhooks aren't so easy anymore because it's running on your local box.
And you might be, as I am, just sitting behind some internet service provider.
I don't have a public web address to my computer, so if I'm running it locally, then how would an
external, how would how would slack send a webhook to to my laptop right there.
How's it going to do it?
It can't put localhost because that would just be localhost for for the slack box.
So somehow there's got to be a web address that it can call to connect into my laptop.
And that's not so easy.
And then oth of course it's the full OAuth for people that know about OAuth, it's like setting up an
app.
It's like, oh, there's a lot to it.
So so it's it's definitely more of a pro situation to be in that is self-hosted.
And now when I say self-hosted, that can mean two things.
You can self-host as in literally installing it on your own computer, running it locally.
I'm looking down at my computer.
That's right.
Right there.
You don't know that my computer is there, but it is, uh, so you can run it locally on your computer
and that would be self-hosted.
You could also then deploy it to a cloud computer that you're in charge of, like an AWS box or a box
on Google's GCP or on Azure.
You get a box and you deploy it there and manage it there on the cloud.
And that's still considered self-hosted.
It's like you've taken what cloud has done and you've deployed it yourself and you have complete control
over it.
It's yours.
And so, uh, and and self-hosting means both of those things.
And what we'll do on this course is we will install it locally and run it there.
I'm not going to do the deployment to the cloud part, because that has nothing to do with Nan and nothing
to do with AI and everything to do with DevOps, but platform engineering.
And I do cover a lot of that on my ML ops course.
If you if you are interested, you could look at that.
But anyone that knows how to deploy something to App Runner or or Google, GCP, cloud run, something
like that, you can you can basically use that to do it.
So it's a parallel task.
You could also give it to it to some DevOps person to do it for you once you've deployed it locally.
So when I say Nan self-hosted, we'll be doing it on our own computers.
That's what we'll be doing.
And after saying I wasn't recapping anything, there is a just a quick recap reminding you of the authentication
patterns that we covered all the way back.
I think in week one of the different ways you can have credentials with a third party that you're integrating
with, and the simple one is when you have an API key, because you're just connecting all of your platform
to another platform like OpenAI, you've got a key with them.
You make the connection.
The API key checks out and you're done.
And then there is OAuth or OAuth two is the full name which which we worked on.
First of all with this very simple way.
It didn't seem that hard at all, like with Google Sheets and Gmail, and I think with slack as well.
I think everything that we've done so far has been this simple way where OAuth two hasn't been so painful.
And that's because we've been going through an cloud, and they've already done some of the heavy lifting
to put in place the kind of OAuth connectivity.
But if you don't have that, if you're if you're working locally or for some of the integrations on
cloud, you have to do the full on OAuth two.
And there is a bit of lift to this.
There are a couple of hoops to jump through.
It's totally doable, but it is a bit of a procedure and and we'll be doing that okay.
And now this this local business, this self-hosted engine.
This is somewhat optional for you.
It's not like this is required.
So there is something of a fork in the road.
At this point.
If you are someone that is reasonably technical, then you should absolutely try this local setup.
That will do together right now, and you could keep going with this for the rest of the week.
You'll need to do a few things along the way, so you'll need to use something like Ngrok for webhooks.
If you already know what Ngrok is, then you might as well you know all about this.
Then do it and we'll do OAuth the advanced way together once, and if you want to keep doing it, you'll
have to do that every time.
And you know there's something to it.
But once you've done it a few times you'll be used to it.
But you should really only take this path if that all sounds good to you and makes sense and you know
how to do it.
Plus, you're super interested in having the flexibility and the privacy of running non locally in a
self-hosted way.
If you're super technical and you want to run models locally as well, then instead of using open router
that we'll be using to call open source models in the cloud, you could run locally.
If you've taken one of my technical courses, you've already done that and you can then connect any
N to a llama and run everything locally.
And if your box is big enough to run something like GPT OS 20, then you'd be able to carry out a genetic
flows running everything locally.
And also, if you've taken my MLOps course or you know about things like App Runner, you'd be able
to take your local install and deploy it to the cloud as well.
So all of these things could be in scope for you, should you wish.
And I'll be honest with you, originally it was my plan to do this with everyone, not to have a fork
in the road, but that this would be the way we would embrace it and move forwards with local install
for everyone.
But I did realise as I went through this myself that it gets to there's more sort of technical fussing
around than might be desired for for many of you, and it could be too much of a distraction.
And if you're already productive in cloud, and if you don't mind paying the £20 a month, $20 a month,
you can see I'm in London then.
Then you might say, ah, okay, I get it.
It's nice to see that I can run it locally, but I'm happy with cloud and I'm more focused on the commercial
side of this.
And yes, if you're more focused on the commercial side, then I would suggest, hey, try once to install
locally as we will do in a second.
It's optional.
You don't need to.
If you don't want to, you can just watch me do it and take that in and then just go back to the cloud
and do everything else in the cloud.
You'll have to sign up for a paid plan and consider going local later if you wish to.
And what I'm going to do is today we will do the the technical part, the installing it locally, which
you can just watch or, or try and go along with as well.
And then for the rest of the week, you know what?
I'm going to do it on the cloud so that it's it's not getting into the technical nitty gritty where
we don't need to.
We're going to focus primarily on the commercial bang for the buck on what can we do to amplify your
business using Nw10 and the technical folk?
You should try and replicate this running it locally.