Documentation

Deploy BackPro AI

Production-ready deployment to Azure, AWS, or Google Cloud Platform

Overview

BackPro AI deploys as a fully managed solution within your own cloud subscription. This ensures complete data sovereignty — your documents and data never leave your controlled environment. Choose your preferred cloud provider below to get started.

Select Your Cloud Provider

Architecture

The deployment provisions a complete production environment with the following components:

  • Backend API — Azure Container Apps running the BackPro AI service
  • GPU Compute — NVIDIA T4 GPU workload profile for AI inference
  • PostgreSQL Database — Azure Database for PostgreSQL Flexible Server
  • Redis Cache — Azure Cache for Redis for sessions and caching
  • Blob Storage — Azure Storage Account for document storage

Prerequisites

Cloud Provider Requirements

  • An active Azure subscription (Pay-As-You-Go or Enterprise Agreement)
  • Owner or Contributor role on the subscription
  • GPU quota allocation (8 cores) — see Requesting GPU Quota

Local Machine Requirements

  • Azure CLI — Version 2.50.0 or higher
  • jq — Command-line JSON processor

Installing Prerequisites

macOS:

Terminal
# Install Azure CLI
brew install azure-cli

# Install jq
brew install jq

# Verify installations
az --version
jq --version

Windows (PowerShell as Administrator):

PowerShell
# Install Azure CLI
winget install Microsoft.AzureCLI

# Install jq
winget install jqlang.jq

# Verify installations
az --version
jq --version

Linux (Ubuntu/Debian):

Terminal
# Install Azure CLI
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

# Install jq
sudo apt-get update && sudo apt-get install -y jq

# Verify installations
az --version
jq --version

What You Receive from BackPro

After completing your purchase, you will receive the following from our team:

  • Deployment Package — Contains deployment scripts and configuration templates
  • Container Registry Credentials — Access to BackPro container images
  • Licence Key — A JWT token that activates your BackPro AI installation

Keep these credentials secure. The container registry credentials and licence key should be treated as sensitive information.

Supported Regions

BackPro AI requires GPU compute, which is available in the following Azure regions:

Australia East
Brazil South
Central India
East US
France Central
Italy North
Japan East
North Central US
South Central US
Southeast Asia
South India
Sweden Central
West Europe
West US
West US 2
West US 3

Step 1: Request GPU Quota

Azure requires you to request GPU quota before deployment. This is a one-time process that typically takes 1-3 business days for approval.

  1. Sign in to the Azure Portal
  2. Navigate to Subscriptions and select your subscription
  3. In the left menu, select Usage + quotas
  4. Click Request increase
  5. Search for Container Apps Consumption GPU Cores
  6. Select your target region and request 8 cores
  7. Provide a brief justification (e.g., "Deploying BackPro AI for document processing")
  8. Submit the request and wait for approval

You will receive an email notification when your quota request is approved. Do not proceed with deployment until you have confirmed GPU quota availability.

Step 2: Authenticate with Your Cloud Provider

Open your terminal and authenticate with Azure CLI:

Terminal
# Log in to Azure
az login

# If you have multiple subscriptions, set the correct one
az account list --output table
az account set --subscription "Your Subscription Name"

# Verify your subscription
az account show

Verify you are authenticated with the correct account before proceeding.

Step 3: Run the Deployment

Extract the deployment package you received from BackPro and navigate to the directory in your terminal.

Option A: Interactive Deployment

The simplest method — the script will prompt you for all required information:

Terminal
# Make the script executable (first time only)
chmod +x deploy-azure.sh

# Run the deployment
./deploy-azure.sh

You will be prompted to enter:

  • Application name — A unique name (3-24 lowercase alphanumeric characters)
  • Azure region — Select from the supported regions
  • Container registry credentials — Username and password from BackPro
  • Database password — Create a secure password (min 8 characters)
  • Licence key — The JWT token from BackPro

Option B: Configuration File Deployment

For repeatable deployments or automation, use a configuration file:

