Projects

A project is the top-level resource in deploybase. It represents a single static site with its source code, build settings, and deployment history.

Project Structure

Field	Description
name	Display name (e.g. My Blog)
slug	URL-safe identifier, used in production URL. Unique per tenant.
framework	Build framework: nextjs, sveltekit, astro, hugo, vite, gatsby, jekyll, or other
git_repo_url	HTTPS clone URL for the source repository
git_provider	github, gitlab, bitbucket, or codeberg
default_branch	Branch that auto-promotes to production (default: main)
build_command	Custom build command (overrides framework default)
output_dir	Custom output directory (overrides framework default)
live_deployment_id	The deployment currently serving production traffic
subdomain	Production subdomain: {subdomain}.sites.deploybase.eu

Framework Detection

When framework is set, deploybase applies default build settings for that framework (build command, output directory, Docker image). See Supported Frameworks for the full defaults table.

If framework is not set or set to other, generic Node.js defaults apply: npm install && npm run build with output to dist/.

Custom build_command and output_dir override framework defaults when set.

Production URL

Every project gets a production URL at:

https://{subdomain}.sites.deploybase.eu

The subdomain defaults to the project slug. It can be changed via update_project, subject to availability (check with the subdomain availability endpoint first).

Custom domains can be added for any project — see Custom Domains.

Multi-Tenancy

Projects belong to a tenant (organization). All project operations are scoped to the authenticated user’s tenant. A project created by one tenant is not visible to any other tenant.

Limits

Project count limits depend on the subscription plan. See pricing for current limits per tier.

Related Concepts

• Deployments — immutable build snapshots within a project
• Preview Deployments — automatic per-branch URLs
• Custom Domains — serve from your own domain