Your first deployment
Create a service from a Git repository, configure its build and check the application. You can start with free resources; their limitations are documented separately.
Video: your first application on Lixev
Sign in, create a workspace, deploy Nginx on FREE, open its public address and inspect logs. English interface and captions, without narration. The tutorial project was removed after recording.
Download tutorial ↓Video: deploy a GitHub project
Deploy DezerdGun/render3 as two services: a FastAPI backend and a Nuxt frontend. Configure root directories, health checks, the API URL and CORS, then add a sample expense. English captions, without narration; the example application has an Uzbek interface. This is a temporary SQLite demo, removed after recording.
Download the English tutorial ↓Create an account
Sign up and select a workspace. The free plan provides limited resources, not a cash bonus.
Sign up →Choose a Git repository
Open service creation and choose the GitHub source. Enter the repository URL and branch. For a private repository, connect an account with access; do not put a token in a public URL.
Create a service →Service types
Web service
A server application accepting HTTP requests: websites and APIs.
Static site
Built HTML, CSS and JavaScript served from a publish directory.
Private service
An internal service without a public URL.
Background worker
A long-running process for queues and background tasks.
Cron job
Scheduled execution using a cron expression.
FREE web services sleep after 15 minutes without inbound requests. The first request after sleep may wait for startup. See free resources for all quotas and database conditions.
Free resources →Configure and deploy
Before deploying, check the root directory, commands, resources and environment variables. Empty commands use platform auto-detection. Your own Dockerfile takes precedence over a generated one.
| Field | Description |
|---|---|
| Name | Service name: use a descriptive name and characters allowed by the form. |
| Branch | Repository branch, for example main. |
| Root Directory | Application subdirectory in a monorepo. Commands run relative to this directory. |
| Build command | Build command, for example npm run build. Dependency installation depends on the selected build method. |
| Start command | Server start command. The application must listen on 0.0.0.0 at the configured port. |
| Publish Directory | For static sites: the built output directory, for example dist. |
| Compute | CPU and RAM allocation. Check cost and plan limits before deploying. |
| Environment Variables | Configuration values and secrets. Do not publish them in Git. |
| Auto-Deploy | Review automatic deployment settings for changes to the selected branch. |
After reviewing the form, select Deploy to create the service and start its first build.
Check the result
Review build and runtime logs on the deployment page. The release must pass its health check. If it fails, check the start command, port, environment variables and application logs.
Open your application
Open the service’s public URL. Test the homepage, nested URLs and API or database connections. Background workers and private services may not have a public URL.
Next steps
Choose a service
Need a recurring scheduled job?
Cron job →Does the process run in the background without accepting HTTP?
Background worker →Should access be internal to the project?
Private service →Does the site consist of built HTML, CSS and JavaScript?
Static site →Does the application accept public HTTP requests?
Web service →
Custom domain
Add your domain in service settings and copy the supplied DNS record to your DNS provider. Wait for DNS verification and HTTPS certificate issuance. Timing depends on DNS propagation and certificate issuance; immediate availability is not guaranteed.
Manage your service
The service panel provides logs, settings and runtime actions. Before stopping a service, changing resources or rolling back, check its current state, plan conditions and feature limitations. Capability status is documented separately.
Capabilities and limitations →