CI/CD

Deliver a generated project runtime to your own target or trigger external deploy hooks after publishing.

CI/CD

CI/CD connects a published Spala project backend to your deployment target. It delivers your generated project runtime, not the Spala dashboard, builder, or platform source code. Use it when you want the generated backend to run on your own server or when Spala should trigger an external provider deploy hook after publish.

Generated Runtime Artifact

The generated project runtime is the backend artifact for one Spala project. It represents the published project API behavior: route handlers, function logic, runtime configuration, docs metadata, and the environment-variable contract needed by that project. It is not the Spala dashboard, visual builder, platform auth system, or Spala source repository.

Hosted Publish is the normal path for most users. CI/CD is the advanced path when your team wants the generated project runtime delivered to your own infrastructure or deploy provider. Feature availability depends on the generated runtime package and the target environment you configure, so test the target with dry run before treating it as production.

Delivery Boundary

| Action | What changes | Where it runs |
| --- | --- | --- |
| Publish backend API | Hosted project API behavior becomes live | Spala-managed project API |
| Publish frontend app | Static UI assets become live | Spala frontend hosting for the project |
| Deploy generated runtime | Generated project runtime is delivered outside the default hosted publish path | Your server or external deploy provider |

Supported Target Types

- SSH server
- SFTP server with SSH commands
- Vercel deploy hook
- Render deploy hook
- Netlify deploy hook
- Railway deploy hook
- Custom webhook

Recommended Workflow

Publish the backend

First publish the project so the generated backend state is ready.

Add a deployment target

Open Settings > CI/CD, choose a provider, and enter the target credentials or deploy hook URL.

Run a dry run

Use dry run to check the bundle and target configuration before deploying.

Deploy

Deploy manually, or enable auto-deploy after publish when the target is stable.

Project deployment only

CI/CD is for deploying your generated project backend or triggering your own infrastructure. It is not a guide for running the Spala dashboard or platform.

Why Users Care

Some teams want Spala to build and validate the backend while their production runtime remains in their own cloud or deployment workflow. CI/CD keeps that path explicit and repeatable.

Publish
/features/publish-export
Publish project changes before deployment
Project Snapshots
/features/project-snapshots
Create checkpoints before large deploys
Environment Variables
/settings
Store deploy and runtime values safely