Roadmap
Last updated: 2026-09-12
This is Loha's public product roadmap. It separates capabilities available in released software from work that is under development or planned. Services release independently; see the Changelog for released highlights.
Release status
“In progress” means implementation, validation, or rollout work remains. It does not mean that a feature is generally available. A feature appears in the Changelog only after its released package is tagged.
Available today
| Area | Status | What you can do |
|---|---|---|
| Workspaces and access | Available | Create workspaces, manage members and roles, and use personal access tokens or service accounts for automation. |
| Repository connections | Available | Connect GitLab, GitHub, Gitea, or Forgejo repositories, configure triggers, and receive commit status updates. |
| Pipelines and builds | Available | Define pipelines in .loha.yml, run builds, inspect step status and logs, and cancel or retry builds. |
| Pipeline authoring | Available | Start from the visual builder or import supported CI configuration, then keep the generated .loha.yml in your repository. |
| Task catalog | Available | Browse documented official tasks and use them in pipeline configuration. |
| Build recovery | Available | See clearer waiting and freshness information while Loha reconciles build state; retrying an already-active build returns the existing run. |
| Releases | Available | Browse recorded image releases from repository, project, or workspace views, including the build and commit that produced them. |
| Programmatic access | Available | Use the versioned /api/v1 API and the hosted MCP server where it is enabled for your workspace. |
| CLI | Token-based access | The CLI has documented installation and self-update tooling. loha login currently uses a personal access token or service-account key. |
| Notifications and outbound webhooks | Available | Receive in-app and email build notifications. Outbound webhooks are enabled only for workspaces where the capability has been made available. |
| Quotas and secrets | Available | Apply plan limits and store repository- or workspace-scoped secrets for builds. |
In progress
- First-build onboarding. Released guidance can detect a missing
.loha.ymland offer starter configuration. We are continuing to improve the path from connecting a repository to a dependable first build. - Loha Deploy pilots. The rollout foundation supports GitOps/ArgoCD and SSH execution paths in the codebase. Real pilot environments, provider validation, and release rollout gates are still required before it can be presented as a production deployment service.
- Build security and artifacts. Artifact storage, retention, scan evidence, and security-report interfaces are under active development. They are not a released security dashboard or an enforcement promise yet.
- CLI browser login. The CLI has documented installer and self-update tooling;
loha loginstill requires a personal access token or service-account key. Browser-based sign-in remains to be released. - Loha Repos. A future managed Git offering is being designed around Forgejo. It is not yet a hosted-repository product.
- Workspace activation and self-service experience. We are refining activation, quotas, and onboarding before expanding self-service access.
Planned
- Deployment promotion and recovery. Ordered environments, health checks, promotion, rollback, and production approvals after the deployment pilots prove the execution paths.
- Enterprise identity. Per-workspace SSO/SAML.
- Reliability readiness. High availability, backup and restore exercises, load testing, a public status surface, and service commitments before broader general availability.
- Compliance and visibility. A workspace audit-log viewer and customer-facing security reporting, followed by longer-term compliance work such as an ISO 27001 track.
- Additional repository and deployment options. GitHub App organisation installs, Bitbucket support, additional deployment providers, preview environments, and progressive delivery strategies.
Known gaps
- Loha has not completed broad production-scale workload validation or general availability readiness.
- Browser-based CLI sign-in is not available; the CLI currently uses token-based authentication. Availability of a hosted CLI release endpoint depends on the distribution provided to you.
- GitHub connections use access-token setup; organisation-wide GitHub App installation and Bitbucket are not available.
- The deployment service is in pilot development and must not be used as a claim of production deployment availability.
- Customer-facing audit-log and vulnerability/security-report views are not released.
- Billing is arranged with our team; there is no self-service payment flow.
How this page is maintained
We review this page against release tags and delivery planning. If an item is in progress, it still requires the stated validation or rollout work before it is considered available.