Getting started
From an empty account to a live website. Most people are done in under fifteen minutes, most of which is waiting for the server.
What you need
- Your website's code in a public Git repository reachable over HTTPS — for example on GitHub.
- A Node.js app (anything with a
package.json: Next.js, Express, Nuxt, a Vite build and so on) or a plain static site of HTML, CSS and JavaScript. - If you want to use your own domain, access to its DNS settings.
1. Create an account
Sign up with your name, email and a password. You can browse the dashboard straight away; creating and deploying projects needs an active plan.
2. Choose a plan
Go to Billing and choose a plan. The Dedicated plan is ₹2,000 a month for a server of your own with 1 CPU and 4 GB of memory, and as many websites on it as it will hold. Payment is handled by our payment provider at checkout; you can cancel any time from the same page.
3. Wait for your server
After payment we set up your server. The dashboard shows its progress while this happens — it usually takes about four minutes. You can create your first project in the meantime and deploy it as soon as the server is ready.
4. Create a project
On Projects, choose New project and fill in three fields:
| Field | Example | Notes |
|---|---|---|
| Project name | acme-marketing-site | For you — it appears in the dashboard and in alert emails. |
| Repository URL | https://github.com/acme/marketing-site | A plain HTTPS URL. A trailing .git is fine. |
| Branch | main | The branch that gets deployed. Defaults to main. |
5. Deploy
Open the project and press Deploy. The build output streams into the page as it runs — cloning, installing, building, starting — and ends with the address your site is live at. Deploying explains every step and what to do if one fails.
If your app needs settings such as a database URL or API keys, add them under Environment variables before you deploy. See Environment variables.
6. You're live
Every website gets its own HTTPS address as soon as it deploys, with nothing to configure. To serve it on your own domain, add the domain on the project page and point one DNS record at your server — see Domains & HTTPS.
From then on, we check every five minutes that your app is running and email you if it stops. Monitoring & logs covers what is checked and where to look when something goes wrong.
Updating your site
Push your changes to the branch, then press Deploy again. Each deploy builds the latest commit on that branch, and every deployment is kept in the project's deploy history with its full build output.
Stuck? Get in touch — include your project name and we can look at the same logs you see.