Points

Show a project’s points meter and a per-resource breakdown of where its points are reserved. Every database, app, storage bucket, and auth app reserves points based on its tier and size — ghayma points is how you read the total and the itemised list from the terminal.

Point values come from the live catalog (GET /api/v1/marketplace/catalog) and can change; the numbers on this page were read on 2026-09-24.

For the concepts behind points — budgets, reserve and refund, and what happens at your limit — see Points & Plans. For the exact per-service formulas, see Pricing by Service.

ghayma points

Show the current project’s meter and breakdown. Reads project_id from .ghayma.json, so run it from a project directory (or after ghayma init).

ghayma points

Output:

Points: 17/20 used · 3 remaining

KIND     NAME         DETAIL                          PTS
app      main         tier a × 2 replicas             6
db       my-postgres  tier xs · 5 GB · daily backup   8
storage  my-assets    10 GB quota                     1
auth     my-app-auth  1k users · 2FA                  2
db       fresh-db     untiered (pending next deploy)  0

This is a Starter project (20 points): app 3 × 2 = 6, database 2 (tier) + 5 (disk) + 1 (daily backups) = 8, bucket 1, auth 1 + 1 (2FA) = 2 — 17 in all.

The first line is the meter — used/budget · remaining. Below it, one row per resource shows its KIND, NAME, a DETAIL summary of how it’s sized, and the PTS it reserves. A resource that has been created but not yet rolled out shows untiered (pending next deploy) and reserves nothing until its next deploy sizes it.

Meter states

The meter adapts to how the project is billed and where it sits against its budget:

• Within budget — the standard Points: used/budget · remaining line above.
• Over budget — an extra ⚠️ over budget by N line appears under the meter. Once enforcement is active, a new create or resize that wouldn’t fit your remaining points is rejected up front; existing resources keep running.
• Enforcement not active yet — a (enforcement not active yet) line means the platform is reporting overages but not yet blocking new resources.
• Pay-as-you-go — projects on PAYG show Pay-as-you-go — usage billed per resource (no points budget) instead of a meter, and the breakdown still lists each resource.

Where points come from

The DETAIL and PTS for each row are computed from your plan’s live catalog — the same figures the create and resize commands preview before you commit. To change what a resource reserves:

• Databases — ghayma db resize
• Apps — ghayma site scale
• Storage and auth apps are sized at create time (storage, auth)

Deleting a resource refunds its points; resizing reserves or refunds only the difference. See Points & Plans for the full model.