Case study 11 of 12 · /resources/case-studies/trueestate

Listing design

Property and bookings, so the hero is a listing card with a booking funnel the agent investigates.

For review: SEO and checks (not shown to visitors)
SEO title
Trueestate Case Study | DevOps TechLab (38 characters)
Meta description
Why did bookings drop? The agent explores the data and shows its evidence. How DevOps TechLab built it on AWS. (110 characters)
URL
/resources/case-studies/trueestate
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. Trueestate
AI & GenAIAWSQueryDashClient story

Trueestate

AI agent that investigates property and booking performance

Why did bookings drop? The agent explores the data and shows its evidence. Built on QueryDash, our agentic investigation platform on AWS.

Told by a Generative AI Engineer from DevOps TechLabReal estate2 min read

The client

Trueestate uses QueryDash, our agentic investigation platform, for real estate.

A typical question the agent answers. “Investigate why property bookings declined.”
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 why property and booking activity changed meant manual SQL across several data points.
  • Insights arrived late and depended on technical expertise.

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

  1. 01
    Discovery

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

  2. 02
    Platform

    QueryDash, our agentic investigation platform on AWS. A React web app on CloudFront and S3, an Application Load Balancer, the agent on Amazon ECS Fargate, Amazon Bedrock with Amazon Nova Pro, conversation and investigation memory in DynamoDB, credentials in AWS Secrets Manager, monitoring in CloudWatch.

  3. 03
    The agent loop

    understand the goal, plan, discover the data, generate SQL, validate it as read-only, execute, analyse, then replan or retry until it can explain the answer.

  4. 04
    Safety

    every SQL statement is validated before it runs; write and schema-changing operations are rejected.

  5. 05
    Onboarding

    database connectivity, Bedrock and Nova Pro configuration, secure credentials, read-only SQL validation, conversational context, real-time streaming and validation of representative scenarios.

  6. 06
    Operations

    application, infrastructure and agent monitoring, query support, troubleshooting and ongoing tuning of planning, SQL generation and recovery.

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 · Backup & DRDynawiild Engineering: Business data copied to Amazon S3 automatically, for disaster recoveryVault design · 3 min read