Daestro

# Daestro > [Daestro](https://daestro.com) is a cloud-agnostic container orchestration platform designed to run compute workloads across multiple cloud providers and self-hosted infrastructure. ## Links [Documentation](https://daestro.com/docs) [Blog](https://daestro.com/blog) [Pricing](https://daestro.com/pricing) [sitemap.xml](https://daestro.com/sitemap.xml) ## Features - Cloud agnostic, works with AWS, DigitalOcean, Linode, Vultr and on-premise - Jobs can even be run on your own machine, either be laptop or enterprise server - View the logs for each job run in realtime or after job has completed - View metrics like CPU and Memory usage of each job run - Set fine grained controls on concurrency, priority and resource usage for your jobs - Use job queues to make sure high priority jobs get processed first - Cron jobs: Run recurring jobs on specified time - Schedule jobs to run at later time or date - Set custom CPU and Memory quota per job definition - Supports Docker image and arbitrary bash code - Jobs can be submitted from either Console (dashboard) or API - All the secrets and API keys are encrypted with AES-256 ## Console [Daestro Console](https://console.daestro.com) is the dashboard that let's user signup using Github or Google Oauth to access Daestro platform. ## Cloud Provider Daestro supports AWS, Vultr, DigitalOcean and Linode on it's platform. User can add the API for the cloud provider which they want to use to run jobs on. ## Cloud Auth Cloud providers i.e. AWS, Vultr, DigitalOcean and Linode are the first class citizen of the Daestro. Daestro directly works on the APIs of these cloud providers to provide complete integration. To do what Daestro does, it needs the API Key from these cloud providers to access resources on behalf of user account. User must create new **Cloud Auth** with the API key. Since Daestro uses users' cloud account to run compute, it is obvious that the usage cost of the server will fall upon user. Daestro only charges the platform use fee. All the other resource usage fee has to be bear by user. ### Creating Cloud Auth - Go to [Cloud Auth](https://console.daestro.com/cloud-auth) page - Click on [Add Cloud Auth](https://console.daestro.com/cloud-auth/add) - There will be shown a form which first asks to choose a **Cloud Providers** - Upon selecting a cloud provider more fields will be asked to be filled, such as in terms of AWS it will ask for "Access Key Id" and "Secret Access Key" while for Others (DigitalOcean, Linode, Vultr) it will ask for "Access Token" - After filling respective API keys user must give this cloud auth a meaningful name - API Keys are encrypted (using AES-GCM 256) and then stored in the db. ### Updating Cloud Auth - User can update name of the Cloud Auth - User can also update keys of the Cloud Auth upon confirming that the keys which are updated belongs to the same cloud provider account and if it does not then user owns the risk of service disruption due to mismatch of keys ### Deleting Cloud Auth - User can delete a Cloud Auth if there are no **Compute Environment** associated with it ## Compute Environment A specification defining the type of compute instance (VM), its location (region/zone), and the associated Cloud Auth. Think of it as a template for launching servers. ### Creating Compute Environment - Go to [Compute Environment](https://console.daestro.com/compute-env) - Click on [Add New](https://console.daestro.com/compute-env/add) - Select: Cloud Auth -> Among all the cloud auth user has created they will also see a special "Self-hosted Compute" option in the cloud auth list. - When Selected "Self-hosted Compute" - Name (Required): Identifiable name for the Compute Environment - Usable CPU Quota Percentage (Optional): Percentage of CPU core to be used for running jobs. 100% means it will use 1 full core, likewise 50% = 0.5 core, 400% = 4 core. Minimum value can be 10%, leave it blank to use full system capability. - Usable Memory Q […truncated]