whatisgithub

What is nimbus?

hritvikgupta/nimbus — explained in plain English

Analysis updated 2026-05-18

4PythonAudience · ops devopsComplexity · 4/5LicenseSetup · moderate

In one sentence

A self-hostable AI agent that reads your code and connects to real AWS and GCP accounts to design, deploy, monitor, and repair cloud infrastructure through chat.

Mindmap

mindmap
  root((Nimbus))
    What it does
      Talks to your cloud
      Reads code and repairs it
      Opens pull requests
    Tech stack
      React
      Express
      SQLite
      MCP servers
    Use cases
      Manage AWS and GCP
      Auto-fix repos
      Architecture canvas
    Audience
      DevOps engineers
      Platform 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

Manage AWS and GCP resources through a conversational agent instead of separate cloud consoles.

USE CASE 2

Have an AI agent read a broken repo and open a fix pull request automatically.

USE CASE 3

Design and visualize cloud architecture on a live canvas before deploying it.

USE CASE 4

Track cloud cost, logs, and telemetry in one shared team workspace.

What is it built with?

PythonReactExpressSQLiteVercel AI SDKMCPDocker

How does it compare?

hritvikgupta/nimbus1038lab/agnes-aiadeliox/klein-head-swap
Stars444
LanguagePythonPythonPython
Setup difficultymoderateeasymoderate
Complexity4/52/53/5
Audienceops devopsvibe coderdesigner

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

How do you get it running?

Difficulty · moderate Time to first run · 30min

Needs an AWS or GCP account, an AI model provider API key, and a generated encryption key for stored credentials.

So what is it?

Nimbus is an AI agent that lets you manage your cloud infrastructure by talking to it in plain language, instead of switching between separate cloud consoles, terminals, CI dashboards, and infrastructure files. It reads your code, understands your architecture, connects to your real AWS and GCP accounts, and can fix problems in your repositories by opening pull requests. The project is built around a few core ideas. You describe the outcome you want, Nimbus proposes a plan, and you approve it before anything runs. Reading information from your cloud accounts happens automatically, but any action that changes a billable resource always waits for your explicit approval first. Everything the agent says is meant to be backed by something it actually read or ran, such as a specific file, a log line, or a live resource, so answers are grounded rather than guessed. Teams share one workspace per project, including channels, cloud connections, and an architecture canvas, while private chats with the agent stay personal. Key features include a chat interface built on a ReAct style tool use loop, a live architecture canvas that draws system diagrams such as load balancer to app to database as you design them, and connections to AWS and GCP through per user MCP servers using your own credentials. It can also connect to a laptop or a CI runner you control, then drive a local Claude Code session step by step to fix a repository, before pushing a branch and opening a pull request. Credentials are encrypted at rest, never shown or logged, and every action leaves a server side audit trail. Under the hood it is a React single page app talking to a thin Express API server, backed by SQLite for storage and Zod for validation. The AI layer uses the Vercel AI SDK with Databricks as the main model provider and OpenRouter as a fallback, plus the Model Context Protocol for connecting to cloud services. The easiest way to run it yourself is with Docker Compose: clone the repo, copy the example environment file, generate an encryption key, fill in your AI provider details, and start the container. The project is released under the Business Source License 1.1, which is source available but places restrictions on competing commercial use.

Copy-paste prompts

Prompt 1
Walk me through setting up Nimbus with Docker Compose and connecting my AWS account.
Prompt 2
Explain how the plan-then-act approval flow works for actions that change billable resources.
Prompt 3
How does Nimbus use per-user MCP servers to scope AWS and GCP access?
Prompt 4
Help me understand how the repairs feature drives Claude Code to fix a repo and open a PR.

Frequently asked questions

What is nimbus?

A self-hostable AI agent that reads your code and connects to real AWS and GCP accounts to design, deploy, monitor, and repair cloud infrastructure through chat.

What language is nimbus written in?

Mainly Python. The stack also includes Python, React, Express.

How hard is nimbus to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is nimbus for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.