MongoDB Financial Services Sao Paulo, Brazil

Base39

Risk Management

Base39 needed to replace slow, subjective credit analysis workflows that could take up to 10 days and required specialist intervention to adapt machine learning models to new data sources.

Base39 cut loan analysis costs by 96% and reduced infrastructure expenses by 84%.
The strategic partnership with MongoDB and AWS enabled Base39 to deploy a robust AI-driven solution in two weeks.
This complex and highly manual process can take up to 10 days and can yield inaccurate and incomplete results.
With a mission to deliver a service that enables its customers to analyze and assess up to 10 loan applications in a minute, Base39 sought a solution that would accelerate the review process.

Reported impact

Business outcome

Base39 deployed its AI-driven credit analysis platform in two weeks, cut loan-analysis costs by 96%, lowered infrastructure spend by 84%, and moved toward analyzing up to 10 loan applications per minute.

  • Cost Reduction
  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

Base39 rebuilt its credit analysis workflow on MongoDB Atlas running on Amazon Web Services and used MongoDB Atlas Vector Search as the feature and retrieval layer for agentic AI. Data from CRM systems, transactional records, and public databases is aggregated into Atlas, where flexible schemas let the team mix structured financial attributes with unstructured context. LangGraph orchestrates agents that call predictive machine learning models plus Amazon Bedrock-hosted Claude 3.7 Sonnet and Claude 3.5 Haiku models to recommend how data should be cleaned, transformed, and evaluated for loan risk. Atlas Vector Search enriches those LLM interactions with domain-specific context, supports real-time feature retrieval, and enables Chain-of-Thought reasoning over each application. Because the stack remained familiar to developers, Base39 shipped quickly while eliminating manual spreadsheet-driven analysis.

Data flow

CRM records, transactional histories, and public-database signals are aggregated into MongoDB Atlas, embedded and indexed with MongoDB Atlas Vector Search, then passed through LangGraph-orchestrated Bedrock model calls so agents can score loans, run what-if analysis, and surface risk recommendations to analysts.

Solution architecture

6 components · 4 layers
  1. Compute
    • Amazon Bedrock Hosts the large language models Base39 uses inside its credit-analysis workflow.
    • Claude 3.7 Sonnet Supports high-quality reasoning and generation for loan-risk analysis tasks.
    • Claude 3.5 Haiku Handles fast, lower-latency model tasks inside Base39's credit workflow.
  2. Storage
    • MongoDB Atlas Serves as Base39's core operational platform and feature store for structured and unstructured credit data.
  3. Serving
    • MongoDB Atlas Vector Search Retrieves relevant vectors and domain context so agentic workflows and models can analyze loan applications accurately in real time.
  4. Orchestration
    • LangGraph Orchestrates the agentic AI workflow that coordinates model calls and multi-step reasoning.

Architecture clues

  • Atlas Vector Search is used as the backbone of Base39's feature store.
  • MongoDB Atlas runs in a serverless deployment model on AWS.
  • The stack combines predictive ML scoring with LLM-based what-if evaluation.
  • The workflow uses a Chain-of-Thought methodology for autonomous analysis.

Evidence from the source

Base39 cut loan analysis costs by 96% and reduced infrastructure expenses by 84%.
“MongoDB Atlas serves as the backbone of Base39’s feature store, powering both structured and unstructured data analysis with MongoDB Atlas Vector Search.”
“MongoDB underpins the data layer, providing flexible schema support, vector search for LLM context, and a managed deployment model that aligns with Base39’s developer-first philosophy.”
“The strategic partnership with MongoDB and AWS enabled Base39 to deploy a robust AI-driven solution in two weeks.”
Transparency Evidence & methodology 100/100 reference value · 79% 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 confidence79%
  • 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
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • 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. MongoDB

    Base39 customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/base39
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jun 18, 2025 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jun 17, 2025 · MongoDB · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.