Blazing Core

Blazing Core is our multi-cloud, policy-driven orchestration service that enables you to describe compute workloads once and deploy them transparently across multiple cloud providers.

What is Core Compose?

Core Compose is the YAML configuration format used by Blazing Core. It merges the simplicity of Docker Compose with the power of declarative cloud infrastructure. Write your infrastructure once in a compose.yaml file, and Blazing Core handles provider selection, placement, networking, security, and compliance automatically.

Supported Providers

• GCP GKE - Google Kubernetes Engine
• Akash Network - Decentralized compute network
• Digital Frontier Cloud (DFC) - Managed cloud infrastructure

Coming Soon

• AWS EKS - Amazon Elastic Kubernetes Service
• Azure AKS - Azure Kubernetes Service

Key Features

Declarative Configuration

Define your entire infrastructure in a single compose.yaml file:

Intelligent Provider Selection

Blazing Core automatically selects the best provider based on your requirements:

• Cost optimization - Lowest price for your workload
• Performance - Best latency and throughput
• Compliance - Data residency and regulatory requirements
• Availability - High availability with automatic failover

Policy-Driven Governance

Enforce compliance and security policies across all deployments:

Automatic Scaling

Built-in autoscaling with CPU, memory, and custom metrics:

GPU Support

First-class GPU support with topology awareness:

Secrets Management

Secure secrets injection with automatic rotation:

Core Concepts

Services

The smallest deployable unit - a container with compute resources, networking, and policies.

Profiles

Reusable configuration templates that can be applied to multiple services:

Sovereignty

Define organization-wide sovereignty policies that control where and how your workloads run:

Governance & Compliance

Blazing Core includes feature registry and compliance controls that validate deployments:

• Feature Registry - Tracks available capabilities per provider
• Control Registry - Maps compliance requirements to technical controls

How It Works

1. Write Your Configuration

Create a compose.yaml file describing your infrastructure.

2. Validate

Run core validate to check syntax and compliance locally:

3. Plan

Preview what will be deployed:

Blazing Core shows:

• Selected provider and fallback chain
• Estimated cost
• Compliance status
• Resource allocation

4. Apply

Deploy your infrastructure:

The Control Plane API:

• Runs placement algorithms
• Provisions resources atomically
• Returns deployment status and audit trail

Architecture

Client-Side (CLI)

• Validation - Fast local syntax and schema checking
• Display - Shows deployment intent and results

Server-Side (Control Plane API)

• Placement - Intelligent provider and region selection
• Provisioning - Atomic resource creation
• Orchestration - Handles async operations
• Auditing - Complete deployment history

This server-side intelligence architecture ensures:

• Consistent placement across all interfaces (CLI, Web UI, mobile)
• Real-time provider availability and pricing
• Atomic operations (all resources created or none)
• Crash recovery (server continues if client disconnects)

Use Cases

Multi-Cloud Deployment

Deploy the same workload across multiple clouds for redundancy:

Data Residency Compliance

Ensure data stays within specific countries:

Cost Optimization

Automatically select the cheapest provider:

GPU Workloads

Run ML training with GPU slicing:

Getting Started

Ready to deploy your first workload? Check out the Quick Start guide.

Learn More

• Architecture - Understand how Blazing Core works
• Service Configuration - Configure your services and workloads
• Provider Capabilities - Compare provider features
• Governance & Compliance - Features and controls