Billing & Pricing

Choose Free on shared infrastructure or a paid managed tier: Standard, Performance, or Enterprise. Paid deployments start with three dedicated nodes. Monthly pricing covers compute, storage, operations, and tier features. Data transfer is additional and billed on actual usage.

Managed Tiers

Starting prices use us-east-1 on AWS and us-central1 on GCP. They cover the default configuration and exclude data transfer. GCP Performance has different compute and storage defaults, so its starting price is higher. Region, capacity, and agreed terms can change the price.

The pricing page and public pricing API show current prices. Use an estimate for your selected configuration before you create a deployment.

Enterprise requires account approval and direct contact. Business support, SLAs, and other custom services are agreed separately. The advertised price does not include those services.

Paid tiers include encryption in transit and at rest, provisioning, upgrades, and monitoring. They have no broker throughput limit. Partitions are dynamic, with no upfront count or per-partition charge.

What You Pay For

Compute plus Storage is the monthly configuration price. It remains payable while the deployment is active, even without traffic. Network is zero when there is no billable transfer. Larger compute or storage can increase monthly pricing. A smaller configuration does not reduce the price below the tier's starting amount.

The throughput input estimates traffic and helps select suitable compute. It does not reserve transfer or require payment for unused throughput. With the same compute and storage, changing throughput changes only the transfer estimate. If the workload requires larger compute, the additional resources increase monthly pricing.

Estimates assume 30 days of steady traffic at the selected rate in each direction. For AWS Standard at 0.1 MB/s in and out, the estimate is $199 per month plus about $15.55 for transfer. The estimated total is $214.55. Billing uses actual transfer instead of the estimate.

Same-region transfer uses graduated rates: each price applies only to the volume within its band. Cross-region and cross-cloud traffic use separate rates. Multi AZ adds a charge for measured cross-zone transfer. Telemetry retention is included in the tier.

Partial Months and Changes

Billing follows UTC calendar months. Proration means charging for the active part of a month. The platform calculates that time by the second, from activation until billing ends.

If a tier or resource upgrade takes effect during the month, each configuration is charged for its active period. Failed upgrades do not activate the proposed pricing. Reports follow recorded resources and their effective times.

A deployment keeps the pricing version and commercial terms recorded for it. Publishing new rates does not change those terms automatically. Agreed terms can override published rates. Ordinary upgrades do not lower the existing monthly configuration price.

An estimate or preview is not an invoice. Invoices use active time, measured transfer, and applicable credits.

BYOC and On-Premise

BYOC platform pricing starts from $1,999 per month. You pay AWS or GCP directly for infrastructure. LaserData adds charges for provisioned vCPU-hours, the allocated processor capacity multiplied by its active time.

The public catalog reports the monthly starting amount. The BYOC estimator accepts vcpus_per_node and includes provisioned capacity in its total. Arrange capacity and commercial terms through sales.

On-Premise pricing requires an agreement with LaserData. See BYOC and On-Premise for deployment requirements.

Account Plans

A managed tier applies to one deployment. An account plan controls organization limits and access to features. The tenant response reports the plan as basic, pro, enterprise, or custom.

Plans limit members, divisions, environments, roles, audit retention, and deployment counts by compute size. They also control access to BYOC, private networking, Multi AZ, and dedicated infrastructure. New organizations start on Pro.

Selecting Enterprise for a deployment does not change the account plan. Enterprise also requires an approved Enterprise or Custom account plan. Contact LaserData to arrange that access.

Spend Limits

A spend limit is a monitoring threshold in USD. The status is ok below 80 percent, warning from 80 percent, critical from 90 percent, and exceeded at 100 percent. No limit, or a nonpositive limit, reports ok.

This threshold does not stop billing or shut down the deployment. Set it during creation or through Update Spend Limit.

Usage Reports

The tenant's Billing page contains deployment reports and invoices. Each deployment has a monthly report. Report details include compute_cost, storage_cost, network_cost, and total_cost.

Managed reports also provide monthly_base_charge for the configuration and network_usage_cost for transfer. These describe charges before negotiated adjustments. The configuration amount includes prorated reserved resources and any billable additional capacity. Do not add these explanatory amounts to the report total again.

Current-month reports show usage to date. Previous-month reports can change while provider data arrives and reconciles. Invoicing waits when reconciliation or settlement checks remain unresolved. Preserve monetary values as decimal strings in API integrations.

Invoices

Invoices group deployment charges for a billing period. Automatically generated numbers follow INV-{MM}-{YYYY}-{tenant_id}. Payment is due 14 days after generation.

Customer APIs expose approved, paid, failed, refunded, and partially_refunded invoices. These invoices support PDF downloads. Draft, pending, and cancelled invoices are not visible through customer APIs.

Payments and Credits

Add a payment method through the Console's Stripe setup flow. Paid creation and upgrades require valid payment information for the billing account. A linked marketplace payment provider can meet this requirement.

AWS Marketplace and Google Cloud Marketplace subscribers can link an agreement to a tenant. The marketplace handles billing for that agreement's scope. Direct payment charges and retries follow the configured payment policy.

Redeem a promo code through POST /tenants/{tenant_id}/billing/promo_codes. A tenant can redeem each code once. Its credit reduces later invoices until used or expired. Credits are consumed oldest first. A credit never takes an invoice below zero: an invoice fully covered by credits is marked paid, the invoice shows the applied amount on a Credits line, and the unused balance carries to the next invoice. List balances through GET /tenants/{tenant_id}/billing/credits.

Promo codes do not apply to marketplace-billed tenants. Existing credits do not change metered usage or the deployment report amounts.

API Reference

The Billing API provides rates, estimates, billing details, reports, invoices, payment methods, and credits. Public pricing endpoints do not require authentication. Tenant billing reads require billing:read, and changes require billing:manage.