More time for the thing you’re building. Explore Cloud beta
HakopodHakopod
Create account
More time for your product.

Start small.
Scale what you build.

Deploy from Git. Connect private services. Give each workload the resources it needs, all from one dashboard. Bring your idea to Hakopod Cloud or run the open-source platform on your own servers.

View on GitHub Open source. Yours to build on.
CLOUD BETA / SIGNUP OPEN

Your next app starts here.

Create your Cloud account, choose available compute, and bring your code. The dashboard guides you through setup and deployment review.

Prefer to self-host? Use your own server.
curl -fsSL https://hakopod.com/scripts/installer.sh | sudo sh

On a fresh Linux server. Install guide

Read the self-hosted install guide Free core · Your infrastructure · No license required
Image

Your apps.
Your terms.

From your next idea
to a place it can run.

Your apps. Your terms.

01:08 · English captions included Read transcript
Bring your codeScale each serviceKeep controlFree core. Room to grow.

You have more
important things
to build.

WHAT’S HAKOPOD

The feature your users keep asking for. The idea you finally have time to try. Hakopod brings deployment, service connections and everyday operations together so running your app takes less of your attention.

Explore the platform
From your first deploy to your next busy day.SEE THE PATH
SMALL BEGINNINGS WELCOME

A clear path to
your first deploy.

You bring the code. Hakopod brings the setup, deployment and day-to-day controls into one place.

  1. 01 / BRING YOUR APP

    Start with what you have.

    Connect a Git repository, bring a container image or choose a deployable template.

    Browse templates
  2. 02 / MAKE IT YOURS

    A guided setup.

    Choose resources, add variables and secrets, and decide which services need a public address. Git builds have their own setup and review.

    See the setup steps
  3. 03 / PUT IT TO WORK

    Review. Click Deploy.

    With your image and configuration ready, review the plan and deploy. Follow the rollout, then inspect readiness and logs.

    Follow a deployment
WHEN YOUR APP GETS BUSIER

Scale the part
that needs it.

A busy API, a growing queue, another service. Give each workload room to grow from the same dashboard.

Explore resource settings

More room for a service

Adjust CPU and memory for the workload that needs them.

More copies for the load

Set replicas for supported stateless services, or configure CPU-based autoscaling within your limits.

More services for your idea

Add a worker or private API. Keep its settings and connections alongside the rest of your app.

Which workloads can scale?

Scaling needs available compute and workspace capacity. Hosted Free allows one small service and one replica; larger workloads need eligible BYO compute or self-hosting. Persistent-volume services use one replica. Managed databases have their own replication and capacity requirements.

ALL THE PARTS OF YOUR APPLICATION

Your app.
Its services.
Working together.

A public frontend. A private API. A place for data.
Keep the whole application in view.

YOUR CODE Git repository YOUR FRONTEND Web application YOUR DATA Database YOUR BACKEND Private API YOUR OPERATIONS Logs & resources YOUR INFRASTRUCTURE Linux server
Concept illustration · Explore each part
PostgreSQL + Redis / Development release

Restore a copy.
Check it before you switch.

PostgreSQL and Redis operations beside your apps. Recover into a separate database, inspect the data, then explicitly change your app’s connection. Your source stays available.

Explore databases in Cloud Available in eligible hosted Cloud workspaces. Compute and storage limits apply.
A recovery workflow you control.
  1. 01Restore.A separate copy.
  2. 02Inspect.Your chance to check.
  3. 03Switch.Only when you decide.

Source data stays available. New writes need a fresh capture before cutover.

THE IDEA BEHIND HAKOPOD

Your ambition can grow.
Your setup can stay understandable.

Start with what your app needs today. Add services and capacity when the work calls for it. Keep the same place to deploy, inspect and understand the whole application.

AFTER YOUR FIRST DEPLOY
01 / SOURCE

Ship the next change.

A repository, container image, or TOML file. Review what will change before applying it, then follow the deployment through to its result.

Follow a deployment ↗ GitHub · GitLab · Container registries
FIG. 02 / SOURCE · CONCEPT ILLUSTRATION
02 / CONNECT

Connect your services privately.

Expose the frontend over HTTPS. Keep databases and workers private. Use named networks and explicit peers to connect the parts that belong together.

Draw your boundaries ↗ Private ports · Network membership · Allowed peers
FIG. 03 / CONNECT · CONCEPT ILLUSTRATION
03 / INSPECT

Find the problem. Keep moving.

Move from an application to its services, pods, and logs. Resource probes and alarm delivery help you investigate the parts that need attention.

