Open-source multi-cloud monitoring

Your cloud infrastructure, in one clear view.

Connect AWS, DigitalOcean, Vultr, Hetzner, Linode, and UpCloud. CloudMoo inventories supported resources, checks provider-reported status on a schedule, and records changes in a dashboard you host.

  • MIT licensed
  • Read-only provider access
  • Self-hosted

Infrastructure inventory

Example view
Checks scheduled
Provider Resource Type Status
AWS production-apius-east-1 EC2 Running
DigitalOcean primary-postgresnyc3 Database Online
Vultr media-storageewr Object storage Available
Hetzner edge-worker-02fsn1 Server Attention
Status history and provider context stay with each resource.

Connect the clouds you already use

AWS DigitalOcean Vultr Hetzner Linode UpCloud

One operational view

Stop switching between cloud consoles.

Cloud providers describe resources and health differently. CloudMoo brings the details your team needs into a consistent inventory without hiding the provider context underneath.

Inventory

Know what is running

Sync compute, databases, volumes, storage, networking, backups, DNS, certificates, and more from supported providers.

Review resource coverage
Monitoring

Catch meaningful changes

Schedule checks from one-minute intervals upward and surface failed, stopped, expired, missing, or provider-error states.

See how checks run
History and alerts

Keep the incident context

Review recent status changes per asset and email configured recipients when a resource state changes. Retention and delivery follow your setup.

Explore the feature set

Provider coverage

Broad visibility, documented precisely.

Coverage varies by provider. The repository documents what CloudMoo inventories, what it monitors, and where provider-specific behavior still applies.

Provider Current coverage Monitoring Documentation
AWS EC2, EBS, RDS, Lambda, DynamoDB, S3, ECS, Lightsail, and more Inventory + status
DigitalOcean Droplets, databases, storage, networking, DNS, CDN, and certificates Inventory + status
Vultr Compute, databases, storage, networking, and platform services Inventory + status
Hetzner Servers, volumes, images, networks, and core cloud resources Inventory + status
Linode Servers and volumes Inventory + status
UpCloud Servers and volumes Inventory + status

Normal sync and monitoring use read-only provider APIs. See each provider document for the exact coverage contract.

Self-hosted by design

Run CloudMoo in your environment.

CloudMoo is MIT-licensed and includes a Docker Compose setup for the Django app, PostgreSQL, RabbitMQ, Celery worker, and scheduler. Your instance stores its inventory and status history in your database and connects to the provider APIs and email backend you configure.

CloudMoo stack Docker Compose
Django
Web console and REST API
PostgreSQL
Accounts, assets, and status history
Celery + RabbitMQ
Scheduled syncs and monitoring checks
Your email backend
SMTP, Amazon SES, or another Django backend

How it works

From credentials to a useful inventory.

The setup is intentionally direct. Connect only what you want CloudMoo to observe, then let the built-in scheduler maintain the view.

  1. 01

    Connect a provider

    Add read-only credentials with the permissions your team chooses.

  2. 02

    Sync resources

    CloudMoo inventories the resources in scope and keeps their provider context.

  3. 03

    Run scheduled checks

    The worker records status changes and keeps a timeline for each monitored asset.

  4. 04

    Follow up with context

    Review the affected resource, recent history, and provider response in one place.

Start with the source

Start with Docker Compose.

Clone the repository, configure the application and provider credentials, then bring up the web app, database, worker, and scheduler.

View CloudMoo on GitHub
TerminalQuick start
$ git clone https://github.com/bilal414/cloudmoo.git
$ cd cloudmoo
$ cp .env.example .env
$ docker compose up --build