kForge fits if…
- You are an IT services company, integrator or managed service provider.
- You equip several subsidiaries or entities that must stay separate.
- Your repositories must stay on your servers.
kForge use case
Continuous integration for all your clients
Software forges and continuous integration tools are designed for a single organisation. Serving twelve isolated clients means installing, upgrading and administering twelve platforms.
The short answer
kForge brings repository tracking, continuous integration, code analysis, tickets and deployment metrics together in a single application installed on your premises. Each client is isolated within the same installation: a developer at client A never sees that client B exists.
One installation, isolated clients
Isolation is not a split by project: every record carries its client identifier, filtered on every request.
- One upgrade instead of one per client
- GitHub, GitLab and local repositories, which stay where they are
- A ticket can be escalated to the parent client if it allows it
Continuous integration without a proprietary format
Stages, jobs in a dependency graph, matrices; execution in a shell, container, Kubernetes or over SSH.
- Twelve quality gates before a production release
- Pipelines imported and exported in YAML
- Export to GitHub Actions format if you leave
Is it the right tool for you?
Limits to know
- Code review and merging still happen on GitHub or GitLab.
- Git runs through an agent installed on your machines, not on the kForge server.
- Pricing is still being defined.