Databricks Financial Services India

Vivriti Capital

Enterprise Knowledge Search · Fraud Detection

Vivriti Capital needed to replace a legacy architecture consisting of Amazon Redshift, open source Spark, Airflow and custom orchestration to eliminate pipeline failures, compliance risks and manual engineering interventions across its API-driven lending business.

Core workloads (including ~20 workflows and 50+ pipelines) migrated within eight weeks, with development and client validation running in parallel to compress the timeline.
~20% Faster SQL performance and almost no downtime for faster deliverables
~25–30% Lower TCO, with reduced cloud, DevOps, and R&D support overhead
~8 weeks Phased migration with no disruption to lending operations

Reported impact

Business outcome

Reported outcomes include ~25–30% Lower TCO, with reduced cloud, DevOps, and R&D support overhead; ~20% Faster SQL performance and almost no downtime for faster deliverables; ~8 weeks Phased migration with no disruption to lending operations.

  • Cost Reduction
  • Productivity Improvement
  • Revenue Growth

Solution

Vivriti Capital built its Databricks implementation around Databricks SQL, Databricks Genie, Redshift, Airflow. Vivriti Capital needed to replace a legacy architecture consisting of Amazon Redshift, open source Spark, Airflow and custom orchestration to eliminate pipeline failures, compliance risks and manual engineering interventions across its API-driven lending business. Databricks SQL serves governed analytics, dashboards, and ad hoc queries for business users and operational teams. Databricks Genie lets business users ask natural-language questions over curated data. Redshift represents a legacy warehouse replaced or simplified by the new platform. Airflow represents legacy orchestration simplified by Databricks-native workflows. The solution also connects to Redshift, Airflow, API, so teams can work from a shared governed environment instead of disconnected tools.

Data flow

Source data is ingested into databricks, curated in shared lakehouse tables, processed with Databricks compute and orchestration services, and served through analytics, semantic search, or model endpoints for downstream users and applications. It connects with Redshift, Airflow, API.

Solution architecture

4 components · 3 layers
  1. Storage
    • Redshift Represents a legacy warehouse replaced or simplified by the new platform.
  2. Serving
    • Databricks SQL Serves governed analytics, dashboards, and ad hoc queries for business users and operational teams.
    • Databricks Genie Lets business users ask natural-language questions over curated data.
  3. Orchestration
    • Airflow Represents legacy orchestration simplified by Databricks-native workflows.

Architecture clues

  • Airflow
  • Databricks Genie
  • Databricks SQL
  • Migrating from Redshift and an in-house platform to reduce risk and cost
  • Phased migration with no disruption to lending operations
  • Redshift

Evidence from the source

Core workloads (including ~20 workflows and 50+ pipelines) migrated within eight weeks, with development and client validation running in parallel to compress the timeline.
Vivriti also uses Databricks Genie for semantic search and conversational analytics, replacing an in-house text-to-SQL solution built on large language models. By adopting a native capability, the team reduced infrastructure complexity and
~20% Faster SQL performance and almost no downtime for faster deliverables
~25–30% Lower TCO, with reduced cloud, DevOps, and R&D support overhead
~8 weeks Phased migration with no disruption to lending operations
“It was a fast, predictable, and well-orchestrated journey,” said Alagu Bala Kumar Narayanan, VP of Architecture and R&D.
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Databricks

    Vivriti Capital customer story

    First-party
    https://www.databricks.com/customers/vivriti-capital
    Source type
    Vendor-published customer story
    Published
    Feb 25, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Feb 25, 2026 · Databricks · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.