Skip to main content
Legia

DevOps & CI/CD

Legia streamlines how your application is tested and released to servers, turning a manual process only one person can run into an automated flow anyone on the team can repeat. The scope includes test environments, monitoring, and rollback mechanisms.

Pricing

How much does DevOps & CI/CD cost?

Cost is based on the number of applications and environments whose release flow is streamlined. One-off work and ongoing support are billed separately.

  • Number of applications in the release flow
  • Number of environments made consistent
  • State of the release flow running today
  • Scope of monitoring and alerts
  • Training needs for your team
Send Message

> Project plan

DevOps & CI/CD · 5 stages

How Legia does it

A general view of the order and length of each stage. A change in scope moves the estimate, and the details are agreed after the consultation.

  1. Mapping the current flow 1 week
  2. Quick-impact fixes 2–3 weeks
  3. Building the release flow 3–6 weeks
  4. Monitoring & securing releases 1–2 weeks
  5. Handover & training 2–3 weeks
Estimated total
2–3 months
Estimated total
Work stages
5 stages
With a written deliverable at each stage
Team response
1 day
Legia team response on business days

After handover, Legia can continue to support you through a monthly support contract or a subscription maintenance scheme, or step away entirely once your team is independent.

Legia's full process

Technology

Technology we build with

The tools actually used on this work. The choice adapts to the systems you already run rather than being forced into one mold.

Release flow

Tools that run automated testing and deployment every time code is updated.

  • GitHub Actions
  • GitLab CI
  • Jenkins
  • ArgoCD

Containers and infrastructure

Packages the application and writes its environment as code, so testing and production behave the same.

  • Docker
  • Kubernetes
  • Helm
  • Terraform
  • Ansible

Monitoring

Records and monitors performance, then gives early warning before users report a problem.

  • Prometheus
  • Grafana

Selected Work

Example projects involving DevOps

All Projects

Three projects that involved Legia's DevOps work, alongside their websites and security.

PT Kebon Agung website home page with a sugar product hero in a cane field and a products section beneath it

Manufacturing & Distribution · 2024

PT Kebon Agung

PT Kebon Agung Corporate Website

Read more ↗

Why Legia

What you receive

A tidy release flow is usually only noticed when the person who normally runs it is away. These six things make releases repeatable by anyone on your team and keep them safe.

  1. 01 · Design

    Handed over with training

    Your team runs it, Legia sets it up. The entire flow is handed over with training.

  2. 02 · Engineering

    Configuration as code

    All configuration is kept as code in your repository, readable and continuable by anyone.

  3. 03 · Ownership

    Open tools

    Built on common, open tools, so you are free to switch vendors without rebuilding.

  4. 04 · Ownership

    Release pipeline security

    Vulnerability scanning and management of keys and secrets are part of the release flow, not separate work afterwards. Access is set per role and check results are recorded.

  5. 05 · Reports

    Measured before and after

    Release frequency, time from finished code to running on the server, recovery time after a problem release, and release failure rate are recorded before the work and measured again afterwards.

  6. 06 · Engineering

    Release flow documentation

    Documentation of the release flow and a guide for handling failures.

FAQ

Frequently asked questions

Haven't found your answer? Tell us what you need, and the Legia team replies within 1 business day.

Ask the Legia team ↗
What is a DevOps service?

A DevOps service streamlines how an application is tested and released to servers: automated release flows, consistent environments, monitoring, and rollback mechanisms. Legia sets it up in stages and hands it to your team, with training and the configuration in your repository.

How much does a DevOps service cost?

Cost depends on the number of applications handled, the starting state of your release flow, and whether the environments are already in the cloud. Legia gives the figure after the flow assessment stage, which can be taken separately.

Does every team need DevOps?

No. If your application rarely changes and is released only a few times a year, the cost of setting up an automated flow probably does not pay off. DevOps benefits most when releases are frequent, involve several people, or have failed and been hard to roll back. Legia gives this assessment in the first session, before a scope is drawn up.

What is the difference between DevOps and server management?

Server management keeps the server running, secure, and fast. DevOps streamlines how your application is tested and gets to that server. They are often done together, but answer different problems.

What security is in the release flow Legia builds?

Vulnerability scanning and management of keys and secrets are part of the release flow, with access set per role and check results recorded. The scope of checks is agreed at the flow assessment stage.

Can our team still release on its own after the project ends?

Yes, and that is the point. Legia sets up the release flow, and your team runs it. Handover includes training and support until your team releases without help. If needed, support can continue through a monthly support contract or a subscription maintenance scheme, billed separately.

Does the release flow lock us in to Legia?

No. Legia builds on common, open tools. All configuration is kept as code in your repository, so any party can read, change, and continue it.

Will our current release process be disrupted?

No. The new flow is built in stages and runs alongside the old way until it proves stable. The full switch is only made once your team is confident.

Can Legia provide a DevOps engineer to join our team?

Yes, through the dedicated team service in the IT Support & Consulting pillar. If what you need is a one-off fix with handover, this DevOps service is the better fit.

How long until the automated release flow is usable?

The whole process, from flow assessment to handover, takes about 9–15 weeks. The highest-impact fixes are done first, with environment consistency and monitoring following, depending on the starting state of your system.