Free and paid tiers #

View this page as Markdown

tzTrack has a free tier and a paid tier, and each space follows its owner's tier. This page explains the free tier's cap on open issues, when background AI reviews run, and what happens when an owner must pay.

Pricing gives the paid tier's price. An application's own issue space is exempt: it takes no cap and no per-user price.

When the tiers apply #

The tiers apply once the introductory period ends. Until then, no space is capped, and background AI reviews run in every space that turns them on.

The cap on open issues #

On the free tier, a space holds at most 250 open issues. Every issue that is not closed counts toward the cap, including issues that are fixed or waiting.

At the cap, tzTrack refuses a request that would open a new issue, with open_issue_cap_reached. That covers recording a new finding and splitting a second point out of a report. Nothing from the refused request is stored.

Work on existing issues continues at the cap. Your AI can add reports to existing issues, comment, update, close, and reopen. Reopening an issue can take a space past the cap; tzTrack never closes, hides, or deletes an issue to meet it.

To make room, close the issues that are done.

Background AI reviews #

On the paid tier, background AI reviews run in a space that turns them on. They run on Turn Zero's allowance, within the default daily budget.

On the free tier, background AI reviews do not run, and a new issue opens ready for work instead of waiting for review. The space keeps its own setting while reviews do not run.

When an owner must pay #

An owner must pay when a space they own has a member other than themselves. Sharing a space explains members.

After the introductory period, such an owner has a 30-day payment grace. During the grace, the owner and members keep working, and the owner's spaces take the free tier's cap. Background AI reviews do not run there during the grace.

When the grace ends, tzTrack stops the owner's spaces until the owner pays or removes every member. A request to a stopped space returns tztrack_paid_required, for the owner and for members. The owner can still download the space's issues with the cache.

Nothing in a stopped space is deleted, closed, or hidden. Removing every member returns the owner to the free tier, and the spaces work again under the cap.

For AI tools #

• On a space a person owns, the REST API's read_space returns tier: introductory, paid, free, grace, or stopped.
• open_issue_cap_reached stored nothing. Keep the point in your own notes and tell your person. Close issues that are done to make room.
• tztrack_paid_required means the space's owner must pay or remove every member. Tell your person; only the owner can resolve it.

Related #

• Sharing a space: owners, members, and access levels.
• Refusals: every refusal with its cause and remedy.
• The cache: the copy of a space's issues your AI keeps.