Billing Management¶
Manifest Platform provides built-in billing management so admins can monitor usage, control costs, and manage subscriptions without leaving the platform. The billing dashboard gives real-time visibility into consumption across compute, AI model inference, storage, and data transfer.
Subscription Management¶
Plans¶
Manifest Platform offers three subscription tiers:
| Tier | Description |
|---|---|
| Experiment | Get started with the platform and explore its capabilities |
| Build | Build and deploy production solutions with expanded limits |
| Scale | Enterprise-grade capacity with custom allocations |
Each tier includes a set of platform features and usage allocations. Features and limits vary by tier — view your current plan details under Admin > Settings > Subscriptions.
Viewing Your Subscription¶
Navigate to Admin > Settings > Subscriptions to see your current plan, status, billing cycle, and renewal details.
Subscription Fields¶
| Field | Description |
|---|---|
product_name |
Name of the subscription plan or product |
status |
One of: active, trial, suspended, cancelled, expired |
billing_cycle |
One of: monthly, annual, custom |
start_date |
When the subscription began |
end_date |
When the subscription ends (null for open-ended) |
trial_end_date |
When the trial period ends (null if not in trial) |
auto_renew |
Whether the subscription renews automatically at period end |
quantity |
Number of seats or units covered |
Changing Plans¶
Contact your Customer Success Manager (CSM) to upgrade or adjust your subscription plan.
Credit Balance¶
Manifest Platform uses a credit-based billing model. Credits are purchased in advance and consumed as you use platform services. The credit balance tracks what has been purchased, consumed, and what remains.
Credit Balance Fields¶
| Field | Description |
|---|---|
total_credits_purchased |
Cumulative credits purchased across all time |
credits_consumed |
Credits used to date |
credits_remaining |
Available credits (purchased - consumed) |
budget_credits |
Optional cap on credits that can be consumed (acts as a budget ceiling) |
contract_end_date |
When the current contract period ends |
low_balance_threshold |
Credit level at which a low-balance alert fires |
alert_enabled |
Whether low-balance alerts are active |
alert_recipients |
List of email addresses that receive credit alerts |
View your current balance on the Admin > Billing dashboard.
Burn Rate¶
The billing dashboard projects how long your remaining credits will last based on recent consumption.
| Metric | Description |
|---|---|
| Daily burn rate | Average credits consumed per day over the recent period |
| Monthly burn rate | Projected monthly consumption at the current burn rate |
| Days remaining | Estimated days until credits are depleted at the current burn rate |
| Projected depletion date | Estimated date credits will run out |
| Service breakdown | Credits consumed per service type (compute, AI gateway, storage, etc.) |
This data is displayed on the Admin > Billing dashboard alongside the burndown chart.
Usage Monitoring¶
The billing dashboard provides real-time and historical consumption data across all billable dimensions.
Usage Categories¶
| Category | Unit | What It Measures |
|---|---|---|
| Compute | vCPU-hours | Hosted service and code block execution time |
| AI Gateway | Tokens | Input + output tokens processed through the AI Gateway |
| Storage | GB-months | Datasets, artifacts, and audit log storage |
| Data Transfer | GB | Outbound data transfer from the platform |
| Deployments | Count | Number of deployment operations per billing cycle |
| Connector Calls | Count | API calls made through managed connector instances |
Viewing Usage¶
Navigate to Admin > Billing to see:
- Burndown chart -- Credit consumption trend over time
- Service breakdown -- Pie chart showing consumption by service type
- Workspace breakdown -- Consumption by workspace
- User consumption -- Per-user credit usage table
- Period selector -- Toggle between 7d, 30d, 90d, or all-time views
Credit Transactions¶
Every credit deduction is recorded as an immutable ledger entry. Each transaction includes:
| Field | Description |
|---|---|
service_type |
Which service consumed the credits (e.g., ai_gateway, compute) |
usage_quantity |
Amount of the service unit consumed |
usage_unit |
Unit of measure: tokens, hours, GB, executions, or calls |
rate_applied |
Credits-per-unit rate used for this transaction |
credits_debited |
Total credits deducted |
balance_before / balance_after |
Credit balance snapshot before and after the transaction |
workspace_id |
Which workspace the usage was attributed to |
resource_type / resource_id |
The specific resource that triggered consumption |
timestamp |
When the usage occurred |
Credit Alerts¶
Credit alerts notify your team when balance or burn rate conditions are met.
Alert Types¶
| Alert Type | Trigger | Severity |
|---|---|---|
low_balance |
Credits remaining falls below low_balance_threshold |
warning or critical |
high_burn_rate |
Daily burn rate exceeds a configured limit | warning |
projected_depletion |
Credits are projected to run out before the contract end date | warning or critical |
anomaly |
Unusual spike in consumption detected | info or warning |
Alert Display¶
Active alerts are displayed on the Admin > Billing dashboard with severity-based styling:
- Healthy (green) -- Balance is above threshold
- Low Balance (orange) -- Balance has dropped below the configured threshold
- Critical (red) -- Balance is less than 50% of the threshold
- Overdrawn (red) -- Balance is negative
Alert recipients are shown on the dashboard.
Rate Cards¶
Rate cards define how usage is priced in credits. Rate cards are dynamic and managed in the platform. Each organization is assigned an active rate card as part of their subscription.
Pricing Models¶
| Model | Description |
|---|---|
flat_rate |
Fixed credits per unit (e.g., 10 credits per GB) |
passthrough_plus_markup |
Passes through the provider's cost and adds a markup percentage |
tiered |
Different rates apply at different usage volumes |
formula |
Custom pricing formula |
The rate applied to each transaction is recorded in the transaction record, so you can always see exactly how a charge was calculated.
Budget Controls¶
Organizations can configure a budget_credits cap to track total credit consumption against a defined budget. When combined with alert thresholds, this provides visibility into spending relative to your allocation.
Budget and contract details are visible on the Admin > Billing dashboard.