Free · No signup · Updated as I learn

Build your own stuff.

A field guide for people who are not engineers. Get your own server. Point an AI agent at it. Stop renting software you could host yourself. Keep the costs from running away while you learn.

I am not a developer. I do not write the code. I run a business, and over the last year I built a stack of about thirty-five services I actually use every day — monitoring, a password vault, a task manager, client dashboards, a daily podcast pipeline, several client websites — by directing AI agents rather than by learning to type C++.

Everything on this page is something I got wrong first and fixed second. It is not a computer science course. It is the set of moves that got me from "I have an idea and no idea how to build it" to "the thing is live and it cost me eleven dollars a month."

How the pieces fit together You talk to an AI agent in plain English. The agent runs on a server you rent for about six dollars a month. On that same server you run the free tools that replace your paid subscriptions. You plain English AI agent reads, runs, fixes YOUR SERVER · ~$6/MO Your projects Password vault Analytics Monitoring
The whole architecture. You describe what you want. The agent does the work. It all lives on one small server you rent — which is also where the free tools live that replace your paid subscriptions.
Who this is for

You run something — a business, a team, a side project. You keep having ideas that die because you assume you'd need to hire someone. You have used ChatGPT or Claude and thought "there's more here than I'm getting." That's you. Start at chapter one and go in order; each one assumes the last.

Six chapters

Roughly a weekend end to end, if you actually do the steps rather than just read them.

Four things I wish someone had told me

  1. You are not learning to code. You are learning to direct. The skill is describing what you want precisely, noticing when the result is wrong, and knowing enough to ask the right follow-up. That is a management skill, and you probably already have it.
  2. Owning the server changes what you're willing to try. When a new tool costs you nothing but twenty minutes, you try ten things a month instead of one thing a year. That's the whole game — not any individual tool.
  3. The costs that hurt are the invisible ones. Not the $6 server. The AI bill you didn't watch, and the eleven SaaS subscriptions you forgot you had. Chapter four and chapter five, respectively.
  4. Break it. It's yours. Everything I know, I learned by taking something down at 11pm and putting it back up by midnight. A server you're afraid to break is a server that teaches you nothing.

Frequently asked questions

Do I need to know how to code to follow this guide?

No. I don't write code and I built about thirty-five services this way. The skill you need is describing what you want clearly, noticing when the result is wrong, and asking a good follow-up. That's a management skill, not a programming one, and you probably already have it.

What does all this actually cost per month?

About $7 for the server, plus roughly $20 to $30 in AI usage if you build automations that call a model. The tools in chapter five are free and open source. For most small businesses that total is less than the SaaS subscriptions it replaces.

What is a VPS?

A VPS is a virtual private server: one slice of a large machine in a data center, rented to you. It has its own operating system, storage, and internet address, and nobody else can see inside it. It costs about six dollars a month and it is the foundation for everything else here.

How is Claude Code different from ChatGPT or a normal chatbot?

A chatbot writes code in a window and you copy it out, run it yourself, and paste the error back. Claude Code is an agent that runs on your server: it opens the real files, runs the real command, sees the real error, and fixes it. It closes its own loop, so you stop being the courier.

How do I stop my AI costs from running away?

Three rules. Use a cheap model for routine work and only step up to an expensive one when the cheap one fails twice. Create a separate API key for every project so you can see which one is spending. Put a hard spending cap on each key, so a runaway loop stops itself instead of draining your balance.

Is self-hosting safe, and what's the catch?

The catch is real: you become the person responsible for updates and backups, because nobody else is doing it for you. Mitigate it by setting up automatic backups the same day you install anything, and by only running projects that are actively maintained. If something is truly irreplaceable and you know you won't maintain it, paying someone else is a legitimate choice.

Which VPS plan should I buy?

The smallest one that comfortably runs several tools, which is about two cores and 8GB of memory. Buying a big plan up front is the most common first mistake. You can upgrade later with one click and no reinstall.

Disclosure

Some links on this site are affiliate links, which means I may earn a commission if you sign up through them, at no extra cost to you. I only link things I actually run. Where a free option is better than a paid one — which is most of chapter five — I say so and I make nothing.

Nobody paid me to write any of this. If a recommendation here ever stops being what I'd tell a friend, it comes off the page.