You want to build an app. First, you have to configure databases, networking, secrets, TLS, login, backups and monitoring.
BaseHarbor is a CLI that provisions, connects and verifies the infrastructure your app needs — on your own machines, using standard protocols and libraries.
Terraform describes infrastructure resources. BaseHarbor describes application needs: SQL, cache, secrets, storage, login or HTTPS.
Declare the needs, review the plan, apply it and verify the result. Provider choices live in Target bindings, keeping application intent portable.
version: 1
app:
name: my-app
environment: dev
services:
sql: true- Start or adopt an app — use existing repositories and normal ecosystem tooling.
- Only the services you need — selected capabilities plus genuine dependencies.
- Connected services — databases, cache, messaging, storage, secrets, identity and observability.
- Protected access — TLS, scoped credentials and explicit trust boundaries.
- Verified lifecycle — plan, apply, inspect, stop, recover and remove with ownership checks and concrete consequences.
- Your infrastructure — Docker and rootless Podman (Quadlet); optional Console and Node Connector.
- Standard application interfaces — database drivers, S3, OIDC and OTLP; no BaseHarbor SDK.
BaseHarbor works deterministically without AI. Use it directly, or let an agent use the same structured operations through JSON and MCP.
baha init
baha up
baha statusThe optional Console adds a web interface. The Node Connector provides protected access to remote hosts.
curl -fsSL https://raw.githubusercontent.com/mcpdev80/baseharbor/main/scripts/install.sh | bash
baha versionGetting started · Documentation · Releases
BaseHarbor is pre-v1. Published versions and installation binaries are available in the GitHub releases. Docker and Podman runtimes are implemented; Kubernetes and OpenShift runtimes are planned. See the documentation for supported paths and current limits.
Apache License 2.0. See LICENSE.