DocumentationSELF-HOSTED / DEVELOPMENT RELEASEView source ↗
Start here

Meet Hakopod

Deploy applications on infrastructure you own, with one place to see what is running.

Hakopod is a self-hosted application platform built on K3s and HAProxy. It gives you a dashboard, a small CLI and one deployment API for applications made of one or several services.

You describe what an application needs, review the proposed change, and deploy it. Hakopod resolves image tags to digests, records a revision and waits for the workload to become ready. You can inspect the pods, read recent logs and return to an earlier successful configuration.

How things fit together#

Concept What it contains
Installation Your management server, cluster and installation settings.
Project A home for related applications and access permissions.
Environment A separate scope such as development, staging or production.
Application A versioned configuration containing one or more services.
Service A container workload with an image, resources, ports and optional storage.

The dashboard opens on Projects. Choose a project and environment to see its applications. An application's services share a private network by default; public HTTP exposure is an explicit setting.

Choose your starting point#

  • A fresh server: follow Installation, then claim the first administrator account in your browser.
  • An existing installation: follow Your first application to deploy an image, import TOML or use the catalog.
  • A repository: connect GitHub or GitLab to import a TOML file or build an image with a Dockerfile or buildpack. Start with Deployments.

The first setup queues a labelled, removable shop sample. It demonstrates a public web service talking to a private service. It contains sample data and is not a payment application.

A small control plane#

The Go API and reconciler run together, with PostgreSQL holding accepted work and history. The dashboard and CLI use the same API. Source builds run on configured GitHub or GitLab runners. Live log inspection does not require an always-running logging stack, and opening an AI template does not load a model.

Optional workloads still need real capacity. A database needs storage; a model server needs enough supported GPU memory. Review configuration and each catalog template's prerequisites before deploying.

Free, licensed and Cloud#

Self-hosted Free includes deployments, rollback, observability, secrets, registries and operational controls. Shared teams, invitations and project role grants require signed Pro entitlements. A license does not change the installation's networking policy.

Hakopod Cloud is a planned service, focused on Git deployments, HTTP/HTTPS, custom domains and private service networking. Public SMTP, SFTP and other custom TCP protocols belong on self-hosted installations with administrator-provisioned ports.

This is a development release. Container checks and local cluster tests do not replace full host installation, recovery and public TLS acceptance on your infrastructure.