Push to GitHub. Your app is live in London.

1. 01

   Order an App Server

   Choose S, M or L and pay by card. Nothing is set up before payment, and a person checks every first order during support hours. Once your order is approved, we set up your App Server by hand. It is ready within 1 working day of approval, and you can follow its status in your panel.

2. 02

   Connect GitHub

   Install the WharfCloud Deploy app on your GitHub account or organisation and choose which repositories it may see. You can pick only the ones you want to deploy.

3. 03

   Import a project

   Pick a repository. We detect common frameworks and suggest the build and start commands; you can change them, set the root folder and add environment variables before the first deploy.

4. 04

   Push to deploy

   Each push to your production branch builds and deploys a new version, usually in minutes. Your app gets a URL such as shop.northwind.apps.wharfcloud.co.uk, with HTTPS from the start.

5. 05

   Review, then merge

   Each pull request gets a preview at its own address, for example pr-12-shop.northwind.apps.wharfcloud.co.uk, and the result shows on the pull request in GitHub.

• Deploy on every push. Builds start from your production branch automatically. You can also redeploy, cancel a build or turn automatic deploys off.
• Pull request previews. Pull requests from branches in the same repository get a live preview. Pull requests from forks wait until you approve them, because they run someone else's code on your server. Previews stop after 7 days without a push and are removed when the pull request closes.
• One-click rollback. The last 5 builds of each project are kept on your App Server, so going back to one of them is instant. Older versions are rebuilt from their commit.
• Custom domains with HTTPS. Add your own domain, prove you own it with a DNS record, point it at your App Server and the certificate is issued and renewed for you. We check custom domains every day. If a domain's ownership record or its address record stops checking out for 7 days in a row, we detach it, so a stale record cannot keep serving your app. You can add it again at any time.
• Environment variables you cannot leak by accident. Values are encrypted in the panel so that only your App Server can read them, and they are never shown again after you save them. You can replace them at any time.
• Build and runtime logs. Watch the build as it runs and read your app's recent output in the panel. Logs are kept for 30 days.
• Usage at a glance. Processor, memory and disk use for your App Server, and how many of its preview slots are in use.

Every plan is a whole App Server for your projects, not a share of one. The processor, memory and disk below are what your apps can use; the server is sized larger so our own build and routing software does not eat into them.

App Server S suits a few small apps, sites and APIs. App Server M suits production apps and busier sites. App Server L suits several production apps or heavier builds. The lower price is our intro price for the first 50 customers. To change size, ask us through a support ticket; you cannot change plan in the panel yet. The App Server restarts briefly when it is resized.

Web apps, sites and APIs that run in a container: Next.js, Vite, Astro, Nuxt, SvelteKit, Remix, Express and other Node.js apps, and static sites. If your repository has a Dockerfile, you can build with that instead, which also covers other languages.

• Each project runs as one container behind our HTTPS proxy. Docker Compose files are not supported yet.
• Your App Server has no SSH access for customers: you change it through GitHub and the panel.

You decide which repositories the app can see when you install it, and you can change that on GitHub at any time. These are the permissions it asks for:

Your App Server gets a short-lived read-only key for one repository at a time, only while it builds. It never holds our GitHub app's own key or our DNS and database credentials.

We would rather you know now than find out after you have paid.

• Managed databases. There is no database service in WharfCloud Deploy yet. Connect to a database you already use and keep its connection string as an environment variable.
• Support for your own code. We support the platform: builds, deploys, previews, domains, certificates and the App Server itself. Debugging or changing your application is yours. If a build fails because of your code, the logs show why.
• A global network. Your apps run in London only. There is no worldwide edge network and no serverless scale to zero; your App Server is always on.
• Other Git hosts. GitHub only for now, not GitLab or Bitbucket.
• Teams. One account owns each App Server for now.
• Sending email straight from your App Server. Outbound port 25 is blocked. Send through an email provider instead, using its API or authenticated SMTP on port 465, 587 or 2525. Our acceptable use policy explains why.

Need a database looked after, Windows, or a server you can sign in to? A Managed Linux Server may suit you better, or ask us.

• Engineers on tickets: Monday to Friday, 08:00 to 18:00 UK time.
• Critical incidents on the platform: Every day, 07:00 to 23:00 UK time. A person responds to critical incidents within 1 hour.
• Nights and weekends: Automated monitoring and automated recovery overnight and at weekends.
• Security updates: we install critical and high-risk updates to the App Server's operating system and our platform software within 14 days, as set out in section 12 of our terms.

We review abuse reports and act on them, because everyone's apps share our name. If you see a site on one of our addresses that should not be there, report it.