Install the console first, then set up AppSweet in your browser. You do not need to prepare Compose files, generate service passwords or fill in an environment file. For an existing Dokploy host, use Install on Dokploy.
This guide installs the current alpha release. Alpha releases are preview software intended for evaluation in a non-production environment. Release downloads and image pulls are public. The installer selects the release from the automatically updated alpha channel.
What you need
- Ubuntu 24.04 or Debian 12, on amd64 or arm64, with root shell access.
- 4 CPUs, at least 8 GB of memory and 40 GiB free on Docker's persistent disk.
- A stable public IPv4 address and reachable, unused ports 80 and 443.
The installer installs missing supported Docker/Compose packages and reuses a compatible runtime. It refuses an incompatible runtime without replacing it. It does not change your firewall rules.
Step 1 — run the installer
Run from a root shell on the server:
curl -fsSL https://releases.appsweet.app/install.sh | sh -s -- --channel alpha
You can download and inspect the script first. It verifies the selected signed
release, prepares private installation state and starts the console over HTTPS.
The initial console hostname is generated from the installation ID and public IP.
To use your own hostname, add --console-hostname console.example.com; its DNS
must point to this server. For multiple public addresses, also supply
--public-ipv4 with the intended IPv4 address.
Step 2 — claim your console
When HTTPS and installation identity have been verified, the installer prints a private claim link. Open it and enter your company name, your name, your email address and a password. You become the company owner. Keep the link private: it expires after 24 hours and allows its holder to claim this installation.
The installer retains state in /var/lib/appsweet by default.
Step 3 — configure AppSweet
In the console, configure the app, console and file addresses, file storage, outgoing email and backups. Use the included storage or your own S3-compatible provider. The included storage needs no manually generated access keys.
Send the test email from Email; your mail server must use TLS or STARTTLS. Encrypted backups need an S3-compatible destination outside this server. If you defer backups, updates stay unavailable until a recent verified backup exists.
Settings are saved as drafts. Run the checks and correct any reported DNS, SMTP or storage problems before applying them.
Step 4 — start it
- Review & apply. AppSweet's services start now.
- Confirm your password. This creates your owner account in the app, with the same email address and password.
- Save the recovery key.
- Activate company. This needs a successful test email.
- Install AppSweet for Mac, enter the company endpoint the console shows, and sign in.
Use the console for later settings changes and updates. From now on, your console password and app password change separately.
Retry an interrupted installation
Fix the reported prerequisite and rerun the same command. It retains the selected release, installation identity and generated keys. After bootstrap completes, rerunning returns you to the console without replacing the configured deployment.
If the claim link expires while the installation is unclaimed, rerun the same command
with --renew-claim. This issues a new link without resetting an existing administrator.
Never delete deployment volumes to retry installation.
For the default alpha installation, renew an unclaimed link with:
curl -fsSL https://releases.appsweet.app/install.sh | sh -s -- --channel alpha --renew-claim
See Troubleshooting for common failures.