Case study 10 of 12 · /resources/case-studies/dexlyn

Driver tree design

Explaining what drives revenue, so the hero breaks revenue into ranked factors and the question stays pinned beside the story.

For review: SEO and checks (not shown to visitors)
SEO title
Dexlyn Case Study | DevOps TechLab (34 characters)
Meta description
Business questions answered through multi-step, evidence-based analysis. How DevOps TechLab built it on AWS. (108 characters)
URL
/resources/case-studies/dexlyn
Keywords
Amazon Bedrock, Nova Pro, ECS Fargate, Aurora PostgreSQL
Check before publishing
  • Rewritten from the case study on devopstechlab.com (PDF supplied 1 Oct 2026). No figures added beyond the original page.
  • Client has agreed to be named on the new site (confirmed 1 Oct 2026).
  • PENDING: original diagram file from the team, to replace the crop from the PDF.
  • PENDING: real figures from the team (time saved, speed or volume), measured with the client.
  • The original page contains an internal editorial note about unverified metrics. Remove it from the live site.
  1. Home
  2. Resources
  3. Case studies
  4. Dexlyn
AI & GenAIAWSQueryDashClient story

Dexlyn

Autonomous BI agent that explains what drives revenue

Business questions answered through multi-step, evidence-based analysis. Built on QueryDash, our agentic investigation platform on AWS.

Told by a Generative AI Engineer from DevOps TechLabBusiness intelligence2 min read

The client

Dexlyn uses QueryDash, our agentic investigation platform, for business intelligence.

A typical question the agent answers. “Determine the main factors affecting quarterly revenue.”
QueryDash is our agentic investigation platform on AWS: people ask questions in plain language, and an AI agent investigates the data and explains what it found.

The challenge

  • Understanding what drove revenue and other key metrics meant manual SQL and combining results by hand.
  • Complex business questions were slower to answer than the business wanted.

How the agent works

The agent loop

Understand the goal. The agent restates what you are trying to find out.

Production data stays protected. Every SQL statement is validated before it runs; write and schema-changing operations are rejected.

What we did

Discovery

understood the questions users needed answered, the data and how it relates, and defined secure, read-only access to production data.

The architecture

Architecture as built (QueryDash platform)
  • Amazon Bedrock
  • Nova Pro
  • ECS Fargate
  • Aurora PostgreSQL
  • DynamoDB
  • Secrets Manager

The result

  • Users ask in natural language instead of writing SQL or waiting for a technical team.

  • The agent runs multi-step investigations, recovers from failed queries and shows evidence for its findings.

  • Follow-up questions keep the context of the investigation.

  • Production data stays protected with read-only, validated access.

  • The same platform extends to new questions without building a new analytics workflow each time.

Want something like this for your team?

Tell us the questions your team asks or the work that slows you down. An engineer will suggest a small first build on Amazon Bedrock.

Next story · AI & GenAITrueestate: AI agent that investigates property and booking performanceListing design · 2 min read