Deploy from Container Registry
This guide walks you through the process of deploying an application from a container registry to Grid.
1Step 1: Select a Cloud Provider
At the top of the "Deploy Application" screen:
Choose your target cloud environment:

This determines where your application will be deployed once built and configured.
📢 Important Payment Information
Each cloud provider implements a unique payment methodology. Akash uses a per-second billing model, while Flux follows a prepaid approach. For comprehensive details on payment requirements and processes, please refer to the Payment Information section.
2Step 2: Configure Application
- Choose Container registry as the source.
Configure the following:
🔧Container Image Settings
- Service name: Unique name for your service.
- Docker image (e.g., gridcloud/hello-app:2.0)
Choose between:
- Public: No authentication needed.
- Private: Requires registry credentials.
If using a private image:
- Select registry provider (DockerHub, GitHub, etc.)
- Enter username and personal access token.
💻Instance Settings
Configure your runtime environment:
- Number of instances
- CPU, RAM, and SSD allocations
You can either:
- Use recommended configuration, or
- Customize manually.
3Step 3: Add Environment Variables (Optional)
Each component supports custom environment variables.
- Scroll to the Environment Variables section.
- Add key-value pairs as needed.
- Values are masked for security and only available to the specific component.
4Step 4: Networking Settings (Optional)
You can expose ports for your service using the Networking section:
- Choose the protocol (HTTP or TCP)
- Select the port
- Optionally assign a virtual host for routing
Each rule added appears in the list and can be edited or removed.
5Step 5: Payments
Before your deployment goes live, you'll need to handle payments based on your selected cloud provider:
Akash: Per-Second Billing
With Akash, you'll be charged on a per-second basis. Credits are continuously deducted from your account based on resource usage.
- Pay only for what you use
- No upfront commitment
- Unused credits are refundable if deployment is cancelled
Flux: Prepaid Model
With Flux, you'll pay upfront for the total cost of resources for a specified duration (minimum 1 week).
- Clear upfront costs
- Duration-based pricing
- Simplified billing process
For more detailed information about payment options, visit the Payments documentation.