Knowledge Base

Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.

Plans, Limits, and Entitlements

The Truestamp plan tiers (free, starter, pro, enterprise), the per-account limits and feature entitlements each tier carries, how usage is counted and enforced, and how an administrator can augment a single account's effective limits and features.

Overview

Every Truestamp account is on a plan, and the plan sets two things: the numeric limits that cap how much you can do, and the named feature entitlements that decide which capabilities you can use at all. Plans attach to accounts, not to teams. There are four customer tiers, from lowest to highest: Free, Starter, Pro, and Enterprise.

Plans are user-centric, and two accounts’ plans can matter at once. The person who created a team is that team’s billing owner, and the billing owner’s plan governs the work done in that team, no matter which teammate does it: the monthly item allowance, the team seats, the custom metadata size and the claims-only budget a submission is checked against. If several people submit items into a team, those items all count against the one billing owner’s monthly item allowance. Item retention follows the plan of the item’s owner: for an item the team owns, that is the team’s creator; for an item a person owns (on a team where the creator retains ownership, the person who submitted it), that is the owning person. Your own plan governs what is yours alone: how many teams you may create, whether a team you create may retain ownership of its items, your outgoing webhook endpoints, your daily chat messages and knowledge-base searches, and the visibility choices in the web submission form. The form’s custom metadata fields, and the sizes it shows, follow the team creator’s plan, the plan the submission is checked against. See scope and tenancy for how the active team is chosen.

Paid billing is not turned on yet, so no plan can be bought today. Free is the default tier that every account starts on. Starter, Pro, and Enterprise are published so you can see where they land, but they are marked “Coming Soon” and their signup buttons are disabled. Free is not a trial: it is a permanent tier with real, if smaller, limits.

Separately from the tiers, an administrator can grant a specific account extra headroom, raising individual limits or adding individual features on top of its plan without moving the account to a different tier. This is how a single account gets a custom arrangement while staying on, say, the Free plan.

The plan tiers

There are four customer-facing tiers. Each carries a bundle of numeric limits and feature entitlements. Higher tiers raise the ceilings and add capabilities.

Limit or feature Free Starter Pro Enterprise
Items per month 50 750 10,000 100,000
Teams you may own (incl. personal) 1 5 20 100
Team seats across the teams you created 1 5 50 500
Custom metadata size none 1 KB 4 KB 16 KB
Claims-only submission budget 256 bytes 1 KB 4 KB 16 KB
Outgoing webhook endpoints none 5 20 100
Item retention 90 days unlimited unlimited unlimited
Chat messages per day (signed in) 25 100 500 2,000
Chat messages per day (signed out, per visitor) 10 10 10 10
Knowledge-base searches per day 500 1,500 5,000 20,000
Support Community Email Email Priority
Team-retained item ownership no yes yes yes

Notes on the table:

  • “Teams you may own” counts your always-present personal team, so Free’s ceiling of 1 means the personal team only, with no additional teams. Paid tiers let you create teams beyond the personal one.
  • “Team seats” counts every membership in every team you created, your own seats included (your personal team takes one, and each team you create takes another for you as its owner), and a person in two of your teams takes two seats. Pending invitations are not seats. On Free the personal team’s one seat is the whole allowance, so a Free account cannot add teammates.
  • The signed-out chat allowance is the same on every plan, because a visitor has no account; it is counted per visitor and per network address.
  • “Custom metadata size” is the maximum size of the freeform metadata you may attach to an item’s claims. Free allows none (basic claims only); a ceiling above zero unlocks custom metadata.
  • “Item retention” of 90 days means items whose owner is on Free expire 90 days after submission, or 90 days after the owner’s plan was downgraded to Free, whichever is later; paid tiers keep items indefinitely. The owner is the owning person for an item a person owns, and the team’s creator for an item the team owns. A newly registered account, whose billing record names no plan yet, is on Free, and its items expire on the same 90 days. See how usage is enforced below.
  • A separate internal, non-customer plan exists for system use with very high limits. It never appears in pricing and cannot be selected.

Limits versus entitlements

A plan gates you in two distinct ways.

  • Limits are numeric ceilings: items per month, teams owned, team seats across the teams the billing owner created, custom metadata size, the claims-only submission budget, outgoing webhook endpoints, item retention days, daily chat messages, and daily knowledge-base searches. Some yes/no capabilities are simply a limit being above zero. Being able to own more than your personal team means your team ceiling is greater than one; being able to attach custom metadata means your metadata ceiling is above zero; being able to configure outgoing webhooks means your webhook ceiling is above zero.
  • Feature entitlements are named capabilities a tier either includes or does not, and which cannot be reduced to a number. The two that matter today are team-retained item ownership (letting a team, rather than the item’s creator, own its items; available on the paid tiers) and the support level attached to the tier (community, email, or priority).

Which account’s plan a check reads is set per limit, as listed in the overview: a team’s work reads the team creator’s plan, and your personal allowances read yours, whichever team you have currently selected.

One further plan-differentiated behavior lives in the web submission form and follows your own plan: the private and team choices in its item visibility picker are available when your own plan is Starter or above, so items you submit through the web form on the Free plan are public (on a paid plan the form starts at team visibility). The form’s custom metadata fields, and the metadata and claims-only sizes it shows, follow the team creator’s effective limits, the ones the submission is checked against: they appear when that plan allows custom metadata, whatever your own plan.

The claims-only submission budget

When you submit an item you can either provide your own hash of the source content or let Truestamp treat the claims themselves as the content of record. In that second, claims-only mode there is a size budget on the submitted claims, measured in canonical form (JCS) and less any nonce, and that budget is a per-plan limit: 256 bytes on Free, 1 KB on Starter, 4 KB on Pro, and 16 KB on Enterprise.

