bento

Your VPS, served on a tray.

Quickstart · Maintainers · Issues

---

Quickstart

bash <(curl -sSL https://raw.githubusercontent.com/felipefontoura/bento/stable/boot.sh)

TL;DR

Paste that on a fresh Ubuntu/Debian VPS, answer three questions (domain, admin email, public IP), and ~15 minutes later you have a hardened host, Traefik + Portainer with TLS, the apps you picked, and an HTML handoff report. Already know bento? Copy and go. Want context? Keep reading.

Prefer to drive it from Claude Code instead of the server console? Install the bento plugin and Claude does the whole flow over SSH — you never SSH in by hand or touch the bento menu. See Install with Claude Code. Ideal for beginners (works on Windows) and for consultants setting up a client's VPS: hand Claude an SSH-reachable host + a domain + an app list and pick up at the end with credentials + URLs.

Table of contents

• Quickstart
• Install with Claude Code
• What is bento
• How it works
• Stacks
• Prerequisites
• After install
• Operations
• For maintainers and contributors

---

What is bento

A guided installer that turns a fresh VPS into a hardened, TLS-fronted Docker Swarm with the apps you want — in under 15 minutes, with one terminal command.

You answer three questions (domain, admin email, public IP), walk through three guided steps (harden, infra, apps), and finish with a single HTML report you can hand off to a client. Every secret is generated for you; nothing is hardcoded.

---

How it works

A one-time bootstrap captures BASE_DOMAIN, ADMIN_EMAIL, and your VPS public IP (auto-detected). Then three idempotent, re-runnable steps:

Step 1 — Harden the system

An embedded copy of the ubinkaze hardening script: installs Docker, applies kernel sysctl + UFW (with limit ssh) + fail2ban + AppArmor + AIDE + auditd + chrony, creates a docker user with your SSH keys, then initializes Docker Swarm and the network_public overlay. Requires one reboot.

Step 2 — Install infrastructure

No prompts. Deploys Traefik (Let's Encrypt + HTTPS redirect) and Portainer at portainer.<your-domain>, generates a strong Portainer admin password, displays it once.

Step 3 — Install applications

Pick from a checklist. For each stack, bento:

1. Prompts only for env vars without sensible defaults. Hostnames default to <key>.<your-domain>; secrets are auto-generated; DB passwords are reused from the postgres stack.
2. Deploys via Portainer's API as a Git-backed stack so Portainer becomes the canonical source of truth for the running spec.
3. Runs an optional install.sh for post-deploy bootstrap (DB creation, migrations).
4. Prints the URL — you open and log in.

When Paperclip is in the deploy set, Step 3 offers an optional Authenticate AI providers step right after a successful deploy so the agent runtime can immediately call out to Claude / OpenAI Codex. The same menu is available any time from the main menu, or directly as bento-auth on the host. Full details in docs/reference/bento-auth.md.

---

Install with Claude Code (no server console)

Everything above — Bootstrap, Step 1, Step 2, Step 3, the post-hardening reboot, the unattended env vars, the recovery when something stalls — is drudgery you shouldn't have to do by hand if you "just want to use it." The bento plugin for Claude Code drives all of it over SSH. You never log into the server console or touch bento's menu: you talk to Claude, it does the rest and hands you back URLs + credentials.

You need: Claude Code, an SSH key on the VPS, and wildcard DNS (see Prerequisites). Nothing is installed locally except Claude Code — Docker/Swarm/apt all run on the VPS.