Terminal
# Copy the example parameters file
cp parameters.example.json parameters.json

# Edit the file with your values
# IMPORTANT: Never commit this file to version control
parameters.json
{
  "parameters": {
    "appName": {
      "value": "yourcompanybackpro"
    },
    "location": {
      "value": "australiaeast"
    },
    "acrRegistry": {
      "value": "backprocontainerregistry.azurecr.io"
    },
    "acrUsername": {
      "value": "YOUR_USERNAME_FROM_BACKPRO"
    },
    "acrPassword": {
      "value": "YOUR_PASSWORD_FROM_BACKPRO"
    },
    "databasePassword": {
      "value": "YourSecurePassword123"
    },
    "licenseKey": {
      "value": "eyJhbGciOiJS..."
    }
  }
}
Terminal
./deploy-azure.sh --params-file parameters.json

Deployment Progress

The deployment script will display progress as it provisions resources.

The process typically takes 25-35 minutes and includes:

  1. Validating prerequisites and parameters
  2. Creating the resource group
  3. Provisioning PostgreSQL database
  4. Provisioning Redis cache
  5. Creating storage account
  6. Deploying container applications
  7. Running health checks

Do not close your terminal or interrupt the script during deployment.

Step 4: Verify the Deployment

Upon successful completion, the script will display your deployment details including the Backend API URL. Verify the deployment is working:

Terminal
# Test the health endpoint (replace with your actual URL)
curl https://yourapp-backend.azurecontainerapps.io/ping

# Expected response:
# {"status":"ok","message":"Server is running"}

# Access API documentation
open https://yourapp-backend.azurecontainerapps.io/docs

Post-Deployment

Accessing Your Resources

All deployed resources can be viewed and managed in the Azure Portal under the resource group created during deployment (typically yourappname-rg).

Viewing Logs

Terminal
az containerapp logs show \
  --name yourappname-backend \
  --resource-group yourappname-rg \
  --follow

Automatic Updates

BackPro AI includes an automatic update system. When we release new versions, your deployment will automatically update within 24 hours. No action is required on your part.

Estimated Cloud Costs

The following are approximate monthly costs for running BackPro AI (prices may vary by region and your agreement):

ResourceSpecificationEst. Monthly Cost (USD)
Container Apps (GPU)NVIDIA T4, 8 cores$800 - $1,200
PostgreSQLFlexible Server, 2 vCores$80 - $150
Redis CacheBasic tier$20 - $50
Storage AccountStandard LRS$5 - $20
Total Estimated Monthly Cost$905 - $1,420

Actual costs depend on usage patterns, data transfer, and your cloud pricing agreement. We recommend setting up cost alerts to monitor spending.

Troubleshooting

Common Issues

GPU quota not available:

Ensure you have requested and received approval for GPU quota in your target region. Check the status in your cloud provider's console.

Deployment times out:

Some regions may experience delays during resource provisioning. If the deployment times out, check your cloud console to see the status of resources. You may need to delete the resources and retry.

Container fails to start:

Verify your container registry credentials are correct. Check the container logs using the commands in the Viewing Logs section.

Health check fails:

The backend may take a few minutes to fully initialise after deployment. Wait 5-10 minutes and try again. If issues persist, check the container logs for errors.

Destroying the Deployment

If you need to remove the deployment, use the destroy command:

Terminal
# Destroy all resources
./deploy-azure.sh --destroy

# Or manually delete the resource group
az group delete --name yourappname-rg --yes --no-wait

Warning: This will permanently delete all resources including databases and storage. Make sure to backup any important data before destroying.

Getting Support

If you encounter issues not covered in this documentation, our team is here to help:

For urgent deployment issues, please include your application name, cloud provider, region, and any error messages when contacting support.

Was this page helpful?

Your feedback helps us improve our documentation.

Send feedback

MEK AI

BackPro AI Strategic Consultant

MEK AI Logo

BackPro AI

Ask MEK a question about us