Save a stack
Keep a planned stack in your organization and see when its plans change.
A saved stack keeps the plans the planner chose for your request, in your organization's console, and tells you when something happens to them.
Save a stack
- Plan a stack on clearvia.app/plan.
- Select Save to Clearvia. Sign in if asked; the plan comes with you.
- Check the plans and the request, name the stack and select Save stack.
The console runs the planner on the request again when it saves, so a stack always records what Clearvia recommended. You can also save the plans a repository check finds, to follow the services a project already uses.
Read a stack's health
- Up to date: nothing has happened to its plans since they were chosen.
- Changed: a chosen plan changed, Clearvia corrected its record, or one of its facts is under review. The changes stay listed on the stack until someone marks them as seen.
- Needs attention: a chosen plan is being retired or was removed, changed in a way that can cost money, lose data or stop the project, or no longer holds the usage you planned for.
Expected usage
When you planned with expected usage (users, requests, data, emails, tokens), each plan shows how much of its free limit that usage takes, such as "22% of free emails · 2,000 of 9,000 a month". The figure is measured against the plan as the catalog shows it now. If a provider cuts a free limit below your usage, the stack needs attention even though nothing about the stack changed. Re-plan to see what fits.
To change the figures as your project grows, select Edit expected usage under the stack's request. The plans stay as they are and are measured against the new figures at once; Re-plan then chooses for them.
Re-plan
Select Re-plan to see what the planner chooses for the same request today. Nothing changes until you select Use the new plans. If the planner's choice moves while you review it, you see the latest choice before anything is saved.
Notifications
When a new version of the catalog changes a stack's plans, the stack's author and the organization's owners and admins get a notification in the console. If the change pushes the stack's expected usage over a plan's free limit, the notification says that first. Turn it off under Account settings → Notifications. Stacks do not send email yet.
From a coding agent
With an API key, a coding agent can read the organization's stacks through the MCP server or the REST API, and save the stacks it plans. Saving from an agent works like saving in the console: the planner chooses the plans.
Who can do what
Every member of the organization reads and saves stacks. The stack's author and the organization's owners and admins rename, edit the expected usage, re-plan, mark changes as seen and delete. An organization keeps up to 50 stacks.