Lagan — Source Control
Your code, wired into your workflow
Lagan hosts your repositories, handles pull requests and review, and pushes over SSH or HTTPS like any Git host you already know. What's different is what happens on push: it dispatches a real workflow in the same engine that runs the rest of your delivery process.
Why Lagan
Git hosting that doesn't stop at hosting
Clone, push, and review the way you always have. The difference shows up the moment your pipeline needs to do something more than run a script.
Git Over HTTPS and SSH
Standard Git access — clone, fetch, push — over smart HTTP or SSH, plus a browse view for trees, blobs, commit history, and branches.
Pull Requests and Review
Compare branches, discuss changes with inline, line-anchored comments, and merge with the strategy that fits — merge commit, squash, or rebase.
A Push Triggers a Real Workflow
There's no bolted-on CI runner translating your push into a separate system's job. A push to a trigger branch dispatches an actual AWE workflow — anything the engine can do, your pipeline can do.
Ticket References Resolve Automatically
Mention a Cunav or Togra reference like ULLAV-42 in a commit message or PR title, and it resolves automatically — one thread from ticket to shipped fix.
Same Identity, Same Access Model
Team-role permissions and single sign-on apply here exactly as they do everywhere else on the platform — no separate user database to keep in sync.
Live Status, Never Cached
Build and pipeline status shown against a commit or PR is read live from the workflow engine — what you see is what's actually running, not a stale cache.
Beyond CI
A push can do more than run tests
Most Git hosts treat CI as a separate system bolted on the side. Lagan doesn't have a CI runner of its own to bolt on — because it doesn't need one.
One engine, not two systems
Your build pipeline and your project workflows run on the exact same engine — there's no separate CI product to configure, secure, and keep in sync with the rest of the platform.
Human steps, mid-pipeline
A pipeline can pause for a real approval task, not just a manual gate hack — the same task model that runs your project workflows runs your pipeline.
AI-driven steps, mid-pipeline
A pipeline task can just as easily be a decision delegated to an AI agent via MCP — evaluating context and choosing the next step, without custom glue code.
We'll show the deep version soon
A closer look at why this beats bolting Actions or Jenkins onto a generic Git host is coming as this page develops — the short version is that Lagan shares every platform capability, not just a webhook.
How It Works
From push to production
What happens after `git push`.
You push
Over HTTPS or SSH, exactly like any Git host — to a feature branch or a configured trigger branch.
A workflow is dispatched
A push to a trigger branch calls the workflow engine directly, cloning and starting a workflow instance from your chosen template.
The pipeline runs, mixed as needed
Automated steps, human approvals, and AI-driven decisions execute as tasks in that workflow, with the same auditability as any other process on the platform.
Review, merge, and it's traced
Open a pull request, resolve any linked Cunav or Togra references, and merge with your chosen strategy — status shown is always read live.
Questions?
Frequently asked questions
Is this just GitHub with extra branding?
No — the git hosting and PR experience will feel familiar, but there's no separate CI product underneath. A push dispatches a real workflow in the same engine that runs your project management and support tooling, so your pipeline can include human approvals and AI-driven steps as first-class parts of the process, not just scripted checks.
Can we fork a repository?
Pull requests currently work branch-to-branch within the same repository. Fork-based contribution is on the roadmap — get in touch if that's a hard requirement for your team.
What merge strategies are supported?
Merge commit, squash, and rebase-merge — chosen per pull request.
Does Lagan support required status checks before merge?
That's on the roadmap and not yet enforced automatically — status is visible on every PR today, but gating the merge button on it is still to come.
Can we migrate from our current Git host?
Yes — repository and history migration is exactly the kind of work our consultancy engagements cover, alongside deciding which pipelines are worth rebuilding as AWE workflows first.
How is Lagan priced and deployed?
Lagan is offered on a project and agreement basis, hosted, on-site, or hybrid on Kubernetes, alongside the rest of the platform. Get in touch to discuss your team and repositories.
Ready for a pipeline that can do more than run tests?
Tell us about your current source control setup and where it stops short.