Skip to content
Livra · with Claude

Ship Jira features with Claude, and stay in control

Pick the tickets — or simply describe the change. Claude finds the code, writes a plan you approve, builds it stage by stage across your repositories, opens the merge requests and writes the documentation. Nothing is pushed or merged without your team.

Request a demo Watch the video

Free for 30 days, then a simple subscription per organisation.

A feature in Livra: its phases, environments and tickets A feature in Livra: its phases, environments and tickets
Video

See how teams and freelancers work in it

A guided tour: a feature from tickets or a plain description to merged code, code review and merging, an organisation’s people and roles, and a freelancer’s own workspace.

Plays from YouTube, which may set cookies once you press play. Watch on YouTube
Works with the tools your team already usesGitLab · GitHub · Bitbucket · Azure DevOps · Jira · Linear · Slack · Microsoft Teams · Google Chat · Sourcebot · Figma · MCP
How it works

Five phases, one decision-maker: you

Every feature moves through the same steps. Claude does the work; you approve what matters.

  1. 1

    Set up

    Pick the Jira tickets, or describe the change in your own words. Claude finds the repositories and branches it touches.

  2. 2

    Check

    Claude checks the branches, the layers and the setup before anything changes.

  3. 3

    Plan

    You read exactly what will change, repository by repository, and approve it.

  4. 4

    Build

    Claude builds stage by stage and opens merge requests. You confirm every push.

  5. 5

    Document

    Run documentation, reports and API collections are written for you.

Built for real codebases

Across every repository a ticket touches

Claude learns where each ticket lives — libraries, APIs, gateways, front ends — and builds in the right order: shared code first, then the services that use it. Each stage opens its merge requests and waits for you.

  • Plans grouped by repository and stage, with the reason for each change
  • Merge requests reviewed, merged or closed in the app, within your organisation’s rules
  • Development, staging and production passes, with your own environments
The Build phase: stages and merge requests The Build phase: stages and merge requests
Capabilities

Everything a delivery team needs around Claude

Approvals built in

Plans, pushes, merge request creation and configuration changes wait for a person. Claude can never merge, approve or force-push.

Claude your way

Your Anthropic API key, Amazon Bedrock, Google Vertex AI, Microsoft Foundry or your company’s LLM gateway — or prepaid Livra Claude credit, with no account to set up.

Rules that fit your code

The pipeline’s rules are yours to edit. Claude can learn your architecture from your repositories and propose new rules for you to review.

Organisations and roles

Each organisation has its own people, Claude account, connectors, rules, environments and budget. Owner, admin and member roles are checked on every action.

Told when it matters

When Claude needs you, a step is done or something fails: in the app, by web push on any device, on WhatsApp, or in your team’s Slack, Microsoft Teams or Google Chat channels.

Insights and forecasts

Lead time, success rate and Claude’s cost per feature, with this month’s budget forecast — so you see delivery improve and spending coming.

Single sign-on and SCIM

Sign in with Okta, Microsoft Entra ID, Google Workspace or any OpenID Connect or SAML provider. People join and leave through SCIM.

Merge requests, reviewed

Claude reviews merge requests and fixes failed pipelines when you ask; a second approval for sensitive environments; release notes when everything is merged.

No issue tracker? Describe it

No Jira or Linear? Write what should change, with its Figma links or design images. Claude finds where the code lives and carries on; add another description later and pick which ones each run works on.

For freelancers too

Work on your own, outside any organisation, at freelancer prices: your GitLab, code search and Claude in your own workspace. Review and merge with your own GitLab access.

English and French

The whole app, its emails and notifications, in each person’s language. Help and the Academy too.

All features, with their phase and status All features, with their phase and status
Security

Your code, your keys, your rules

  • Secrets are encrypted and never shown again — only their last four characters
  • Organisations are isolated: no connector, key or feature is shared between them
  • Claude works in temporary folders that are removed afterwards
  • Single sign-on (OIDC, SAML), SCIM, two-step verification, IP allow-list and an audit log you can download
  • Hosted for you: HTTPS, daily backups and updates included
More on security →
For every role

One place for the whole team

Developers

Start a feature from its tickets, follow Claude live, answer its questions, approve each push and review the merge requests without leaving the app.

Engineering managers

See every feature’s phase and status, set budgets and models, decide who may merge, and fit the rules to your architecture.

Freelancers

Your own workspace: connect your GitLab and code search, set up your Claude account, and review and merge with your own GitLab access. Join a client’s organisation when it invites you.

Owners and admins

Invite your people or provision them with SCIM, connect your code host and tracker, choose your Claude account and budget, and pay by card, PayPal or mobile money.

Livra Academy

Learn it in an afternoon

Short lessons for developers, admins and owners — from your first feature to fitting the rules to your code.

Start learning
1Getting startedEveryone
2Building with ClaudeDevelopers
3Running your organisationOwners and admins

See it on your own tickets

A 30-minute demo with your Jira and GitLab, or bring your whole organisation onto the platform.

Request a demo Bring your organisation