AnySites

// GETTING STARTED

Quick Start

Connect a repository and deploy your first app on AnySites.

AnySites deploys a Git repository as either a container app (a long-running process behind a reverse proxy) or a static site (files served directly, no server process). Both start the same way.

1. Connect a Git account

GitHub connects with one click via OAuth. GitLab (including self-hosted instances) connects with a Personal Access Token, since most GitLab installs aren't reachable for OAuth callbacks. Do this once per account — see Connect Your Git Account.

2. Create a project

  • Pick Container for anything that runs a process (Node, Python, Go, ...) or Static for plain HTML/CSS/JS with no server.
  • For a container app, set the tech stack (Node / Python / Go / Other). If it isn't Node, you'll need your own Dockerfile — see Deploy with a Custom Dockerfile.
  • Select the repository and production branch (defaults to main).
  • Set build/start commands and the port your app listens on (default 3000). These only matter if AnySites is generating the Dockerfile for you — see Build and Start Commands.
Creating the project also tries to register a webhook on your repository automatically, so future pushes to the production branch trigger a deploy. If your Git account connection is missing or expired, this step fails silently and the project page will show an "auto-deploy not connected" warning with the webhook URL — see Deploy Webhooks.

3. First deploy

Click Manual Deploy to build immediately rather than waiting on a push. Watch progress in Deploy History; open the log icon on any deploy to see the full build output.

4. Verify

Every project gets a platform subdomain in the form {name}-{hash}.anysites.app (the hash avoids name collisions across accounts). Once a deploy is ACTIVE, that URL serves your app.

Related documentation