Manage Project Resources
The project management page shows current usage and remaining quota for each resource. Purchase a resource pack when a single quota runs low, upgrade the plan for more product capabilities, or use a Dedicated instance for isolated computing resources.
View resource usage
- In the User Center, find the project and select Manage.
- Review the used and remaining amount for each resource.
Resource quotas and purchased packs belong to the current project. Confirm that you opened the intended project before making changes.
View usage details
Select Details on a resource card to see where that resource’s quota came from and what consumed it.
| Resource | What the details show |
|---|---|
| AI points | Time, feature, model, and points spent for each run |
| Automated Actionflow runs | Time, flow name, and trigger for each run |
| Outbound data transfer | Transfer per asset path for a chosen day, and the individual requests beneath a path |
| Database storage | Current size and share of each table |
| Object storage | Current size of app assets and of static site deployments |
RPS keeps no per-event record, so only its total is available.
Details open in tabs. Sources lists where the quota came from — the plan, resource packs, and so on — with the validity period of each. Usage records or Composition lists the individual events or the current breakdown.
How far the details reach
- Metered resources (AI points, automated Actionflow runs) and outbound data transfer reach back at most 30 days. Earlier periods show totals only, and the page states the date the records start from.
- Storage resources (database storage, object storage) show the current composition. Storage has no history.
- Outbound data transfer for the most recent days is still arriving and can still change. The page marks the date after which figures are not yet settled.
Details are unavailable when the project has not been published and no runtime holds its records, when the project has no runtime credential, or when the resource keeps no per-event record.
If a project has more than one live deployment, the details cover one deployment only and will not add up to the chart.
Reading the records
- Automated Actionflow runs: each row shows the flow’s current name. Renaming keeps no history, and deleted flows appear as their original identifier.
- Database storage: rows are listed per table, and each size includes that table’s own indexes and TOAST. Usage-record tables exist to bill the project and are not billed as storage. Time-series tables keep their rows in chunks outside the project schema, which are also not counted.
- Object storage: totals are grouped as app assets and static site deployments; individual files are not listed. Use the Resource Manager to trace and remove specific files.
- Outbound data transfer: each day lists only the paths that used the most transfer. The rest are folded into “Other”.
These details belong to the current project. Details in the account menu is a different record: it tracks the Copilot AI Points balance on your account.
Choose how to add capacity
| Project need | What to do |
|---|---|
| One resource is running low, but the current plan still provides the capabilities you need | Purchase a resource pack for that resource |
| You also need more product capabilities or higher baseline quotas | Upgrade the project plan |
| The shared server does not provide enough concurrency, or the project needs an isolated runtime environment | Purchase a Dedicated instance and complete the server migration |
Purchase resource packs
- On the project management page, find the resource that needs more capacity.
- Select the + beside the resource, choose a pack, and complete payment.
- Return to project management and confirm that the available quota has increased.
You can purchase any number of resource packs. Packs for the same resource add to the quota of the current project.
Understand resource limits
| Resource | What counts toward usage | What happens at the limit |
|---|---|---|
| RPS | Requests processed by the project each second | Requests may be delayed or fail |
| Database storage | Tables, records, and indexes | New data cannot be written |
| Object storage | Images, videos, and files uploaded to the project | New files cannot be uploaded |
| Outbound data transfer | Page assets, media, and files sent from the server to user devices | Affected content may not load |
| AI points | AI Agents, vectorization, and vector search in the published app, plus any points transferred to Copilot for building | The affected AI features stop running |
| Concurrent AI conversations | AI Agent conversations running at the same time in the project | Free and trial projects run one at a time and further conversations fail immediately; paid plans are unlimited |
| Automated Actionflow runs | Actionflows started by schedules and database triggers | Automatically triggered Actionflows stop running |
Quotas vary by plan. See Momen Pricing for current amounts.
Additional notes:
- AI points: Pay for AI features inside your published app. They are separate from Copilot AI Points, the account balance that pays for building with AI Copilot. The manual transfer below is the only way project AI points are spent on building.
- Outbound data transfer: Resets at the start of each billing cycle rather than on the 1st. The quota that comes with the project plan follows the plan’s expiry date; the quota that comes with a dedicated computing power kit follows the kit’s own start date. Unused quota does not roll over.
- Database storage: Updates and deletions can leave old row versions occupying space temporarily. Momen reclaims that space automatically.
- Object storage: Deleting a database record does not delete a referenced file. Use the Resource Manager to trace references and remove unused files.
Transfer project AI points to Copilot
Building with AI Copilot normally spends Copilot AI Points from your account. When that balance runs out, you can transfer a project’s AI points to Copilot and keep building that project.
Select Transfer on the AI points resource card on the project management page, then enter an amount in the dialog. Only the project owner can transfer; for everyone else the button is disabled.
How transferred points work:
- A transfer only happens when you click it. AI Copilot never takes project points on its own.
- Transferred points leave the project’s AI points pool immediately, so the project resource shows the reduction right away.
- They can only be spent building the project they came from, not any other project.
- Your account balance is always spent first; transferred points are used once it is empty.
- Each transfer has a minimum amount, shown in the dialog. The dialog also lists what the project has available to transfer and how much of the transferred amount is still unspent.
- Nothing is held back for the app: transferring the project’s whole balance leaves its own AI features — AI Agents, vectorization, vector search — with nothing to run on until you add more.
A transfer cannot be undone: the points cannot be returned to the project pool. They expire together with the project AI points they came from, and anything still unspent at expiry is lost. Transfer in the amounts you actually need.
Transfers and the runs that spend them both appear in Details in the account menu, labeled Transferred from project and Copilot run (transferred points).