[ / ]
Your infrastructure.
Your call.
Run Hakopod on your own Linux machines. Keep control of nodes, networking, and the services you expose.
Explore self-hosted OPEN SOURCE. OPEN POSSIBILITIES.Your apps.
Your apps.
Your rules.
A little less infrastructure.
A lot more building.
Give your applications a home on servers you own. Deploy from Git, connect your services, and see what’s happening. All in one place.
Linux · ARM64 + AMD64 · Built on Kubernetes A PLACE FOR EVERY SERVICEFIG. 01 / THE PLATFORM
Out in the worldWeb / HTTPS
Keep it between servicesPrivate by configuration
01 / A LITTLE MORE ROOM TO BUILDLESS GLUE. MORE GOOD IDEAS.
You built the app.
Give it a place to grow.
From the first service to the pieces around it.
One clear view of
your applications, without losing control of what runs underneath.
01
Ship with context.
Review the plan. Follow the rollout. Return to a previous configuration when you need to.
Deployments & rollbacks ↗02Connect deliberately.
Public frontends. Private backends. Shared networks with explicit membership and allowed peers.
Networks & boundaries ↗03See the whole story.
Go from an application to its services, pods, logs, and resource usage. Keep failures in view.
Monitoring & alarms ↗ 02 / YOUR NEXT DEPLOYMENTFROM REPOSITORY TO RUNNING
A familiar start.
A better everyday.
Use the dashboard when you want a clear view.
Keep TOML in Git when
you want repeatable changes.
It’s the same application underneath.
YOUR WORKFLOW, CONNECTED
Start where your code lives.
Connect GitHub or GitLab. Choose a build preset or bring a container image. Keep the deployment definition beside your code.
Connect a sourceCONCEPT DIAGRAM / NOT A LIVE DASHBOARD
your-repositorymain / hakopod.toml
Build presetDockerfileOCI image
Review deployment plan
03 / ALL THE PIECES, TOGETHERYOUR OWN LITTLE CORNER OF THE CLOUD
Small details.
Real control.
Make room for the things that turn a deployment into an application you can actually operate.
Explore the platform 01 ↗02 ↗03 ↗04 ↗
Variables and secrets
Service-level configuration. Explicit secret bindings.
Backups with a destination
Object storage, schedules, and reviewed restore operations.
Access with boundaries
Accounts, scoped credentials, and licensed team permissions.
Problems worth your attention
Deployment failures, unhealthy services, and alarm delivery.
04 / CHOOSE YOUR HOMECONTROL THAT FITS YOUR TEAM
Your server today.
More ways to run tomorrow.
Start with the open-source platform.
Choose the operating model
that suits your work.
Your infrastructure.
{ + }
Just bring
the application.
Hakopod Cloud is being designed for small apps: Git deployments, HTTPS, private services, and predictable limits.
Meet Hakopod CloudWhat is Hakopod?
A self-hosted application platform on Kubernetes. It brings application configuration, deployments, private networking, and operations into a shared dashboard, CLI, and API.
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 is open source. Team creation and other Pro capabilities require signed license entitlements. Self-hosting does not require using Hakopod Cloud.
Can I use Hakopod Cloud today?
Cloud is in development. There is no hosted signup or published Cloud pricing yet. You can explore the product direction here or start with self-hosting.