All work

AMove

Enterprise & Business Software · File & Knowledge Management

From reliability foundations to AI knowledge retrieval inside a live cloud product

A longitudinal brownfield engagement: reliability and coverage work first, then AI-assisted ingestion and retrieval across knowledge bases held in different cloud storage services.

BrownfieldRetrievalReliabilityAWS
Product viewAMoveReplace with a 16:10 product screenshot

The starting point

A file and cloud management product, desktop application and web portal, in use by customers across multiple cloud storage services.

What had to change

Critical paths built up over years had uneven coverage, and later the product needed knowledge scattered across different cloud storage to be retrievable inside the workflow.

What couldn't break

Everything had to be delivered without freezing the roadmap or disrupting a product customers depend on.

Why this was hard

Coverage had to be earned across a multi-year codebase, and knowledge retrieval had to work across knowledge bases stored in different cloud services with different access models.

What Datics changed

First a structured quality and regression strategy across the portal's critical paths, then AI-assisted ingestion, vectorization and retrieval across knowledge bases in different cloud storage, with Slack interaction and workflow automation.

In sequence, alongside ongoing product work: stabilize the foundation, then add the AI retrieval and workflow capability on top of it.

Reliability foundation

A structured quality and regression strategy across the portal's critical paths.

AI ingestion and vectorization

AI-assisted ingestion and vectorization of knowledge bases.

Cross-cloud retrieval

Retrieval across knowledge held in different cloud storage services.

Slack workflow automation

Slack interaction and workflow automation on top of retrieval.

System flowAMove workflow / architectureReplace with a workflow or architecture visual

What changed

A more predictable product, and knowledge held across different cloud storage services now retrievable through the workflows people already use.

Delivery freeze required
None. Work added alongside feature delivery
Phase one
Regression coverage across a multi-year codebase
Phase two
AI ingestion, vectorization and retrieval

Under the hood

Datics role
Quality engineering followed by AI product engineering: test strategy and regression coverage, then ingestion, vectorization, retrieval and Slack workflow automation.
Integrations
The product's desktop application, web portal, the cloud storage services behind them, and Slack.
Deployment
Customer's production cloud environment on AWS, with OpenAI, Python, Node, React, LangChain, a vector database and the Slack API; tested with Selenium, Cypress, JMeter and OWASP ZAP.
Production boundary
Customer's production cloud environment.

Technology

AWSOpenAIPythonNodeReactLangChainVector databaseSlack API

What this unlocked

The retrieval and automation layer is the base for further capability inside the product.

Published write-up on datics.ai

Have a product with the same kind of constraints?

Tell us what already exists and what you want it to do. We will tell you what it takes.

Book a 30-minute product review