Skip to main content
You don’t have to build yourself: connect your GitLab repository and Havic pulls the code, builds it in an isolated sandbox, and serves the result — on every new revision.

​
How it works

1

Connect the repository

Connect your GitLab repository to the website. Convenient if you already sign in with GitLab.
2

Havic detects the framework

During the build, Havic matches your source against framework signatures („Gleicht Framework-Signaturen ab …”) and suggests the right configuration.
3

Sandbox build

The build runs isolated in a sandbox. You can keep working in the meantime.
4

Publish

After a successful build and health check, the site goes live.

​
Framework detection & runtime backends

Havic automatically detects whether your project is a static site or needs a runtime backend (i.e. must run as a process). For backends, Havic suggests a runtime and shows a hint. Detected runtimes include:

Ruby on Rails

Python

.NET

For a runtime backend you configure:
Field (DE)EnglishMeaning
Start-BefehlStart commandHow the process is started.
PortPortWhich port the app listens on.
Readiness-PfadReadiness pathPath Havic checks for readiness.
Release-BefehlRelease commandOptional, e.g. a database migration before start.
ReplikateReplicasNumber of parallel instances.
Database included: Havic automatically provisions a MariaDB and sets DATABASE_URL. To use your own external database, just add DATABASE_URL as a secret.
Add secrets like SECRET_KEY_BASE, RAILS_MASTER_KEY, or API keys as additional secrets (KEY=VALUE per line). They’re injected securely at runtime and never baked into the image.