Case Study

Making Application Deployment Faster Through DevOps

Real Estate
Industry
Real Estate (PropTech / Loyalty SaaS)
Services
Architecture Design, Backend Development, Frontend Development, DevOps, Quality Assurance
Company Size & Location
Startup / Growth-Stage SaaS, India
Technology Stack
Java · Spring Boot · Angular 10 · MySQL · Docker · Jenkins · Nginx · AWS (EC2, S3) · Review Board
Team
DevOps Engineer · Java / Spring Boot Developer · Angular Developer · QA Engineer
Timeline
Project-Based Engagement
01

Client Vision

Loyalie is a startup providing a suite of loyalty solutions specific to the real estate sector used by top developers to manage customer and channel partner loyalty. In fact, 5 of India’s 15 largest real estate builders, including Mahindra Lifespaces, Godrej Properties, Tata Housing, and the Lodha Group, use Loyalie. As adoption grew, Loyalie wanted to put its engineering on a more scalable footing - automating builds and deployments through a modern CI/CD pipeline, introducing containerization for consistent environments, and establishing disciplined code reviews and coding standards. The goal was to ship new releases faster and more reliably while raising overall code quality across its Java Spring Boot and Angular stack.

02

Challenge

Loyalie’s platform was already in active use by major developers, but its release process hadn’t kept pace with its growth. Deployments were entirely manual, code quality depended on individual discipline rather than a shared process, and the team wanted both addressed before scaling further.

Manual, Downtime-Prone Deployments  

Every release was deployed by hand, and each one introduced significant downtime for a platform relied on by large real estate developers. The process was slow, error-prone, and difficult to repeat reliably.

No Build or Containerization Automation  

There was no pipeline to automate application builds or packaging. Without containerization, environments drifted and releases were inconsistent across dev and production.

Inconsistent Code Quality  

Code was committed without a mandatory review step or enforced coding standards, leaving quality dependent on individual developers rather than a consistent, repeatable process.

Multi-Environment Tooling Complexity  

Standing up the review and build tooling surfaced real obstacles - configuring Review Board scripts and hooks consistently across multiple environments, and stopping Jenkins from misfiring duplicate builds on a single commit.

03

Solution

Focaloid implemented an end-to-end CI/CD and code-review workflow across Loyalie’s Spring Boot and Angular applications automating builds, introducing Docker-based packaging, and enforcing peer review on every commit.

Mandatory Code Review with Review Board  

Installed and configured Review Board so that on every code commit, the change is automatically shared for review and only approved after that review. Review was enforced on all Spring Boot application commits.

Containerized Applications  

Dockerized both the Spring Boot backend and the Angular frontend, giving the team consistent, reproducible environments from development through production.

Automated CI/CD with Jenkins  

Implemented DevOps integration using Jenkins to build Docker images for both applications automatically on commit, replacing the manual build-and-deploy process.

Branch-Based Deployment Strategy  

Configured Jenkins so commits to the dev branch push the Docker image straight to the dev server, while commits to the release branch are tagged and saved to Docker Hub giving the team a clean, predictable promotion path.

04

Our Approach

Focaloid worked alongside Loyalie’s engineering team to design and roll out the pipeline in structured phases, validating each piece before moving on.

Phase 1: Architecture & Tooling Design  

Assessed the existing Spring Boot and Angular stack and designed the target CI/CD architecture - selecting Review Board for code review, Jenkins for build automation, and Docker for packaging.

Phase 2: Code Review Enforcement  

Installed and configured Review Board, wiring commit hooks so every Spring Boot commit is sent for review and approved before merge - overcoming the complexity of configuring hooks consistently across multiple environments.

Phase 3: Containerization & Build Automation  

Dockerized both applications and set up Jenkins to build images automatically on commit, resolving early issues with Jenkins misfiring multiple builds per commit.

Phase 4: Branch-Based Deployment & Testing  

Implemented the dev/release branch strategy - automatic push to the dev server for dev commits, tagged images saved to Docker Hub for release commits - then tested the full pipeline end to end.

05

Result / Impact

For the Client

  • ~80% reduction in release deployment time after replacing manual deployments with an automated CI/CD pipeline (estimated)
  • Near-zero release downtime, down from significant downtime on every prior manual release
  • 100% of builds and Docker image creation automated through Jenkins, eliminating manual packaging effort
  • Consistent dev-to-production environments achieved through Docker-based containerization

For the Development Team

  • 100% of Spring Boot commits routed through mandatory peer review before merge
  • ~40% fewer defects reaching production through enforced code review and coding standards (estimated)
  • ~50% faster, more reliable promotion of code from dev to release via the branch-based strategy (estimated)
  • Reproducible builds across all environments, removing “works on my machine” inconsistencies

For the Business

  • Faster, lower-risk feature delivery to the major real estate developers relying on the platform
  • A scalable engineering foundation able to support continued growth without re-architecting the release process
  • Higher overall code quality and maintainability, reducing long-term technical debt

06

Why It Matters

For a loyalty platform trusted by some of India’s largest real estate developers, every release touches programs that thousands of customers and channel partners depend on. Manual, downtime-heavy deployments don’t just slow the engineering team- they risk disrupting live loyalty programs and eroding the trust of enterprise clients. By automating builds, containerizing the applications, and enforcing disciplined code review, Focaloid turned Loyalie’s fragile release process into a fast, repeatable, and reliable one. That foundation lets Loyalie ship with confidence and scale the platform without its delivery process becoming the bottleneck.

Let's build

Still deploying by hand and paying for it in downtime?

We help SaaS and product teams turn slow, manual releases into automated, reliable CI/CD pipelines with containerization, code-review discipline, and quality gates built in.