Points & Plans

Every Ghayma plan gives you a points budget to spend across the platform’s services. This page explains what points are, how they behave, and what happens when you reach your budget. It is a concept guide — for the exact cost of any individual service, and for live prices, check your dashboard.

A plan is a budget, not a bundle

A plan doesn’t hand you a fixed shopping list — “two apps, one database, some storage.” Instead, it grants a single points budget. Every service in the marketplace prices its footprint in points, and you spend that budget on any mix of services you want.

That flexibility matters because no two projects look alike. A mobile-app backend, for example, might need a couple of managed databases, some object storage, and an auth service — and zero web apps. With a bundle, you’d pay for app hosting you never use. With a points budget, you spend the whole thing on the databases, storage, and auth that your backend actually needs.

The same plan ladder therefore serves every shape of workload. You pick the plan whose budget covers your footprint, then decide for yourself how to divide it up.

How points work

Points are an allowance, not a meter. They measure the maximum concurrent footprint your project is allowed to hold — not something that ticks down over time.

The rules are simple:

• Creating a resource reserves its cost against your budget.
• Deleting a resource refunds its cost back to your budget.
• Resizing a resource reserves or refunds only the difference — grow a database’s disk and you reserve the extra; move an app to a smaller tier and the difference comes back.

Points don’t decrease on their own. There is no hourly charge against your budget. The only rule the platform enforces is:

sum of your active resource costs  ≤  your plan budget

As long as that holds, everything you’ve created keeps running. Free up a resource and those points are immediately available to spend on something else.

What costs points (and what doesn’t)

Not everything on the platform draws from your points budget. Points price the resources that hold real capacity — reserved CPU and memory, held disk, held user capacity. Things that are shaped like flow (traffic) are metered separately, and a few operational limits are plain per-plan caps.

Custom domains, deployments per day, and environment variables have fixed per-plan limits — they’re guardrails against abuse, not products you buy with points. Bandwidth is metered against your plan’s separate bandwidth allowance.

That allowance is counted per project: the bandwidth and compute usage of every site in the project — the main site and any additional sites you’ve added — is summed into the project’s usage.

The points meter

You can always see where your budget stands:

• In the dashboard — your project overview shows a points meter (used out of your plan budget) with a per-resource breakdown.
• From the CLI — run ghayma points to print the same used-versus-budget summary and breakdown for the current project.

The breakdown lists what each resource is reserving, so you can see at a glance which app, database, bucket, or auth service is holding which share of your budget — handy when you need to free points and want to know where to look.

One line you may notice is an app marked untiered (pending next deploy). An app adopts its compute tier — and therefore its points cost — on its next deploy. Until you deploy it, it shows as untiered. Run a deploy and it settles onto its tier, and the meter updates to reflect it.

When you run out of points

If a create or resize would push you past your plan budget, the platform rejects it and tells you the shortfall. You have three ways forward:

1. Upgrade your plan. A larger plan means a larger budget. The upgrade takes effect immediately, and you pay only the price difference for the days left in your current month or year — the dashboard shows the exact amount before you confirm.
2. Free up points. Delete a resource you no longer need, or downsize one that’s larger than it has to be. Every deletion refunds its full cost and every downsize refunds the difference, so the points come back right away for you to reuse.
3. Switch to pay-as-you-go. Graduating to pay-as-you-go lifts the points budget entirely — instead of a fixed allowance, you’re metered on what you actually use.

Over-budget states

Because points are checked only when you create or resize something, your own actions can never leave you over budget — a request that wouldn’t fit is simply rejected before anything is created.

The one thing that can put a project over budget is a platform-side price change (repricing). Even then:

• Nothing running is ever touched. Points are enforced only at creation and resize time. Existing apps, databases, storage, and auth keep running exactly as before — the platform never throttles, freezes, or deletes a running resource to reclaim points.
• New creates pause. While you’re over budget, new creates and resize-ups are held back until your footprint fits again — either because you freed some points or because you upgraded to a bigger plan.

Downgrading follows the same principle, on a delay. A downgrade takes effect at the start of your next billing period — you keep your current plan and its full budget until then, and there is no refund for the part of the period you’ve already paid. If you pick a plan whose budget is smaller than your current footprint, the dashboard warns you before you confirm. If you go ahead anyway, your existing apps, databases, storage, and auth keep running untouched — but from the moment the smaller plan starts, and until your footprint fits its budget, new creates and resize-ups are held back, exactly as after a repricing. To lift that hold, free some points (remove or downsize resources) or upgrade back.