Your applications. Your infrastructure.
BaseHarbor brings applications and their backends together on verified Linux Targets. Use one CLI to run native workloads, connect secure provider bindings and inspect the result.
Documentation for BaseHarbor v0.4.26. Published versions and installation binaries are available in the GitHub releases.
From repository to running application
Install the CLI and a rootless Docker or Podman runtime, then open your application's repository:
baha init
baha up
baha status
baha init adopts the repository and records its system-generated application identity. baha up provisions or reuses the requested providers and their genuine dependencies. A supported local application with no requested managed services needs no unrelated service containers or compulsory login. An explicitly enabled management Core or Console has its own security dependencies. Status distinguishes verified readiness from a workload that is merely running.
Build with your normal tools
Keep your application code and libraries. BaseHarbor detects supported Compose, Quadlet and Kubernetes workload sources, resolves provider-neutral requirements and supplies protected bindings. Ambiguous or unsupported sources require an explicit next action before deployment.
Run with shared or isolated providers
Choose supported provider placement and a managed local or enrolled remote Target. Ownership, TLS, permissions and retained data remain explicit throughout the lifecycle. Core resource observations distinguish measured reference topologies from planning estimates and the cost of additional isolation.
Control and verify
Inspect a plan before mutation, diagnose failures with Doctor, and review backups before recovery. CLI, JSON and MCP use the same domain operations. EN and DE documentation have equivalent page and command coverage; shipped technical identifiers and verified CLI output stay identical.
Choose your next task
| Task | Start here |
|---|---|
| Create, adopt or operate an application | Applications |
| Select a local or remote deployment destination | Targets |
| Connect managed or external backends | Providers |
| Manage identity, TLS and trust | Security |
| Automate through JSON and MCP | Automation and agents |
| Find exact shipped commands and contracts | Command index · Reference |
Delivered changes and support boundaries are recorded in the release notes.