See the details.
Projects, applications, deployments, and infrastructure in an interface made for everyday operations.
All the moving parts.
One place to make sense.
Your applications are more than a deploy button. Keep their configuration, connections, and everyday operations close together.
Make room for your apps ONE COHERENT APPLICATION
From a single service
From a single service
to a connected system.
Start with a web app. Add a private API, a worker, and a database. Each service gets its own configuration, while the application keeps the whole deployment in view.
Deploy your first application↗ ORIGINAL CONCEPT ILLUSTRATION
01 / A CONNECTED WORKFLOWGIT. CONFIGURATION. SERVICES.
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
02 / EVERYTHING HAS ITS PLACEEXPLORE THE DETAILS
01 / Deployments
Know what changed.
Immutable application revisions, planned changes, and deployment history keep the next step in context. Roll back a successful configuration without pretending to roll back data.
Read the guide↗ 02 / NetworkingA boundary around your work.
Named service networks, private ports, and scoped virtual networks connect the right services. Explicit grants keep cross-application communication deliberate.
Read the guide↗ 03 / ConfigurationOne file, many ways to work.
Edit TOML in the dashboard or keep it in a repository. Service variables, secret references, resources, and storage use the same canonical configuration.
Read the guide↗ 04 / OperationsFollow the problem to its source.
Inspect services and pods, filter logs, view resource usage, and review alarm events. Diagnose the current workload, not only the last deployment result.
Read the guide↗ 05 / StorageCare for the stateful parts.
Persistent mounts and filesystem permissions give your data a home. Configure object storage for supported backup and restore workflows.
Read the guide↗ 06 / AccessThe right tools, in the right hands.
Start with an installation administrator. Use scoped API credentials and explicit permissions; licensed team features bring members and roles together.
Read the guide↗Use the view
that fits the work.
The dashboard, CLI, and REST API share the same application model. No secret second configuration to keep in sync.
Keep your flow.
Plan and deploy from your terminal. Use scoped credentials for automation and CI.
Make it repeatable.
Keep service definitions in version control and review configuration changes with your team.