Skip to main content

Introduction

The Cloudbear Automation Platform (CAP) deploys and runs your applications from a single configuration file. You describe what your application needs, and CAP provisions and maintains it.

Our goal is to provide a seamless and opinionated way to deploy applications, handle environment variables, manage services like databases and queues, and integrate with CI/CD pipelines, all through a single, declarative configuration.

How CAP works

CAP uses a config.cap.yaml file, placed in your application's repository, as the primary source of truth for your infrastructure definition. This YAML file describes your application's requirements, such as:

  • HTTP Endpoints: How your application is exposed to the web.
  • Environment Variables: Configuration specific to your application, including secrets management.
  • Services: Definitions for databases (e.g., MariaDB, PostgreSQL), message queues (e.g., RabbitMQ), and caching layers (e.g., Dragonfly).
  • Workers & Cronjobs: Background processes and scheduled tasks.
  • Pipelines: Integration with your CI/CD system to automate builds and deployments.

CAP reads this file on every deployment and provisions whatever it describes. You define what you want; CAP works out how to run it, so there is no infrastructure to write or maintain yourself.

Dive into the Tutorials to get started, explore How-To Guides for specific tasks, and consult the Reference section for detailed information on every configuration option.

Back to top