Deploying Services

This guide walks you through deploying a service to Forte Platforms from start to finish. You can use either the web console or the CLI — choose the tab that matches your workflow.

Prerequisites

• A Forte Platforms account
• A GitHub repository with your code
• The Forte GitHub App installed on your repository

Step 1: Create a Project

Projects group related services together. You'll need at least one project before creating a service.

Step 2: Create a Service

A service connects a GitHub repository to Forte's deployment pipeline. Each push to the configured branch triggers an automatic deployment.

Step 3: Monitor Your Deployment

Once created, Forte automatically starts the first build and deployment. You can follow along in real time.

What Happens Behind the Scenes

When you create a service, Forte runs a multi-stage pipeline:

1. Containerization — If your repository already includes a Dockerfile, Forte uses it as-is. If not, Forte auto-detects your language and framework and generates a Dockerfile for you — no configuration needed.
2. Image Build — Your code is built into a container image by Forte. Any environment variables and secrets configured on the service are available during the build as Docker build arguments, so dependencies that require authentication tokens (e.g., private npm registries, private PyPI indexes) will work automatically.
3. Health Check Discovery — Your application must expose an HTTP GET route that returns a success status (e.g. /health, /status, or /). Forte automatically detects the port your application listens on and discovers the health check path. This is required for your deployment to succeed.
4. Deployment — The image is deployed to Forte's infrastructure with auto-scaling based on your selected tier.
5. DNS & TLS — A public HTTPS endpoint is provisioned for your service.
6. DDoS Protection — Your service is automatically protected against distributed denial-of-service attacks. Traffic is monitored and malicious requests are mitigated before they reach your application.

Each step is logged and visible on the service's deployment detail page.

GitHub Deployment Status

Forte automatically reports deployment status back to your GitHub repository using GitHub Deployments. No configuration is required — this works out of the box for any service connected to a GitHub repository.

For each deployment, Forte:

• Creates a GitHub Deployment linked to the commit (or branch HEAD for manual triggers).
• Posts status updates as the pipeline progresses: in_progress when the build starts, and success or failure when it completes.
• Links back to the Forte Console — each status includes a link to the deployment detail page with full build logs.

The deployment environment name in GitHub is set to your service name, so you can track deployment history per service directly in your repository's Environments tab.