The budget applies only to claims-only submissions. When you supply your own external hash, the claims byte budget is not consulted at all, so hash-first submissions are not constrained by it. Every current tier has a budget above zero, so claims-only submission is available on all tiers; the budget only bounds how large a claims-only submission may be.

How usage is counted and enforced

Limits are checked when you act, and the enforcement is deliberate about who pays.

  • Items per month is counted across every team the billing owner created, over the current calendar month in UTC. An item submitted by any teammate with write access counts toward the owner’s monthly allowance, not the teammate’s. When the count reaches the effective limit, the next submission is refused.
  • Teams owned is checked when you create a team, comparing the number of teams you already own against your ceiling.
  • Team seats are checked when an invitation is sent, against every membership in the teams the billing owner created; pending invitations are not seats. They are counted the same way again when the invitation is accepted, so an acceptance is refused, and the invitation stays pending, once the seats across the billing owner’s teams have reached the limit. The team page adds that one team’s pending invitations to the seats across the billing owner’s teams and disables its invite button once the sum reaches the limit.
  • Outgoing webhook endpoints are checked when you create one, against the endpoints you already have.
  • The claims-only budget is checked against the team billing owner’s effective limit when you submit a claims-only item, using the byte size of the submitted claims in canonical form (JCS), less any nonce.
  • Daily chat messages are counted per user over a UTC calendar day against your effective daily limit (signed-out visitors per visitor and per network address); other short-window guards also apply to keep bursts bounded.
  • Daily knowledge-base searches are counted per user over a UTC day, and only for searches that reach a search provider; a fleet-wide ceiling applies on top, and a per-minute guard bounds bursts. Exceeding the allowance answers with the same rate-limit refusal as any other limit on the API surfaces.
  • Item retention is applied in the background by a daily job. An expired item that is still waiting for its block is removed at once; an expired item that is committed or redacted is marked expired and kept for a 7-day grace period before it is permanently deleted; an item already in a block but not yet committed waits until it commits. Owners are warned by email before that happens, at 30, 15, 5 and 2 days remaining (every team owner of the team, for a team-owned item). Retention follows the effective retention limit of the item’s owner, its plan’s with any administrator override: the owning person for an item a person owns, the team’s creator for an item the team owns. An owner whose limit is unlimited keeps their items. The 30-day warning states the retention the items are kept for. The item page, its banner and the items list show the date the job uses, worked out from the owner’s retention, whoever views the item: a Pro member of a team-retains team whose creator is on Free sees the Free date for the team’s items, and a Free member of a Pro creator’s team-retains team sees none. The banner above the items list gives the retention of the items you submit to the team: the creator’s on a team-retains team, your own otherwise.

When you reach a limit, Truestamp tells you which limit you hit and how to resolve it rather than failing silently. Creating a team past your team ceiling, for example, returns an actionable message instead of a bare refusal.

Administrator overrides

An administrator can tailor a single account beyond its plan without changing the tier. Two kinds of augmentation are possible:

  • Limit overrides raise (or set) individual numeric limits for that one account. An override for a given limit replaces the plan’s value for that account only; any limit not overridden keeps its plan value.
  • Extra features grant individual named entitlements to that one account on top of whatever its plan already includes.

The account’s effective limits are its plan limits with any overrides layered on top, and its effective features are its plan features plus any granted extras. Enforcement uses these effective values, item retention included: an override of the item retention days moves when the owner’s items expire and when their warning emails go out, so a Free account given a 365-day retention keeps its items for 365 days. Overrides and extras are per-account and never change the plan tier itself; an account can carry a custom arrangement while remaining on the Free plan. An override of the custom metadata size or the claims-only budget counts only up to the Enterprise value, 16 KB: every item’s claims are capped at 20,480 bytes in canonical form on every plan, and the 16 KB bound keeps that cap from refusing claims a team’s limits allow.

Choosing a plan

  • Free suits an individual getting started: the personal team only, a modest monthly item allowance, small claims-only submissions, no custom metadata, no outgoing webhooks, and a 90-day item retention window. It is a permanent tier, not a trial.
  • Starter suits a small team that needs to collaborate: additional teams and teammates, unlimited item retention, custom metadata and larger claims-only submissions, outgoing webhooks, team-retained item ownership, and email support.
  • Pro suits a growing organization operating at higher volume: much larger monthly item allowances, more teams and members, and larger metadata and claims-only budgets.
  • Enterprise suits a large organization needing the highest volumes and ceilings, plus priority support. Enterprise pricing is arranged directly rather than listed.

Because paid tiers are marked “Coming Soon”, an account that needs more headroom today can be granted administrator overrides on the Free plan in the meantime.

Limitations

  • Plan tier applies at the account level, not per team. Switching teams never changes your own plan, but a team created by someone else is governed by that person’s plan for its items, seats and metadata, and for the retention of the items the team owns.
  • Monthly item usage is pooled per billing owner across all the teams they created, so teammates’ submissions draw down the owner’s single allowance.
  • Item retention removal applies to items whose owner has a retention limit (the owning person, or the team’s creator for a team-owned item): Free’s 90 days, or an administrator override; items whose owner is on a paid tier without one are retained indefinitely.
  • Paid billing is not turned on yet, so no plan can be bought right now. Free is the default tier every account starts on; Starter, Pro, and Enterprise are displayed as “Coming Soon” with signup disabled.
  • A downgrade can be blocked when your current configuration depends on a higher tier. In particular, an account that created teams with team-retained item ownership cannot be downgraded to a tier that lacks that entitlement. A team never leaves the team-retains model once it has chosen it, so the block clears only when those teams are deleted.