Inspect a service ↗ Pods · Resource usage · Logs · Alarms
FIG. 04 / INSPECT · CONCEPT ILLUSTRATION
04 / RECOVER

Make recovery part of the plan.

Keep configuration revisions and data recovery separate. Set an object-storage destination, review backup schedules, and rehearse a restore.

Plan your recovery ↗ Object storage · Backup schedules · Reviewed restores
FIG. 05 / RECOVER · CONCEPT ILLUSTRATION

Know what’s running.
Find what needs you.

INSIDE HAKOPOD / ACTUAL DASHBOARD / LOCAL DEMO

Move from a service to its logs, resources and deployment history. These actual dashboard captures come from our local demo.

Scroll to explore, or choose a view. Use arrow keys then Enter on the tabs.

Services

Actual Hakopod dashboard: The shop application with its web and API services. Local demo workloads, revision 18.

The shop application with its web and API services. Local demo workloads, revision 18.

LOCAL DEMO · 13 SEP 2026View full image↗

Inspect

Actual Hakopod dashboard: An actual service probe, current pod, and historical failed pod. Sample readings describe this local demo only.

An actual service probe, current pod, and historical failed pod. Sample readings describe this local demo only.

LOCAL DEMO · 13 SEP 2026View full image↗

Configure

Actual Hakopod dashboard: Applied TOML for the shop application. Configuration remains reviewable alongside its deployment history.

Applied TOML for the shop application. Configuration remains reviewable alongside its deployment history.

LOCAL DEMO · 13 SEP 2026View full image↗

Deploy

Actual Hakopod dashboard: A recorded shop deployment from 12 September. Historical rollout details are separate from current service health.

A recorded shop deployment from 12 September. Historical rollout details are separate from current service health.

LOCAL DEMO · 13 SEP 2026View full image↗
A PLATFORM THAT LEAVES YOU IN CONTROL

The infrastructure
is still yours.

Use Cloud to manage connected compute, or operate Hakopod yourself. Keep your configuration in Git and choose which services are public. A simpler workflow should still leave the choices yours.

Explore self-hosted
Git

Your source of change

TOML

Your configuration, reviewable

Linux

Your choice of infrastructure

Yours.

Your applications and data

GOOD COMPANY FOR YOUR APPLICATION

Bring the tools
you already like.

Start with a database or a tool you know. Review the secrets, storage, and requirements before deployment.

Image PostgreSQL Image Redis Image MySQL Image Metabase Image Open WebUI Image Gitea
Explore the shared template catalog
A HOME THAT FITS YOUR WORK

One platform.
Your way to run it.

AVAILABLE TO SELF-HOST

Your infrastructure.
Your call.

Run Hakopod on your own Linux machines. Keep control of nodes, networking, and the services you expose. Basic teams, invitations, and fixed roles are Free.

Explore self-hosted
CLOUD BETA / SIGNUP OPEN

Your next app.
A Cloud workspace.

Keep your projects, deployments and private services in a hosted dashboard. Start with an account and choose from the compute options available to your workspace. Paid checkout is not open yet.

See how Cloud works

Notes from the workbench.

VIEW ALL
Product / 3 min read

Start small. Keep your options.

The idea behind Hakopod: make the first deployment approachable, and let the next decision wait until your application needs it.

Read the story↗
Operations / 3 min read

A request is a good place to start

When an HTTP endpoint fails, start with the request that reached it. A practical tour of Requests and routing in Hakopod.

Read the story↗
Engineering / 3 min read

Let a quiet HTTP service sleep

Scale-to-zero is useful when the waiting is acceptable. Here is how to decide which services should sleep.

Read the story↗
BEFORE YOU GET COMFORTABLE

A few good
questions.

Read the docs ↗
What is Hakopod?

An application platform for deploying and running web apps, APIs, workers and their services. Use the hosted Cloud dashboard or install the open-source platform on your own servers.

Do I need to know Kubernetes?

Application owners can work with the dashboard and TOML. The installation operator still owns the cluster, storage, upgrades, and recovery. The docs explain those responsibilities before installation.

Can I run databases and workers?

Yes. Services can stay private, run without public HTTP, use persistent volumes, and receive their own variables and secret bindings. Images must support Hakopod’s non-root runtime. Back up persistent data separately from configuration.

Is everything in the open-source edition?

The deployment engine, teams, invitations and fixed roles are Free. Pro adds actor audit history. Custom roles and organization MFA enforcement remain planned.

Can I use Hakopod Cloud today?

Cloud is in development and account signup is open. BYOD launch prices start at $5/month, with Team at $15/month. Paid checkout is not open yet. Explore Cloud for onboarding and compute options.