explaingit

missionfinops/local-ai-finops

Analysis updated 2026-05-18

0Audience · pm founderComplexity · 1/5Setup · easy

TLDR

A written architecture proposal for running AI-assisted cloud cost investigations inside a company's own data boundary instead of an external SaaS tool.

Mindmap

mindmap
  root((Local AI FinOps))
    What it does
      Architecture proposal
      Keeps data in-house
      Explains cloud costs
    Components
      Tools
      Skills
      Business RAG
      FinOps RAG
    Principles
      Local first
      Evidence backed
      Model is replaceable
    Related project
      Kulshan tool
    Audience
      Enterprise FinOps teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Study a proposed design for keeping AI-driven cloud cost analysis inside a company's security boundary.

USE CASE 2

Use as a reference architecture when planning an enterprise FinOps AI tool.

USE CASE 3

Evaluate how the Kulshan open source tool fits into a larger local AI FinOps design.

USE CASE 4

Get language for explaining why sending internal cost data to external AI platforms may be risky for regulated companies.

What is it built with?

AWSRAGLLM

How does it compare?

missionfinops/local-ai-finops00kaku/gallery-slider-block04amanrajj/netwatch
Stars00
LanguageJavaScriptRust
Last pushed2021-05-19
MaintenanceDormant
Setup difficultyeasyeasymoderate
Complexity1/52/53/5
Audiencepm foundergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

This is a design document, not runnable software, so there is nothing to install.

The README does not state a license for this document.

In plain English

This repository is not a piece of software you install and run. It is a written architecture proposal from Mission FinOps describing a possible design for using AI inside large companies to investigate cloud spending, while keeping sensitive company data under the company's own control rather than sending it to an outside AI service. FinOps refers to the practice of managing and explaining cloud computing costs. The document itself says clearly that this is a concept, version 0.1, and that not every piece described in it currently exists. The core problem the document lays out is that explaining a change in cloud costs usually requires pulling together many different kinds of internal information: billing data, business context, engineering changes, support tickets, ownership records, accounting details, and internal policies. For a regulated company, sending all of that sensitive information to an external AI platform may not be allowed. The proposal argues the real challenge is not picking which AI model to use, but building a trustworthy system around it that can show its evidence. The proposed design runs the AI model close to the company's own data, inside the company's own boundary. The AI model itself is treated as replaceable and can be swapped for any approved model, open source or otherwise. What stays constant are four building blocks: tools that collect and organize evidence, skills that represent repeatable investigation steps, a layer of business specific context, and a layer of general FinOps knowledge. The model's job is to interpret and explain the evidence, not to be treated as the source of truth itself. The document points to one existing open source project, called Kulshan, as an early building block for making AWS cost investigation more local and repeatable, though it notes Kulshan does not implement the full architecture described here. The proposal repeatedly stresses that any explanation the system produces should show its supporting evidence, note contradicting evidence, state its confidence level, and be honest about what remains unknown, rather than claiming certainty it cannot support.

Copy-paste prompts

Prompt 1
Summarize the four core components (tools, skills, business RAG, FinOps RAG) this architecture note proposes.
Prompt 2
Explain why this document argues the AI model should not be treated as the source of truth.
Prompt 3
What role does the Kulshan project play in this proposed architecture, and what is it missing?
Prompt 4
Help me understand the difference between evidence that is missing versus evidence that was evaluated and found nothing, as this document describes it.

Frequently asked questions

What is local-ai-finops?

A written architecture proposal for running AI-assisted cloud cost investigations inside a company's own data boundary instead of an external SaaS tool.

What license does local-ai-finops use?

The README does not state a license for this document.

How hard is local-ai-finops to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is local-ai-finops for?

Mainly pm founder.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.