Skip to content

Usage & Cost

AppMecca meters what each app consumes so you can see where your resource usage goes. mecca usage surfaces that data.

Cost Summary

mecca usage summary myapp

This aggregates an app's usage into cost categories:

  • Builds — number of builds and total build minutes
  • Runtime — per-service container runtime, measured in GB-hours (memory × hours running)
  • Backups — number of backup bundles and their total size
Billing Summary: myapp (dev)

  Builds     12 builds, 34 min — $0.41
  Runtime
             Service   Duration   Memory   GB-hours   Cost
             web         168h 0m   256 MB       42.0   $0.76
             worker      168h 0m   128 MB       21.0   $0.38
             Total                                     $1.14
  Active     2 container(s)
  Backups    5 backups, 84 MB — $0.02

Narrow the window with --since (an ISO date):

mecca usage summary myapp --since 2026-07-01

A cost of N/A means no rate is configured for that category on the environment yet — the usage is still measured, it just isn't priced. Rates are set by your platform operator.

Raw Records and Reports

# Individual usage records for an app (optionally filtered)
mecca usage show myapp --type container_runtime --since 2026-07-01

# An environment-wide report across every app you can see
mecca usage report --since 2026-07-01

--since takes an ISO date (2026-07-01) on all three commands — not a relative window like 7d. mecca usage report takes no app name; the other two require one.

All three accept the global --json flag for machine-readable output.

What's Metered

Category Basis
Build minutes How long each build ran in the AppMecca build service
Container runtime Per-service GB-hours (memory limit × time running)
Backup storage Size of stored backup bundles
Drive storage Sampled periodically per app + branch

Metering runs automatically — there's nothing to enable.

Function services are not metered yet

A service that runs as a function (runtime: function) writes no runtime record, so its compute is missing from every total on this page. It is never shown as $0.00: the dashboard's Usage page lists it under Not metered, and the --json output of these commands carries it as not_metered_services. The table output does not mention it. See Function Services.

Runtime cost follows your declared memory limit, not actual usage

GB-hours are computed from resources.memory (or the platform default when you declare none), so an over-generous limit costs you even when the container is idle. See Configuration: Services.

Billing is not invoicing yet

These figures are usage metering and cost estimates derived from the environment's configured rates. Full billing and invoicing is not part of the platform yet — use mecca usage summary to understand consumption, not as a statement of account.

Next Steps