Deploy your app from Git or the CLI

A push to the app’s configured branch starts a deployment. Auto-deploy is on by default and can be turned off for each app.

1. 1Eza receives the new commit.
2. 2Railpack detects the stack and selects build and start commands. If your repository contains a Dockerfile, Eza uses the Dockerfile.
3. 3Eza builds the app and runs the health check.

• Passing

  A passing health check sends traffic to the new deploy.

• Failing

  A failing health check keeps the previous deploy live.

You can roll back to an earlier deploy in about 30 seconds.

Railpack selects build and start commands for recognised stacks. You can override these settings in the dashboard, CLI or API:

• Start command
• Root directory
• App port
• Health check path

Eza does not use an eza.yml file at launch.

For Docker builds, place a Dockerfile in your repository. For advanced Railpack build changes, use railpack.json.

The Eza CLI stores local app links in .eza/config.json. This file does not store build settings.

Run eza deploy in a local folder.

If Eza cannot find a Git remote, it offers to upload the current folder. This works like eza deploy --local.

Eza respects .gitignore and .ezaignore when it uploads files.

In CI, use eza deploy --local --yes to upload without an interactive prompt.

$ cd juma-shop$ eza link$ eza deploy --local

$ eza login            # Sign in$ eza orgs create      # Create an organisation$ eza link             # Link this folder$ eza deploy           # Deploy current code$ eza logs --follow    # Stream runtime logs$ eza logs --build     # Show build logs$ eza db tunnel        # Open a database tunnel

eza link asks you to choose or create an organisation, project, environment and app.

• If you belong to one organisation, Eza skips the organisation selection.
• The environment defaults to production.
• Eza saves these selections to .eza/config.json, so later commands work without extra flags.

Use build logs when an app fails during installation or compilation.

Use runtime logs when an app starts but returns errors after deployment.

$ eza logs --build$ eza logs --follow

A failed health check keeps the previous deploy live.

Eza injects connection details into your app environment. Managed databases include:

• PostgreSQL
• MySQLBeta
• MongoDB-compatibleBeta
• Redis-compatible

Use eza db tunnel to connect from your computer through a local TCP port.

$ eza db tunnel production-db

The same tunnel works with psql, mysql, mongosh and redis-cli.

• PostgreSQL and MongoDB-compatible databases support point-in-time recovery.
• MySQL uses binlog backups.
• Valkey uses daily snapshots and append-only files.

Environment variables are encrypted at rest with envelope encryption.

Runtime variables are injected when your app starts. They do not enter the build. Mark a variable as build-time only when the build needs it.

Secret values remain hidden in the dashboard until you reveal them. Eza records each reveal.

Eza scheduled jobs use standard five-field cron syntax. Schedules run in Africa/Nairobi time by default.

0 8 * * 1-5

This runs at 08:00 from Monday to Friday in Nairobi.

Docker Compose is Beta.

Eza supports a documented subset of Compose files. Check the supported services before you deploy.

Use a docker-compose.yml file in your repository.

PayEdge works with apps hosted on Eza Cloud or elsewhere.

Create a PayEdge configuration, copy the API key and call the STK push endpoint over HTTPS.

Amounts use whole KES. The minimum amount is KES 1.

import { PayEdge } from '@eza/payedge' const client = new PayEdge({  apiKey: process.env.PAYEDGE_API_KEY}) const result = await client.stkPush({  phone: '254712345678',  amount_kes: 1500,  account_reference: 'INV1024',  idempotency_key: 'request-1024'}) console.log(result.checkout_request_id)

PayEdge hosts the Safaricom callback URL, verifies the result and forwards it to your webhook endpoint.

• Owners and Admins must use two-factor sign-in.
• Members and Viewers can use two-factor sign-in.
• All customer data is stored and processed in Kenya.

Report a security issue to security@eza.co.ke.