Skip to content

krishnaramadas/DRACO

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

5 Commits
Β 
Β 

Repository files navigation

πŸ‰ DRACO β€” DataOps Response And Cost Optimization

A Snowflake-native AI platform for DataOps incident response and cost intelligence β€” built entirely on Snowflake Cortex, Cortex Search, and Streamlit in Snowflake. No external APIs. No hosting. Pure Snowflake.

Status Platform AI UI


🧩 What is DRACO?

DRACO is a unified DataOps intelligence platform with two core capabilities:

πŸ”§ Tab 1 β€” DataOps Incident Assistant (DoRRA)

An AI-powered L1/L2 shift assistant that helps on-call engineers during production incidents β€” without guessing or hallucinating fixes.

Given an incident, DRACO can answer:

  • "What are the documented troubleshooting steps for this pipeline?"
  • "Has this error happened before? What was the resolution?"
  • "Is this expected behaviour?"
  • "Who do I escalate to for a P2 bridge call?"

DRACO only surfaces what developers have explicitly documented in runbooks or historical incident records. If the answer isn't documented β€” it says so and provides escalation contacts. No hallucinated fixes on production systems.

πŸ’° Tab 2 β€” Cost Intelligence Assistant

A Snowflake-native cost dashboard powered by SNOWFLAKE.ACCOUNT_USAGE with an embedded AI chat assistant β€” giving engineers visibility into warehouse spend, query costs, and storage usage without leaving Snowflake.


πŸ—οΈ Architecture

ChatGPT Image Feb 25, 2026, 07_00_15 PM

βš™οΈ Tech Stack

Layer Technology
Database Snowflake
AI Search Snowflake Cortex Search
LLM Snowflake Cortex (Mistral / Llama)
Orchestration Snowflake Tasks + Streams
UI Streamlit in Snowflake
Data Ingestion Snowpipe, External Stages
Cost Data SNOWFLAKE.ACCOUNT_USAGE (native)

Zero external dependencies. 100% Snowflake native.


πŸš€ Project Status

  • Architecture design
  • Mock runbooks (5 pipelines, varied formats)
  • Mock incident archive schema
  • Snowflake DDL + table setup
  • Cortex Search service configuration
  • Streamlit app β€” DataOps tab
  • Streamlit app β€” Cost tab
  • End-to-end testing
  • Demo video

πŸ’‘ Design Decisions

Why strict docs-only responses? DRACO is designed for production DataOps environments. Hallucinated troubleshooting steps on live pipelines are dangerous. The system prompt explicitly prohibits the LLM from suggesting fixes that aren't documented by the development team.

Why fully Snowflake-native? No external hosting, no API keys, no infra to manage. Everything β€” data, AI, and UI β€” lives inside Snowflake. This makes DRACO portable, secure, and easy to demo from a single Snowflake account.


πŸ‘€ Author

Krishna Ramadas β€” Senior Data Engineer 4+ years building production DataOps systems for Fortune 500 clients.

LinkedIn GitHub


πŸ“„ License

MIT License β€” see LICENSE for details.

Releases

No releases published

Packages

No packages published