All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Integrating an AI Agent into a Legacy Ruby on Rails Application with Sensitive Data

By

cionescu1

5mo ago· 6 min readen

Summary

A Director of Engineering at Mon Ami shares their experience integrating an AI agent into a 7-year-old Ruby on Rails monolith that handles sensitive aging and disability case worker data. The article details how they implemented the AI agent using RubyLLM, maintained existing Pundit authorization policies, and leveraged Algolia search without creating parallel systems or compromising security constraints. The solution focuses on improving client record lookup performance while preserving the multi-tenant architecture's data sensitivity requirements.

Key quotes

· 4 pulled
I'm a Director of Engineering at Mon Ami, a US-based start-up building a SaaS solution for Aging and Disability Case Workers.
We built a large Ruby on Rails monolith over the last 7 years. It's a multi-tenant solution where data sensitivity is crucial.
Looking up clients' records is, in particular, an action that is just not performant enough with raw database operations.
I walk through how I added the first AI agent tool using RubyLLM, Pundit policies, and our existing Algolia search, without introducing a parallel system or loosening constraints.
Snippet from the RSS feed
We run a multi-tenant Rails application with sensitive data and layered authorization. In this post, I walk through how I added the first AI agent tool using RubyLLM, Pundit policies, and our existing Algolia search, without introducing a parallel system

You might also wanna read