Skip to main content
A visible capability is not necessarily runnable, and a plan entitlement does not guarantee that a provider will return data. Alesta evaluates several boundaries before it can show a result or start an action.

The availability stack

1

Plan entitlement

The workspace plan must include the panel or action. A lock and upgrade prompt indicate a plan boundary.
2

Member role

Some administration actions require the workspace Owner. Other workspace work may be available to both Owner and Admin roles.
3

Connection and selection

Provider-backed measurements may require authorization and a selected account, property, organization, or repository.
4

Service readiness

The Alesta service and third-party provider must support the requested operation in the current environment.
5

Source coverage

The source must have usable data for the domain and requested window.
6

Credits and target lock

Eligible paid actions require remaining capacity, and only one action can run on the same protected target at a time.

Plan boundaries

Includes one zero-rated domain-first profiling run for an eligible workspace. It provides the bounded public baseline and free documents available to that run. New chat turns, Signals, deeper Web areas, Social measurement, and model-backed corrections can be plan-locked.
See Pricing and Billing for the current plan catalog.

Common states and responses

Plan access, provider support, and data coverage answer different questions. A successful upgrade can unlock a run while the final panel still reports unavailable source data.

References