TinaCMS has one of those pricing models that looks simple until you try to answer a more practical question: when will I actually have to pay?
The answer is not necessarily when your site gets bigger. TinaCMS does not push Free users toward a paid plan because they have published too many articles. The current Free plan includes unlimited documents. Instead, the pressure to upgrade usually appears when more people need CMS access, when content needs a formal review process, or when an organization needs stronger permissions, support, or enterprise authentication.
There is also an important distinction behind the pricing page: TinaCMS and TinaCloud are not the same thing. TinaCMS is open-source software. TinaCloud is the hosted backend and collaboration service that removes much of the work involved in operating Tina in production.
That distinction changes how TinaCMS pricing should be evaluated. The real decision is less “Is TinaCMS free?” and more “When is paying for TinaCloud more sensible than staying on Free or running the backend ourselves?”
Pricing and plan details in this article were checked on August 27, 2026. TinaCMS can change plan limits and feature availability, so verify the current pricing page before purchasing.
TinaCMS vs. TinaCloud: What Are You Actually Paying For?
TinaCMS is built around a Git-backed approach to content management. Content can live in Markdown or JSON files in your repository, while Tina provides an editing interface so writers and marketers do not have to work directly with those files.
In production, however, the editing experience needs backend infrastructure. Tina’s data layer provides a GraphQL API, and the system needs authentication, authorization, database indexing, and Git integration so authenticated editors can safely make changes.
TinaCloud provides that infrastructure as a managed service. If you use TinaCloud, its subscription plans are what you are evaluating on the Tina pricing page.
Tina also supports self-hosting. In that model, you can provide your own database, authentication system, Git integration, and backend endpoint instead of depending on TinaCloud.
That means TinaCMS can be free in a meaningful open-source sense, but a production CMS still has an operational cost somewhere. You either pay TinaCloud, or you take responsibility for more of the infrastructure yourself.
TinaCMS Pricing at a Glance
Tina currently offers five TinaCloud tiers: Free, Team, Team Plus, Business, and Enterprise. Prices are listed in US dollars and are charged per project.
Free: $0. It includes 2 users, 2 roles, one project, community support, unlimited documents, and a 100 MB asset-size cap.
Team: $29 per month when billed monthly, or $290 per year. It includes 3 users and supports up to 10 users. Additional users are currently $9 each on monthly billing or $90 per seat per year on annual billing.
Team Plus: $49 per month or $490 per year. It includes 5 users and allows up to 20. Additional users are currently $15 per month or $150 per year. Tina’s current pricing page also lists Editorial Workflow on this tier.
Business: $299 per month or $2,990 per year. It includes 20 users, has no listed user ceiling, and adds Business Support, three roles marked as beta, Editorial Workflow, and API functionality marked as beta.
Enterprise: Custom pricing. This is the tier aimed at organizations needing features such as SSO, custom requirements, enterprise support, or more complex governance.
There is one pricing-page detail worth watching. Tina prominently displays lower effective monthly prices when annual billing is selected. For example, Team appears at roughly $24 per month when the $290 annual fee is divided across 12 months. The month-to-month price is still $29.
How Far Can You Actually Go With TinaCMS Free?
Quite far, provided the team stays small.
The most important thing about the Free plan is what it does not meter: documents. Tina currently lists unlimited documents across its plans, including Free.
That makes Tina’s upgrade path different from CMS products where content records, API requests, bandwidth, or database usage quickly become the main pricing constraint.
A blog with thousands of Markdown files could theoretically remain on TinaCloud Free if only one or two people need CMS access. Meanwhile, a much smaller company website could outgrow Free immediately if three members of the marketing team need individual accounts.
This is why site size alone is a poor way to decide whether TinaCMS Free is sufficient.
Who is TinaCMS Free best for?
Free is particularly attractive for a solo developer running a content site, a developer working with one non-technical editor, a small documentation project, a personal site, or an early-stage company where CMS access is tightly controlled.
It can also make sense for evaluating Tina on a real project rather than treating Free as a temporary sandbox. The important constraint is that only two users can access the project.
The First Hard Upgrade Trigger: A Third User
For many small teams, this is the point where Free stops being enough.
Imagine a site initially maintained by one developer and one content manager. That setup fits neatly within the Free plan.
Then the company hires a marketer, adds a freelance writer, or decides that another developer needs CMS access. Now there are three people who need separate accounts, while Free is capped at two.
The website itself may not have changed at all. Traffic might be identical. The content library might contain exactly the same number of documents. Yet the collaboration model has changed enough to create a paid-plan decision.
This makes team size one of the most important TinaCMS pricing metrics to monitor.
Team: Paying Mainly for More Collaborators
Team is the most straightforward upgrade from Free. It starts at $29 on month-to-month billing and includes three users, with the ability to expand to ten by purchasing additional seats.
The ideal Team customer is not necessarily operating a technically complicated website. It is simply an organization that likes the basic TinaCloud experience but needs more than two authenticated users.
Think of a startup where a developer, marketing lead, and content writer all need access. Or a documentation team where several employees contribute updates but the publishing process is still relatively simple.
The question is whether $29 per month is worth paying just because a third person needs access. In a commercial environment, the answer can easily be yes. Giving each contributor an individual account is preferable to sharing credentials, and managed infrastructure has value when people depend on the CMS for their jobs.
But Team should not be mistaken for a major workflow upgrade. It still lists two roles, and organizations with more complicated approval or governance requirements may quickly start looking at the next tiers.
Team Plus: When Publishing Workflow Becomes the Real Requirement
Team Plus costs $49 per month or $490 annually and raises the included user count to five, with a maximum of 20 users.
The more interesting reason to consider it is not simply the extra seats. Tina’s current pricing page lists Editorial Workflow as a Team Plus feature.
Editorial Workflow changes the risk model of publishing. Instead of every content edit being written directly to a protected production branch, Tina can create a separate Git branch and draft pull request. Editors can continue working on that branch, a preview can be reviewed, and the changes can then be merged when they are ready.
For a developer, that sounds like a familiar Git process. For an editorial team, it translates into something more useful: draft, review, approve, and publish without making every unfinished change immediately part of the production branch.
That matters for agencies requiring client approval, documentation teams reviewing technical changes, companies with legal or compliance checks, and publishers where writers should not be able to push every edit straight into production.
There is currently a Tina documentation inconsistency
Anyone buying Team Plus specifically for Editorial Workflow should verify availability before subscribing.
As of this review, Tina’s pricing page lists Editorial Workflow under Team Plus. Its dedicated Editorial Workflow documentation says the feature is available on “select paid plans.” However, a separate Tina marketing page for Editorial Workflow still says it is available only on Business and Enterprise.
The pricing page is the most relevant source for a purchase decision, but the conflicting information is significant enough that teams depending on the feature should confirm entitlement with Tina before committing.
Business: A Much Bigger Price Jump
Business is where the pricing conversation changes substantially.
The plan costs $299 per month on monthly billing or $2,990 annually. It includes 20 users and currently lists no maximum user limit. Tina also lists Business Support, three roles marked as beta, Editorial Workflow, AI features marked as coming soon, and an API marked as beta.
At this level, the question should not be “Do we want a few more CMS features?” A jump from $49 Team Plus to $299 Business requires a stronger organizational reason.
The better reasons are operational: a larger content organization, higher support expectations, more people requiring access, additional role separation, API requirements, or a business where CMS problems have enough financial impact that better vendor support matters.
For a solo publisher, small blog, developer-led documentation site, or five-person marketing team, Business is likely to be difficult to justify unless one of its specific capabilities solves an important problem.
In other words, Business should be justified by governance and operational requirements, not by the assumption that a bigger website automatically needs a bigger plan.
Enterprise: When CMS Pricing Becomes an IT Decision
Enterprise has custom pricing and is aimed at organizations whose CMS requirements extend beyond normal editing and publishing.
SSO is the clearest example. For a large company, centralized identity and access control may be a security requirement rather than an optional convenience. Enterprise-level support, custom roles or workflows, procurement requirements, and corporate infrastructure constraints can also move the decision beyond the content team.
This is why Enterprise should not be interpreted simply as the plan for a high-traffic website. A site can have substantial traffic without needing enterprise CMS governance. Conversely, an internal or lower-traffic corporate property may still require Enterprise because of security and identity policies.
Don’t Overlook TinaCloud’s Per-Project Pricing
User count is the obvious pricing constraint, but another detail can become equally important: Tina says its prices are per project.
Its current plan comparison lists one project for each standard plan.
For a company with one main website, that is easy to understand. The economics become more interesting when the organization operates a corporate site, documentation site, developer portal, separate product properties, campaign sites, or multiple brands.
An agency should pay even closer attention. A $29 or $49 subscription may look inexpensive when considering one client project, but an agency managing numerous independent Tina projects needs to model the cost across all of them rather than treating the subscription as an account-wide fee.
Before choosing TinaCloud, map both variables: how many people need access and how many separate projects will need TinaCloud.
Can You Self-Host TinaCMS Instead of Upgrading?
Yes, and this is one of the most important differences between evaluating Tina and evaluating a closed SaaS CMS.
Tina’s documentation provides a self-hosting path for its backend. You can supply your own database, authentication and authorization system, and Git provider while hosting the GraphQL backend yourself.
Tina provides an Auth.js-based authentication option, for example, and its self-hosting documentation describes deployments using serverless environments such as Vercel and Netlify.
But “self-hosted” should not be translated into “no cost.”
A managed TinaCloud plan has an obvious subscription cost. Self-hosting replaces some of that subscription expense with infrastructure and engineering responsibility.
You need to consider hosting, database services, authentication, configuration, deployment, updates, monitoring, debugging, security, and the developer time required when something fails.
For an engineering-heavy company already operating similar infrastructure, self-hosting may be perfectly reasonable. It may also be attractive when an organization wants greater control over authentication or needs an architecture that does not map neatly to TinaCloud’s commercial plans.
For a small content team, however, paying TinaCloud can easily be cheaper than turning CMS infrastructure into another internal system that developers have to maintain.
The AI Question: Don’t Pay for a Roadmap Feature
Tina’s pricing page currently references AI capabilities, but it marks them as “Coming Soon.”
That distinction matters when comparing TinaCMS with CMS platforms already selling mature AI-assisted editing, generation, translation, personalization, or content-operations features.
A feature on a roadmap should not carry the same purchasing weight as a capability you can test in production today.
For now, evaluate TinaCloud’s paid tiers based on existing collaboration, workflow, support, authentication, and infrastructure benefits. Treat future AI functionality as potential upside rather than part of the current value calculation.
When Tina’s AI tools become generally available, the useful questions will go beyond whether the editor can generate text. A serious evaluation should examine whether AI understands Tina’s structured content models, can populate fields reliably, assists with metadata and SEO, respects roles and publishing workflow, supports repeatable editorial operations, and introduces separate usage limits or costs.
Those details will determine whether AI meaningfully changes TinaCMS’s value for content teams or simply adds another writing assistant to the editor.
When Does TinaCMS Free Actually Stop Being Enough?
For most users, there are four upgrade triggers worth watching.
1. People: Free supports two users. A third person needing their own CMS account is the cleanest trigger to consider Team.
2. Workflow: Once content needs formal review, protected branches, pull requests, previews, or approval before production, the decision moves beyond simple seat count. This is where Editorial Workflow becomes relevant.
3. Projects: TinaCloud pricing is per project. Organizations running several independent sites need to model that cost separately.
4. Governance: Larger organizations may need additional roles, stronger support, SSO, API access, or enterprise controls regardless of how many documents they publish.
Notice what is missing from that list: content volume.
Because Tina currently includes unlimited documents across the plans shown on its pricing page, the typical upgrade path is driven more by how an organization works than by how much content it stores.
Which TinaCMS Plan Should You Choose?
Choose Free if one or two people manage a single project and you do not need sophisticated editorial governance. It is especially compelling for developer-led sites and small teams that want a real Git-backed CMS without immediately adding another SaaS bill.
Choose Team when the Free workflow still works but more people need individual access. For many small commercial teams, this is the most natural paid tier.
Evaluate Team Plus when you need more collaborators or when Editorial Workflow is important. Because Tina’s current pages provide conflicting information about workflow availability, confirm the feature with Tina if it is the reason you are upgrading.
Choose Business only when the larger user allowance, support level, roles, workflow, or API capabilities solve a concrete operational need. The price increase is too large to justify merely because Business appears more complete on the comparison chart.
Talk to Tina about Enterprise when SSO, corporate identity requirements, custom governance, or enterprise support are part of the buying process.
Consider self-hosting if your organization has the engineering capacity and values infrastructure control enough to take responsibility for the backend, database, authentication, authorization, and Git integration.
How TinaCMS Pricing Compares With Alternatives
TinaCMS should not be compared with Sanity, Contentful, Storyblok, DatoCMS, Payload, Strapi, or Decap CMS by looking only at the cheapest advertised monthly price.
The underlying pricing and architecture models differ too much.
Some headless CMS platforms make API usage, bandwidth, content records, environments, locales, or seats major pricing variables. Self-hosted platforms may have little or no software subscription cost but require more infrastructure work. Tina combines open-source software, Git-backed content, an optional managed cloud service, and a pricing model where collaboration and project count deserve particular attention.
A useful comparison therefore asks: How many editors do we have? How many projects will we run? Where will content live? Do editors need visual editing? Do we need formal approvals? Who operates the backend? What happens when usage scales? Do we require SSO? And which AI features actually exist today?
Those questions produce a much better buying decision than comparing the first number printed on each vendor’s pricing page.
TinaCMS Pricing Verdict
TinaCMS Free is more than a disposable trial. For a one- or two-person team managing a single project, it can be a legitimate production option, particularly because Tina currently does not impose a document limit on the Free plan.
The first meaningful constraint is collaboration. Add a third editor and Team becomes relevant. Introduce formal review and publishing controls and the conversation shifts toward Team Plus or higher. Add larger teams, stronger permissions, API requirements, support expectations, or corporate authentication and Business or Enterprise begins to make more sense.
The most important pricing lesson is therefore simple: TinaCMS Free usually stops being enough because your organization becomes more complicated, not because your content library becomes bigger.
And because Tina can be self-hosted, paying TinaCloud is never purely a software-access decision. You are also paying to avoid owning more of the CMS infrastructure yourself.
For small teams, that can make TinaCloud an easy expense to justify. For larger or engineering-heavy organizations, the right calculation is not “free versus paid.” It is TinaCloud subscription cost versus the total cost and responsibility of running the same capabilities yourself.
Frequently Asked Questions
Is TinaCMS free?
Yes. TinaCMS is open-source, and TinaCloud also has a Free plan. The current Free cloud plan includes two users, two roles, one project, community support, and unlimited documents.
What is the difference between TinaCMS and TinaCloud?
TinaCMS is the open-source CMS software and editing experience. TinaCloud is Tina’s managed backend service for capabilities such as the content API, authentication, Git-connected editing, and collaboration. TinaCMS can also be configured with a self-hosted backend.
How many users can use TinaCMS Free?
TinaCloud Free currently supports a maximum of two users. If a third person needs their own CMS access, you will need to consider a paid TinaCloud plan or a different deployment approach.
Does TinaCMS charge based on the number of documents?
Not under the current TinaCloud pricing table. Tina lists unlimited documents across Free, Team, Team Plus, Business, and Enterprise. Other limits, particularly users and projects, are more likely to affect the plan you need.
Is TinaCloud pricing per website?
Tina describes its pricing as per project, and the current comparison table lists one project for each plan. If you operate several separate sites or TinaCloud projects, account for project count when estimating total cost.
Can TinaCMS be self-hosted?
Yes. Tina documents a self-hosted backend option where you provide infrastructure such as the database, authentication, Git integration, and backend hosting. Self-hosting can reduce dependence on TinaCloud, but it transfers more implementation and maintenance responsibility to your team.
Does TinaCMS have AI features?
Tina’s current pricing page references AI features but marks them as coming soon. Until those capabilities are released and documented, they should be treated as roadmap items rather than established reasons to buy a particular plan.
Is TinaCMS Team worth paying for?
Team makes the most sense when more than two people need CMS access but your workflow is still relatively straightforward. If you only have one or two editors, Free may continue to cover the core TinaCloud requirements. If approvals and publishing governance are the real problem, evaluate the workflow features on higher tiers instead of upgrading solely for seats.
