Quickstart
This guide walks you through deploying a real application on Runsite Platform — start to live URL in a few minutes.
1. Create an account
Section titled “1. Create an account”Sign up at the Runsite dashboard with email and password, or with Google. A workspace is created for you automatically.
2. Create a project
Section titled “2. Create a project”A project is a container for related services that share environment variables, secrets and team access. From the dashboard, click New project and give it a name.
3. Deploy a service
Section titled “3. Deploy a service”Choose what you want to deploy:
Deploy a web service from Git
Section titled “Deploy a web service from Git”-
In your project, click New service → Web Service.
-
Connect your GitHub, GitLab or Bitbucket account.
-
Pick a repository and branch.
-
Set the build and start commands. For most stacks, sensible defaults are detected automatically:
Stack Build command Start command Node.js npm install && npm run buildnpm startPython pip install -r requirements.txtgunicorn app:appDocker (uses your Dockerfile)(uses your CMD) -
Click Deploy. Runsite clones the repo, builds the image, and starts the service. You can watch the build log stream live.
-
Once the build finishes, your service is live at
https://<your-service>.runsite.app.
Deploy a static site from Git
Section titled “Deploy a static site from Git”- In your project, click New service → Static Site.
- Connect your repository.
- Set the build command (e.g.
npm run build) and the publish directory (e.g.dist). - Click Deploy. Your site is live at
https://<your-site>.runsite.site.
If the desired subdomain is taken, Runsite will append a short numeric suffix automatically (my-app-2.runsite.app). A handful of subdomains like docs, api and app are reserved by the platform.
Provision a database
Section titled “Provision a database”- In your project, click New service → PostgreSQL or Redis.
- Pick a version. The instance is provisioned in seconds.
- Copy the internal connection URL for use from other Runsite services in the same project, or the external connection URL to connect from anywhere over TLS.
4. Add environment variables
Section titled “4. Add environment variables”Open your service settings and add any environment variables you need. They are encrypted at rest and injected at runtime — restart the service to apply changes.
5. Add a custom domain (optional)
Section titled “5. Add a custom domain (optional)”Open your service settings and click Custom domain → Add. Follow the DNS instructions to point your domain at Runsite. TLS certificates are issued and renewed automatically. See Custom Domains for the full guide.
What’s next
Section titled “What’s next”- Browse the services reference to learn each capability in depth.
- Set up API keys for CI/CD.
- Use the CLI to manage projects from your terminal.