Know what is running
Sync compute, databases, volumes, storage, networking, backups, DNS, certificates, and more from supported providers.
Review resource coverageOpen-source multi-cloud monitoring
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.
Infrastructure inventory
Example view| 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 |
Connect the clouds you already use
One operational view
Cloud providers describe resources and health differently. CloudMoo brings the details your team needs into a consistent inventory without hiding the provider context underneath.
Sync compute, databases, volumes, storage, networking, backups, DNS, certificates, and more from supported providers.
Review resource coverageSchedule checks from one-minute intervals upward and surface failed, stopped, expired, missing, or provider-error states.
See how checks runReview recent status changes per asset and email configured recipients when a resource state changes. Retention and delivery follow your setup.
Explore the feature setProvider coverage
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 | Read docs |
| DigitalOcean | Droplets, databases, storage, networking, DNS, CDN, and certificates | Inventory + status | Read docs |
| Vultr | Compute, databases, storage, networking, and platform services | Inventory + status | Read docs |
| Hetzner | Servers, volumes, images, networks, and core cloud resources | Inventory + status | Read docs |
| Linode | Servers and volumes | Inventory + status | Repository |
| UpCloud | Servers and volumes | Inventory + status | Repository |
Normal sync and monitoring use read-only provider APIs. See each provider document for the exact coverage contract.
Self-hosted by design
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.
How it works
The setup is intentionally direct. Connect only what you want CloudMoo to observe, then let the built-in scheduler maintain the view.
Add read-only credentials with the permissions your team chooses.
CloudMoo inventories the resources in scope and keeps their provider context.
The worker records status changes and keeps a timeline for each monitored asset.
Review the affected resource, recent history, and provider response in one place.
Start with the source
Clone the repository, configure the application and provider credentials, then bring up the web app, database, worker, and scheduler.
View CloudMoo on GitHub$ git clone https://github.com/bilal414/cloudmoo.git
$ cd cloudmoo
$ cp .env.example .env
$ docker compose up --build