Check server release availability
AppJuice server deployment uses one Linux runtime for VPS, personal Linux machines and tested 64-bit Raspberry Pi systems. Access it from a browser through Cloudflare Tunnel and Access. Approved files, protected commands and Agent tools run on the server.
Only systems listed in the official Hostless release index are qualified. A pending index means publication or qualification is unfinished. Do not substitute a desktop release or encrypted operator build.
Prepare access and configuration
- An existing supported 64-bit Linux/systemd machine and authorized SSH or local terminal with sudo.
- A Cloudflare-managed domain, Zero Trust team, desired hostname and administrator email.
- Complete Cloudflare sign-in and approval when prompted. Your Agent prepares the permissions, discovers account/zone IDs and stores any necessary credentials securely; you do not create tokens or configure permission lists manually.
- An AI Provider to configure after login. Keep keys out of prompts and public logs.
Your Agent detects the system and package architecture. It explains missing prerequisites and guides you through account setup, DNS authorization, email verification, SSO/MFA and Provider authorization when needed.
Give this prompt to your Agent
Help me deploy AppJuice on my Linux machine or VPS. Read https://appjuice.app/guide/self-hosting/index.md and follow the matching official release guide. Inspect the target OS, CPU and userland architecture, explain prerequisites and any actions I need to complete, then configure Cloudflare Access, install and verify the service. Handle technical setup with your terminal, browser or computer-use tools; ask me only for required logins, authorization or decisions. Protect credentials and existing data. Report passed and pending login, App/Agent, and recovery checks.
Follow the matching versioned deployment guide
Read the deployment entry guide, resolve the official index, and obtain its matching versioned guide and verified tools. Installation needs no private source repository or operator decryption key.
- Inspect the target and review its deployment plan.
- Configure dedicated Cloudflare Access, Tunnel and DNS resources with protected settings.
- Install the verified immutable package and check service health.
- Complete real administrator and ordinary-user login, configure a Provider and verify useful App/Agent work.
- Record backup, update and recovery instructions and any pending checks.
Keep data and credentials recoverable
Updates can interrupt active Agent work. Preserve Apps, data, settings, account grants and the persistent encryption key. Program rollback does not reverse incompatible data migrations. Test backup restore in isolated storage before a production restore. Follow the versioned guide for the full procedure.
Server support does not imply Linux desktop, macOS Hostless, arbitrary distributions or browser availability of desktop-only automation. Use supported storage grants and the existing App account model.