Frequently Asked Questions

Aiploy is a deployment platform for Go applications. You push your code with a single CLI command and Aiploy handles building, containerising, and routing it - no Dockerfiles, no CI pipelines, no config files.

An Aiploy account, the CLI, and a plan (every plan starts with a 7-day free trial). No Docker knowledge required, no cloud provider accounts, no YAML to write.

Run the one-line installer on Linux (amd64) or macOS (Apple Silicon):

curl -sSL https://aiploy.dev/install.sh | sh

It drops the aiploy binary into /usr/local/bin when that directory is writable, and falls back to ~/.local/bin otherwise (auto-appending it to your $PATH). Once installed, aiploy update keeps it current.

Those two platforms are the ones we ship. Windows is not supported.

1. Register an account and start a plan from the Plan page.
2. Authenticate the CLI (opens your browser):

   aiploy auth

   For CI or headless environments, pass an API key directly:

   aiploy auth <your-api-key>

   (Generate a key from the dashboard.)
3. Inside your project directory, create an app:

   aiploy init

4. Deploy:

   aiploy deploy

Your app comes online within seconds at a random *.aiploy.dev subdomain - you'll see the URL printed at the end of aiploy deploy.

Go only.

No. Aiploy generates one for you automatically based on your code. It produces a minimal, production-ready image - no configuration needed on your side.

Aiploy inspects your source code and picks up the port your app listens on. If no port is detected, Aiploy defaults to 8080. You can also set a PORT environment variable to be explicit.

Aiploy can automatically provision PostgreSQL, MySQL, and Redis alongside your app. Connection strings are injected as environment variables at deploy time - no manual setup required.

Every app gets a random *.aiploy.dev subdomain with automatic HTTPS. On Pro and Business you can also point your own domain at an app — see below.

Yes, on Pro (3 domains per app) and Business (10 per app). Add the domain from the app's page in your dashboard, then point a CNAME record at the target we show you. We check DNS automatically; once the record is visible the domain goes active and HTTPS is provisioned on the first request. Certificates are only issued after that check passes.

A root domain works too if your DNS provider supports ALIAS, ANAME or CNAME flattening.

No. Deploying requires a paid plan, and every plan starts with a 7-day free trial.

Every plan starts with a 7-day free trial. A card is required up front and nothing is charged until the trial ends, at which point it converts to the paid plan automatically. Cancel any time before then to avoid the charge.

One trial per account, ever. If you've already used yours, subscribing charges you immediately.

Starter is the entry plan:

• 1 app
• 32 MB memory, 0.1 vCPU (shared)
• 10 MB upload per deploy
• 1 database (PostgreSQL, MySQL, or Redis)
• 25 MB soft database size limit
• No backups, no custom domains

See pricing for the full comparison.

More apps, more memory and CPU per app, larger uploads, more databases, custom domains (3 per app on Pro, 10 on Business), and longer backup retention: every plan keeps automatic database backups, and Pro extends Starter's 2 days to 7, Business to 30 plus on-demand backups. See pricing for the full side-by-side comparison.

Paddle, acting as our Merchant of Record. They handle payment, tax, and refunds - see our Terms. Card details are stored by Paddle and never touch our servers. Your invoices are listed on the Billing page, and payment methods are updated through Paddle's billing portal (linked from that page).

Pick a plan on the Plan page. You'll see the prorated amount before confirming, and the change takes effect right away.

Cancel from the Billing page. You keep access until the end of the billing period you already paid for, and you can resume the subscription from the same page any time before it lapses.

Backups for your apps are deleted 7 days after the period ends.

Your apps are suspended: containers are torn down and any custom domains are dropped, but your app settings and environment variables are kept. Subscribing again does not restart them automatically - run aiploy deploy to bring an app back.

Your account is marked past due and a banner appears in the dashboard. You have 3 days to update your payment method through the billing portal; after that the subscription is downgraded and your apps are suspended as described above.

Run aiploy logs from your project directory to stream live container logs.

Aiploy builds a new image and recreates the container. The app is briefly unavailable during the restart.

No. Re-deploy an older version of your code to roll back.

Yes. Each plan has a soft limit and a higher hard limit - on Starter that's 25 MB and 37 MB. Once a database passes the hard limit, writes are blocked until it shrinks back below the soft limit. Reads keep working throughout.

Your app databases are backed up automatically on every plan and retained for the plan's retention window (2 days on Starter, 7 days on Pro, 30 days on Business). Business can also trigger a backup on demand with aiploy backup.

List what's available with aiploy backups and restore interactively with aiploy restore.

Your code is uploaded, used to build the container image, and then deleted. Only the running container is retained. Your source code is not stored long-term.

Yes. All .aiploy.dev subdomains are served over HTTPS with TLS certificates managed automatically.

API keys authenticate the CLI when creating apps and deploying code. They are stored locally in ~/.config/aiploy/config.json. You can rotate your API key from the API keys page.

Yes - visit your Account page and click Delete account. Deletion is immediate and irreversible. If you have an active subscription, cancel it first from the Billing page; you can delete the account once it's set to cancel.