Skip to content

Plans & pricing

AppGantry's pricing model has two ideas:

  1. You pay for the bytes you move and keep, not per seat. Teammates, reviewers, and CI bots are always free to add.
  2. Heavy-distribution customers can cap the bill at the platform fee by hosting artifacts in their own cloud account (BYOSA).

The canonical pricing table lives at appgantry.com/pricing. This page explains what each meter actually measures and how billing is posted.

Plans at a glance

Team Business Enterprise
Platform fee $5 / mo, pre-paid $100 / mo, post-paid Coming soon
Storage model Hosted (metered) Hosted or BYOSA (flat) -
Per-MB charges Yes Yes on hosted; waived under BYOSA -
Build retention default 30 days 12 months -
SSO / SAML - ✓ -
RBAC + org-wide audit feed Basic ✓ -
Support Community Standard -

Enterprise (SSO, custom region pinning, audit-feed export, SLA-backed support) is on the roadmap. Register interest.

Retention is always configurable per org in every plan. Longer windows simply cost more MB-months on hosted (and nothing on BYOSA).

The three meters (hosted storage only)

When your org is on hosted storage, three independent meters fill your invoice. All quantities are decimal MB (1 GB = 1000 MB).

Storage

  • Unit: MB-month.
  • Counts: retained artifact bytes held over the billing period.
  • Sampled: daily; averaged at month close.

Storage is a rate over time, not a one-time charge. Holding 1 GB for a full month is 1 GB-month. Holding it for 15 days is about 0.5 GB-month. Shorter retention → fewer MB-months.

Upload

  • Unit: MB.
  • Counts: new build artifact bytes successfully ingested.
  • Measured at: the upload-completion callback, against the blob's actual size.

Failed and abandoned uploads are not billed. A background reaper sweeps incomplete direct-to-blob uploads so they don't accrue storage either.

Download

  • Unit: MB.
  • Counts: bytes shipped to testers and developers: both count.
  • Measured at: the per-request log row × artifact size.

Tester downloads are the line that can surprise you on a viral build. See spend caps for how to bound it.

Billing posture

Plan Posture Behaviour
Team Pre-paid Your account holds a balance; usage draws it down. When the balance hits $0, uploads and downloads are blocked (HTTP 402) but metadata stays readable. Top up to resume.
Business Post-paid Billed in arrears against an optional hard spend cap.
Enterprise Coming soon -

BYOSA orgs are exempt from the spend-cap and 402 gates entirely. Your own cloud provider is the spend ceiling.

Worked examples

These mirror the pricing-page examples.

A. Small internal beta on Team

  • 20 builds × 100 MB uploaded: 2 GB × $0.05 = $0.10
  • ~2 GB held across the month: 2 GB-month × $0.10 = $0.20
  • 50 testers × 5 builds × 100 MB downloaded: 25 GB × $0.18 = $4.50
  • Platform fee: $5.00
  • Total ≈ $9.80 / month

B. Heavy distribution on Business (hosted)

  • 2 GB uploaded: $0.10
  • 30 GB-month held: $3.00
  • 2,000 testers × 10 builds × 150 MB downloaded: 3,000 GB × $0.18 = $540.00
  • Platform fee: $100.00
  • Total ≈ $643.10 / month: egress dominates.

B′. Same customer on Business + BYOSA

  • Platform fee: $100.00 flat. No metering.
  • Their own Azure account absorbs the 3,000 GB egress at the cloud-provider rate (~$0.087/GB ≈ $261).

See also