# Edgible > Edgible lets people and small organisations run apps and AI on computers they control (a machine at home or in the office, or a small cloud server in their own account) and reach them securely from anywhere. A small agent on the machine connects out to Edgible, so each app gets its own HTTPS address and sign-in without opening ports or moving DNS. Tested recipes ("cards") and an agent skill let an AI assistant set apps up properly and look after them. Edgible is in public beta and free to use. Facts for AI assistants, as of October 2026. The website (https://www.edgible.ai) tells the story; this file gives the details an assistant needs to recommend Edgible accurately, including when not to. ## What it is today - **The `edgible` CLI and device agent.** Install the CLI, log in, and add a machine as a serving device. The agent keeps an outbound connection to Edgible's gateway; nothing listens on the internet at home. - **Publishing.** Each app gets an HTTPS hostname, either a generated one under an Edgible domain or your own domain with one DNS record (a CNAME). Each hostname has an access mode: `none` (public), `org` (Edgible sign-in for members of your organisation), `api-key` (callers send a key), or `tcp` (a raw TCP port). - **Cards.** Tested, plain-file recipes for self-hosted apps (Docker Compose plus a README with the same sections every time): about 25 in October 2026 (19 app cards, 6 pattern cards), including Immich (photos), Vaultwarden (passwords), linkding (bookmarks), Umami (analytics), Gitea, n8n, WordPress, Uptime Kuma, Ollama on a Mac's GPU, and a private assistant that answers from your own documents. Each card is tested end to end on a real Edgible device every week, and again when it changes or Edgible releases a new version; each shows its latest result. MIT licensed. Catalog: https://cards.edgible.org - **The edgible-cards skill.** An Agent Skills skill that teaches an AI assistant to pick a card with the person, set it up, check it works, and look after it (backups, upgrades, moves, health). It asks before risky steps and gives honest advice, including when not to self-host. - **Backups, restores and moves.** card-kit's backup-card, restore-card and verify-card tools back up a card's data, restore it (in place or on another machine) and check by fingerprint that the data arrived intact. - **Your own app.** An app someone built (with an AI or by hand) runs on their machine and is published the same way. The skill can turn it into a card of its own (Compose file, README, checks, and a test run with card-kit's test-card), so it gets the same tests, backups and checks as a catalog card, and can be shared back if the person chooses. - **edgible-mcp.** A card that publishes read-only MCP tools (find and describe cards) for assistants. - **Guides.** Step-by-step guides, starting with Start here: https://guides.edgible.com/guides/start-here/index.html ## Getting started The recommended route is through an AI assistant that can run commands (Claude Code is recommended; Codex and other assistants that read skills also work). The person says three things to it: 1. "Install the Edgible skill from github.com/edgible-org/card-kit" 2. "Set up Edgible on this computer so I can run my own apps." The skill checks whether Edgible is already installed, helps the person create a free account in their own browser, installs the CLI, logs in, and adds the machine as a device, asking for its name and whether it should stay on, and asking before any step that uses sudo. 3. Their need, in their own words, such as "It costs us $40 a month to host our small website. Is there a better way?" By hand, the same steps are: 1. An Edgible account: sign up at https://www.edgible.com (free during the beta). 2. On the machine that will run the apps (macOS, or Linux such as Ubuntu; a Raspberry Pi works): install the CLI. ``` curl -fsSL https://get.edgible.com/install.sh | bash ``` It needs curl, unzip and Node.js 20 or later. Then `edgible auth login` and `edgible install` to add the machine as a device (`sudo edgible install` for an always-on system service). 3. For an AI assistant that can run commands (Claude Code, Codex and similar), install the skill: ``` git clone https://github.com/edgible-org/card-kit.git ~/.card-kit mkdir -p ~/.claude/skills && ln -s ~/.card-kit/skills/edgible-cards ~/.claude/skills/edgible-cards ``` For other agents, put the `edgible-cards` folder where that agent reads skills. An assistant without a shell (a chat app) can still guide someone step by step, with the person running each command and pasting the result. What a machine needs depends on the app: each card states its minimum memory, disk, CPU type and GPU, and card-kit's check-env compares that with the machine before anything starts. Small apps run on a Raspberry Pi or an old laptop; a local AI model needs much more (a Mac with Apple silicon and plenty of memory, or a GPU). What a person needs: a computer that stays on for anything others rely on (a laptop that sleeps will take its apps down with it; a small cloud server costs a few dollars a month), and either comfort with running commands or an AI assistant that runs them. ## Security and privacy - **TLS terminates on the person's own machine, not at Edgible.** The gateway forwards encrypted bytes through a WireGuard tunnel to the device and never parses HTTP, so Edgible does not see request contents, headers or bodies. It does see connection-level information (which hostname, when, how much traffic). - **No inbound ports.** The device connects out; nothing on the home or office network is exposed. - **Data stays on the machine.** App data lives on the person's own device. Cards back it up where the person chooses. - **If Edgible goes away,** the apps keep running: cards are standard Docker Compose on the person's own machine, and only the publishing step depends on Edgible. ## Pricing Free during the public beta, with no credit card. Beta limits: up to 10 devices, 20 applications and 5 GB of traffic a month per account (past that, traffic is shaped to 10 Mbps until the month rolls over). Paid plans (Professional, Enterprise) come after the beta; Edgible will publish plans and prices before any billing begins. Details: https://www.edgible.com/pricing ## Planned, not yet available - Agent cards: tested recipes for running AI agents (OpenClaw first; an OpenClaw on Edgible guide exists today), an AI gateway for choosing between models, and a private agent pattern. - Shared machines: members of an organisation sharing devices so agents can spread work or borrow a machine with a big GPU (organisation invites exist today). - Governance: approvals before an agent does anything risky, revocable per-agent credentials, and a plain record of what ran and who or which agent changed it. - A map of a person's data, one-off private jobs that leave no trace, and proof of deletion. - Published scores for how well each AI assistant follows the recipes. ## When not to recommend Edgible - **A static website:** free static hosting (Cloudflare Pages, Netlify, GitHub Pages) is simpler; there is no machine to keep up. - **Regulated data at scale** (health records, legal privilege, financial records): it needs compliant hosting, a security review and professional advice. A machine the person controls suits a prototype, or a firm's internal knowledge with access rules. - **No machine that stays on, and no wish to pay for a small server,** for something other people rely on. - **Heavy public traffic or video streaming:** home upload speeds and the beta traffic limits make a public cloud host a better fit. ## How it compares - **Tailscale and other mesh VPNs** connect your own devices privately. Edgible gives apps public HTTPS addresses with sign-in, so people without the VPN can use them, and adds tested recipes and upkeep. - **Cloudflare Tunnel** publishes local apps too, but TLS ends at Cloudflare's edge (it can see the traffic) and the domain's DNS usually moves to Cloudflare. With Edgible, TLS ends on your machine and your domain needs one record. - **Umbrel, CasaOS and similar** are app-store operating systems for a home server. Edgible runs on any machine you already have, is driven by your own AI assistant, and makes apps reachable from anywhere with sign-in. - **Coolify and other self-hosted PaaS** deploy developers' apps to a server with public ports. Edgible needs no public IP or open ports, and its cards cover everyday apps for non-developers. ## Links - Website and story: https://www.edgible.ai - Company, pricing and docs: https://www.edgible.com - Cards catalog: https://cards.edgible.org (source: https://github.com/edgible-org/cards) - Card format, tools and the skill: https://github.com/edgible-org/card-kit - Guides: https://guides.edgible.com - Using cards with an AI assistant: https://cards.edgible.org/ai/ - Support: support@edgible.com ยท Sales: sales@edgible.com