Platform - Plans

Liveblocks offers three plans: Starter, Pro, and Enterprise. The Starter plan is free and includes all the features you need to get started, while the Pro and Enterprise plans offer higher limits, enhanced features and resources. All plans include our first day free policy, meaning you only pay for returning users.

Starter plan

The Starter plan is free and designed for developers getting started with Liveblocks. Key features include:

• Up to 50 monthly active users, with first day free
• Up to 10 simultaneous connections per room
• Pre-built components
• Realtime infrastructure
• 3 team members per account
• Community support

Comments

Comments is free up to 50 monthly active users and 2,000 comments per month.

Notifications

Notifications is free up to 50 monthly active users and 2,000 comments per month.

Text Editor

Text Editor is free up to 50 monthly active users and 256 MB data stored.

Sync Datastore

Sync Datastore is free up to 50 monthly active users and 256 MB data stored.

Pro plan

The Pro plan starts at $180/month and is designed for companies adding collaboration in production. Key features include:

• Up to 1,000 monthly active users, with first day free
• Up to 50 simultaneous connections per room
• 10 team members per account
• More simultaneous connections
• Products priced separately
• Email support

Comments

Comments is free up to 50 monthly active users and 2,000 comments per month. You can get higher limits with a paid add-on.

Notifications

Notifications is free up to 50 monthly active users and 2,000 notifications per month. You can get higher limits with a paid add-on.

Text Editor

Text Editor is free up to 50 monthly active users and 256 MB data stored. You can get higher limits with a paid add-on.

Sync Datastore

Sync Datastore is free up to 50 monthly active users and 256 MB data stored. You can get higher limits with a paid add-on.

Enterprise plan

The Enterprise plan is tailored for organizations with custom needs and advanced security. Key features include:

• Up to 100M monthly active users, with first day free
• Tiered usage pricing
• 99.9% Uptime SLA
• SOC 2 Type 2 report
• HIPAA compliance with BAA
• Support Slack
• Implementation support
• Dedicated Slack support

Comments

Comments can be included in the enterprise plan.

Notifications

Notifications can be included in the enterprise plan.

Text Editor

Text Editor can be included in the enterprise plan.

Sync Datastore

Sync Datastore can be included in the enterprise plan.

General billing information

What is a monthly active user (MAU)?

Monthly active users (MAU) represents the number of users that have used any Liveblocks features within a given month, with the exception of users that only connect one time, as they are always free. Users are identified by the userId property provided in your authentication endpoint. This userId generally comes from your database or your authentication provider.

One unique userId corresponds to one user, no matter how long they connect for. For example, a user that connects for 5 minutes on 2 different days is counted as 1 MAU, and a user that connects 8 hours a day for a month is also counted as 1 MAU. This applies so long as usage falls under our Fair Use Policy.

First day free policy

All plans include our first day free policy, meaning you only pay for returning users. In concrete terms, when a userId connects for the first time, they do not count towards your MAU limit. They are only counted when they connect to Liveblocks again on another calendar day. For all users, days start at 00:00 UTC and end at 23:59:59 UTC.

How is data storage calculated?

Storage for Text Editor and Sync Datastore is a cumulative calculation that represents all data that is currently stored. It does not reset monthly, and the total usage will continue to accrue over time as you add more content and data. You can monitor your usage at any time in the dashboard.

Do you count monthly active users during testing?

If you connect to rooms and call the Liveblocks API during any automated testing, you may want to provide a static userId to avoid hitting limits.

For example, you could do this by setting an environment variable and checking the process when you call authorize from @liveblocks/node.

TEST_USERID="machine"

export default async function auth(req, res) {  const room = req.body.room;  const response = await authorize({    room,    secret,    userId:      process.env.NODE_ENV === "test" ? process.env.TEST_USERID : "user123",  });  return res.status(response.status).end(response.body);}