DOCUMENTATION / GETTING STARTED

What you need before your first deployment.

BRIQONA Deploy is a control plane for your projects. Live deployments need a configured GitHub App and workload server outside the app.

Deployment readiness: live builds, custom routing and certificates require a separately operated, security-hardened workload server and verified GitHub configuration. These services are not reported as active until they pass live checks.

1. Create an account and project

Verify your email, open your dashboard, and configure the project name, address, branch, stack and build commands.

2. Connect GitHub

A GitHub App installation must be configured to list repositories and receive push events. No fake repository list is shown.

3. Provision a workload server

A separately operated Ubuntu VPS must run a hardened worker and reverse proxy. The BRIQONA app does not run Docker or customer code.

4. Configure domains

Point the apps wildcard DNS record to your workload server. Custom domains require ownership verification before routing or TLS.

Supported stacks in the plan

Static HTML

Serve an existing static site or build output.

Vite / React

Build static output for a CDN-style runtime.

Node.js

Run a supported Node app on a configured port.

Next.js

Use standalone output and bind to 0.0.0.0.

Plain PHP

Serve PHP behind an HTTP server.

Laravel

Use an external database; files are ephemeral.

Project limits and build settings

  • • Current plan resources are shown on the pricing page. Other service limits are not advertised until configured and verified.
  • • Project addresses must be 3–40 lowercase letters, numbers or hyphens; reserved names are blocked.
  • • Build and start commands are configuration only until a real worker is connected.
  • • Use external databases for Laravel or Node applications. Managed databases are outside MVP scope.

Environment values and application storage

Build-time secrets and runtime values are distinct. Never commit `.env` files into a repository. Laravel application storage is ephemeral in this MVP; persistent volumes and managed databases are not provided.

Secrets are never shown in project listings. Workload execution requires the separately configured worker and secure server-side secret handling.

GitHub App configuration

The GitHub App must be installed for the repository owner and grant Contents: Read and Metadata: Read permissions. Configure the setup callback and push/installation webhooks to the public endpoints in the supplied operations runbook. App ID, private key, slug, and webhook secret stay in the deployment environment's secret configuration.

Every project records its selected installation. The server checks the installation owner before listing repositories and requesting a short-lived repository token. Uninstalling the App disables automatic deployment for linked projects.

Domain setup

A custom hostname remains inactive until the displayed TXT ownership record resolves. Add the appropriate application CNAME/A record only after your workload operator provides the routing target. TLS status remains pending until the external reverse proxy and certificate service are installed and tested.

Limits and support

No capacity or uptime commitment is made until production services are configured and monitored. Contact BRIQONA support at 03003444701.

Deployments wait in queue until worker infrastructure is configured.