Need help with cloud-from-scratch?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

192 Stars 10 Forks MIT License 337 Commits 10 Opened issues


Build yourself a private self-hosted full-stack personal cloud system.

Services available


Need anything else?

Contributors list

No Data

[ Tested 2020.05.28 ] [ Updated 2020.06.03 ] [ Design Version 0.1 (Beta) ]


This project is very early in, it's mission is to maintain contemporary patterns and resources including specific instruction to create and operate personal cloud systems. If you find a 'bug' or have ideas please contribute with a new issue or by making a pull request. Thanks! Let's make this a great way to build our own cloud.

Cloud From Scratch

Build a self-hosted personal private cloud system from scratch.

You may be surprised to find that building and maintaining your own private cloud system, using your own equipment, hosted in your own home, is not only possible, it's relatively easy and is really fun and rewarding. The following instructions should provide everything you need to build a multi-host capable personal cloud computing platform from scratch. Using primarily off the shelf technologies and inspired by the "Arch Way" (Simplicity, Modernity, Pragmatism, User centrality, Versatility) this project aims to require only a small amount of technical attention and allow a wide range of expression and functionality. After completing the following steps you'll have yourself a fully functional personal private cloud system ready to be shaped into the services you wish. I don't know about you, but I know I'm excited, so let's get started.


When completed the system looks something like this.

[ EDGE NODE VPS ]                     |               [ LAN NODE ]

From this platform you'll be able to install, own, operate and access from anywhere, from any device, any cloudable software you choose to install.

Chat * Photos * Calls * File Storage * Music * Notes * Weather * News * Etc

You'll have your own public domain name like resolving data and apps from a cloud system you built from scratch running on equipment inside your own home network.

Cool, let's do it!


For this particular setup we'll use a... * Domain Name - Public Address * Cloudflare Account - Bandwidth Assistance * VPS Account - Privacy and NAT Mitigation (Linode/Digital Ocean/Vultr/Etc) * Raspberry PI - Local Host (v3 or greater, or adopt the instructions to a PC or Virtual Machine)

Note the requirements are needed for following the directions specifically, if you're comfortable doing something different feel free to adapt the instruction to suit your situation. For example, depending on your drivers you may or may not feel comfortable using Cloudflare. Some advantages of Cloudflare are privacy (hiding your actual server IP (if you proxy all the addresses,)) caching (if you expect a lot of traffic,) nice API control, and it's free. But, you trade that for unencrypted man in the middle, certainly an understandable deal-breaker for certain situations. If you find yourself in this situation Cloudflare can be skipped and your domain mapped directly to your edge node IP using your registrars dns panel.

If you're not already familiar with Wireguard and Docker you may want to first familiarize yourself with these as they play core roles in this project. These instructions assume you are comfortable with command-line based installation and configuration. For text editing we'll use vim, feel free to replace vim with the text editor of your choice.

If this sounds like your cup of tea dear reader read on. Or if you prefer something a little more automated consider one of these.


  • Provision Edge Node

    • VPS Instance
    • Wireguard
    • Docker
    • Caddy
  • Setup Domain

    • Register Domain (or use an existing one)
    • Cloudflare Setup
  • Build a Local Node

    • Configure OS
    • Wireguard
    • Docker
    • Caddy
  • Example Applications

    • Ghost
    • GOGS
    • Express
  • Troubleshooting

  • Optional Configurations

  • Discussion

  • Links

Provision Edge Node

The edge node functions as a lightweight, always online, public access gateway, mainly routes traffic, provides a layer of privacy and mitigates NAT issues.

Create a VPS instance at your favorite VPS service, like Digital Ocean or Vultr. (use these affiliate links to support this project: Digital Ocean | Vultr $100 free credit for 30 days.)

Any tier level with at least 512MB RAM should be enough.

Create a new instance using Debian 10 (Buster)

For the purpose of this tutorial we'll assume your edge node ip address is

Log in via SSH to your new server

$ ssh [email protected]

and update the system

$ apt update
$ apt upgrade


We'll use wireguard to route traffic through your NAT and provide a layer of privacy to keep your home IP address private. You can think of this kinda like a reverse VPN.

Install and configure wireguard on edge node.


Running services in docker keeps things tidy and manageable, we'll setup docker to contain our edge services starting with a reverse proxy web server.

Install and configure docker on edge node.


Caddy is super easy to use, automatically supports Let's Encrypt https certs and will be used to route our domain requests into our home node network.

Install and configure caddy on edge node.

Setup Domain

Domain Name

