# Edgible Guides

> Hands-on guides for publishing a self-hosted service on a public HTTPS hostname with Edgible, using an outbound connection on TCP 443 and no port-forward. Every chapter is one job with one smoke test. Links below are raw markdown.

## Overview

- [Welcome](https://guides.edgible.com/index.md): what Edgible does, what the guides cover, and where to start
- [What Edgible does, and where these guides prove it](https://guides.edgible.com/capabilities.md): Edgible publishes a service running on a machine you own at a public HTTPS hostname, using only an outbound connection on TCP 443
- [Glossary](https://guides.edgible.com/glossary.md): Every term these guides use, in one place
- [Working with an AI tool](https://guides.edgible.com/working-with-ai.md): These guides are published so that a coding agent or a chat assistant can read them as easily as you can
- [For evaluators and architects](https://guides.edgible.com/appendix/for-evaluators.md): Where Edgible sits if you already know tunnels, reverse proxies, and self-hosted ingress

## Start here

- [Start here: chapters](https://guides.edgible.com/guides/start-here/README.md): From a blank virtual machine to a page the internet can load, without touching your router
- [1. Edgible on an Ubuntu VM](https://guides.edgible.com/guides/start-here/01-edgible-on-vm.md): Your own box, reachable from the internet, with no inbound port on your router

## Website on Edgible

- [Website on Edgible: chapters](https://guides.edgible.com/guides/website-on-edgible/README.md): The whole small-site stack on one machine you own, with nobody else holding the numbers
- [1. The site on the VM](https://guides.edgible.com/guides/website-on-edgible/01-site-on-the-vm.md): A folder of files, served by nginx on loopback, with nothing on the internet yet
- [2. Publish the site](https://guides.edgible.com/guides/website-on-edgible/02-publish-the-site.md): Your own pages on a public HTTPS hostname, with the router untouched
- [3. Umami on the VM](https://guides.edgible.com/guides/website-on-edgible/03-umami-on-the-vm.md): Analytics for the site, with the visitor data on your own disk
- [4. Publish Umami](https://guides.edgible.com/guides/website-on-edgible/04-publish-umami.md): One process on two hostnames: the tracking script open to the world, the dashboard behind your org login
- [5. Uptime monitoring with Uptime Kuma](https://guides.edgible.com/guides/website-on-edgible/05-uptime-kuma.md): A monitor that watches the public hostname the way a visitor would, and tells you when it stops answering
- [6. Tear down the website stack](https://guides.edgible.com/guides/website-on-edgible/06-website-teardown.md): Four hostnames gone, containers stopped, and a deliberate decision about the analytics data

## n8n on Edgible

- [n8n on Edgible: chapters](https://guides.edgible.com/guides/n8n-on-edgible/README.md): The back office workhorse: the automation that runs at 3am, on a machine in your own building
- [1. n8n on the VM](https://guides.edgible.com/guides/n8n-on-edgible/01-n8n-on-the-vm.md): The workhorse installed on your own VM, holding your credentials, reachable from nowhere yet
- [2. n8n editor through Edgible](https://guides.edgible.com/guides/n8n-on-edgible/02-n8n-editor-through-edgible.md): Your workflow canvas, on your phone, behind an org login
- [3. Public webhook hostname](https://guides.edgible.com/guides/n8n-on-edgible/03-n8n-public-webhook-hostname.md): One n8n, two published hostnames, two auth modes
- [4. A cron workflow](https://guides.edgible.com/guides/n8n-on-edgible/04-n8n-cron.md): Your first working automation, with no public endpoint to trigger it
- [5. A webhook a stranger can hit](https://guides.edgible.com/guides/n8n-on-edgible/05-n8n-public-webhook.md): An unauthenticated caller reaches your box, without touching the router
- [6. Tear down n8n](https://guides.edgible.com/guides/n8n-on-edgible/06-n8n-teardown.md): Remove both public hostnames before you stop watching the VM

## OpenClaw on Edgible

- [OpenClaw on Edgible: chapters](https://guides.edgible.com/guides/openclaw-on-edgible/README.md): The agent everyone is currently trying, with its shell and its admin console kept off the internet
- [1. OpenClaw on the VM (loopback Gateway)](https://guides.edgible.com/guides/openclaw-on-edgible/01-openclaw-on-the-box.md): OpenClaw on your own VM, answering locally, not yet published
- [2. OpenClaw Control UI through Edgible](https://guides.edgible.com/guides/openclaw-on-edgible/02-publish-openclaw-control-ui.md): Reach your agent from your phone, behind your org login
- [3. OpenClaw changes the public Edgible site](https://guides.edgible.com/guides/openclaw-on-edgible/03-openclaw-changes-edgible-site.md): Ask for a change in chat, and the public page updates
- [4. OpenClaw skill for the Edgible CLI](https://guides.edgible.com/guides/openclaw-on-edgible/04-edgible-openclaw-skill.md): Teach the agent to run the hosting, not just talk about it
- [5. Telegram pocket client for OpenClaw](https://guides.edgible.com/guides/openclaw-on-edgible/05-telegram-pocket-client.md): Message the agent on your VM from a chat app you already use
- [6. WhatsApp linked device for OpenClaw](https://guides.edgible.com/guides/openclaw-on-edgible/06-whatsapp-pocket-client.md): The chat client most people already have, and the one that can bind a Cursor session
- [7. Cursor Agent from OpenClaw on the Edgible site](https://guides.edgible.com/guides/openclaw-on-edgible/07-cursor-agent.md): Same page, same URL, this time built by a coding agent
- [8. Models beyond free Gemini](https://guides.edgible.com/guides/openclaw-on-edgible/08-models-beyond-free-gemini.md): Free tiers prove a hello
- [9. Tear down OpenClaw](https://guides.edgible.com/guides/openclaw-on-edgible/09-openclaw-teardown.md): Remove OpenClaw and its hostname without breaking the other guides on this VM

## LLM on Edgible

- [LLM on Edgible: chapters](https://guides.edgible.com/guides/llm-on-edgible/README.md): Private AI: the prompts, the documents and the weights never leave hardware you own
- [1. Ollama on bare metal](https://guides.edgible.com/guides/llm-on-edgible/01-ollama-on-bare-metal.md): A model answering on your own GPU, with nothing leaving the machine yet
- [2. Edgible publishes Ollama](https://guides.edgible.com/guides/llm-on-edgible/02-edgible-to-ollama.md): Publish Ollama over HTTPS with a bearer secret, not a forwarded port
- [3. n8n uses the published Ollama URL](https://guides.edgible.com/guides/llm-on-edgible/03-n8n-uses-ollama.md): One published hostname serves both n8n workflow nodes and the AI Assistant
- [4. OpenClaw uses the published Ollama URL](https://guides.edgible.com/guides/llm-on-edgible/04-openclaw-uses-ollama.md): An agent on one machine you own, thinking on a GPU in another, over HTTPS with a bearer secret
- [5. Tear down the published LLM](https://guides.edgible.com/guides/llm-on-edgible/05-llm-teardown.md): The inference hostname gone, the key revoked, and the Mac back on loopback