Service limits and fair use
What each plan includes, how usage is counted, and what happens when you reach a limit.
Every limit in Trellis is tied to a level of the hierarchy: a client workspace, a group inside it, a project, a seat, or a guest. Knowing which level a limit applies to explains almost every question about what your plan includes.
How usage is counted
A company account holds client workspaces. Each workspace holds groups, each group holds projects, and each project holds tasks. Workspace and group allowances are counted per workspace, so three groups on Studio means three groups in each of your workspaces rather than three across the account. Project allowances on the Free plan are counted across the whole account.
What each plan includes
Free covers one workspace, one group, three projects, two internal seats, two client guests, and no automations. Studio raises this to three workspaces, three groups per workspace, unlimited projects, unlimited seats, unlimited free guests, and five active automations per workspace. Agency allows ten workspaces, ten groups per workspace, and twenty-five automations per workspace. Scale removes the numeric caps entirely.
Reaching a limit
Limits are enforced on the server, not just in the interface, so the result is the same however you reach them. When you try to create something beyond your allowance the request is refused, the interface names the limit you have hit, and it offers the plan that lifts it. Nothing you already have is altered, and no work in progress is lost.
Changing or downgrading a plan
Moving to a lower plan never deletes anything. If you end up above the new allowance, everything you already created stays readable and editable, and only new items beyond the limit are blocked until you either upgrade again or bring your usage under the cap yourself. Trellis will not remove a workspace, group, or project on your behalf.
Seats and client guests
Internal seats are the people on your team who sign in and do the work. Client guests are the people you invite to review and approve, and they are counted separately, so inviting a client never consumes a team seat. From Studio upward, guests are unlimited and free, and their access is scoped to only the projects you share with them.
Fair use
The published allowances are the operating limits, and they are what the product enforces. If your delivery model needs something outside them, such as an unusually large migration or a short burst of extra workspaces during onboarding, contact support before you start rather than working around the limit.
Worth remembering
- Workspace and group allowances are per workspace. Free plan project allowances are per account.
- A blocked action means the limit was reached, not that anything was removed.
- Client guests never consume an internal seat.
- Downgrading is non-destructive. Existing work stays, new work beyond the cap is paused.
Common questions
A workspace is a board at the top of the hierarchy, normally one per client. Groups, projects, and tasks all live inside it.
Nothing is deleted. Anything above the new allowance stays readable and editable, and only new items beyond the limit are blocked.
No. Guests are counted separately from internal seats, and from Studio upward they are unlimited and free.
On the server. The interface explains the limit, but the rule is applied behind it, so the outcome is consistent.
Related guides
Ready to apply this?
Bring a real project into Trellis with guided onboarding, or ask us anything about your setup.