Use your own existing domain or register a new one. | namecheap -- support this project by using this affiliate link.


Use CloudFlare as your name server (set your domain name name servers to the nameserver names your cloudflare account instructs.)

DNS Configure an A record to point to the IP of your VPS. WITH cloudflare proxy enabled. eg

A @
with your domain name and
is an example address, use the ip address of your edge node whenever you see the

Configure cloudflare a CNAME record
with your domain name eg
) point it to your domain name WITHOUT cloudflare proxy (click to make a grey cloud). eg
CNAME edge

SSL/TLS Set to Full (strict) Option (otherwise you may get a 'too many redirects' error.)

Configure your domain name on the edge node.

GOOD JOB! At this point you have a working edge node with a publicly assigned domain name ready to accept and forward web traffic to your at home local network. Now might be a good moment to take a break and go for a little walk. Next up... local node!

Local Node

Local nodes live within your home network. In this system local nodes are pretty much where everything lives and happens. Cloud systems can be built from one or more hosts, but to keep things simple we'll start out with just one node, a Raspberry Pi.

Get Pi

Pi Kit $100 This is a kit, feel free to get any Pi setup v3 or better.

Install Raspbian

Note: if you don't have a Pi, you could use a virtual machine, or laptop if so note you may need to adapt these instructions to your situation.

Install and configure raspbian on your local node.


Here we'll setup the local side wireguard. When the local node boots and gets an internet connection it will automatically connect to your edge node and become virtually accessible to external requests.

Install and configure wireguard on your local node.


Local node services are setup within docker containers. Web requests are routed through caddy (running in a container) to other containerized processes but are all mapped into urls within your domain name.

Install and configure docker on your local node.


When a web request arrives at your edge node, it hits your edge node caddy instance, which routes the request through wireguard to your local caddy which then routes it to the docker container running the service at that url.

Install and configure caddy on your local node.

SUPER!! Everything is connected! You now have a publicly addressable domain name which serving content from a device within your local network. Cool. Next let get that node doing things.


A cloud needs to do things, you'll be able to build your cloud into whatever suits you. Here you'll find a few examples to get you started, we'll start with a simple caddy static file server then move on to dynamic container based applications.

Caddy static file serving

(note from here out you can assume we're dealing with the LOCAL NODE)

Edit Caddyfile

$ vim ~/Caddyfile

Comment out the

line and add
section. ``` {
file_server {
    root /usr/share/caddy/
#respond "Yay!  It really works!"   
Edit ~/www/

$ vim ~/www/ ```

Say something witty.

Static works too!!

Restart Caddy

$ sudo docker restart caddy_web_server


$ curl -v
Try testing from your browser on your phone or desktop.

Browse to []

You should see your wit!!

Here you might notice too that if you enter you'll be forwarded to the secure link

Fine work. Now for something more appy.

Dynamic (sky's the limit) applications.

Here's few apps setups to try, click one of these or jump to the more page for expanded lists.

There's plenty more one can install, and more becomes available all the time.

There you have it. Your own cloud. Let us know what you do with yours!


Sometimes things change or there might be a misstyped command. Here are some hints and tips to get the wrong back in line.

Doing More

Security Adjustments


Why run a personal cloud?

It's better to own your platform.

  • Ad Free (Calmer/Cleaner/Faster)
  • Control
  • Convenience
  • Persistence
  • Personalization
  • Privacy
  • Options
  • Speed
  • "Unlimited" Storage

Where to go next

  • add TC (traffic control)
  • multiple nodes
  • email hosting
  • https access lan side
  • advanced management
    • automated application distribution
    • system health monitoring
    • network boot and automated dynamic provisioning
  • remote service sharing and integration
  • firewall
  • cloud suite

Related Links


Similar Projects


Additional Reading


Web GUI automated run your own cloud systems

Prefer turnkey web gui based management? Take a look at these. * * * * * * * *

Useful tools and services


Related tech to consider


About Cloud From Scratch technology

The cloud from scratch project favors using established technologies over building new tech. * Easier to adopt * Familiarity * If something exists that works, don't build something new * Longevity * Leverage billions of dollars worth of existing energy * Well understood * Tested

Learn more about the tech *

Containerization and digging deeper * *

How to support this project

  • contribute feedback/ideas/recommendations/discoveries
  • report issues (this project contains moving targets)
  • create online videos
  • share on social media
  • sponsor

Have a suggestion, question, comment, or request? Would like to see instructions for a particular topic? Submit a NEW ISSUE.

Contact: [email protected]

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.