Getting Started with Twilio Projects and Subaccounts

Twilio Console allows users to create two different types of accounts: Projects and Subaccounts.

Projects

Twilio Projects are separate Twilio accounts with their own resources and account balance. Projects are recommended to all customers who are building out different use cases, segregating data for different development lifecycle phases, or need to control user access. Projects are required for building Twilio Flex, and also recommended for PCI compliant payment processing with <Pay>.

Twilio Projects can be be created and accessed via Console. For more details, please see our article View and Create New Projects in Twilio Console.

Subaccounts

Project-owned Subaccounts have their own resources, but are owned by a project, and share that balance. Subaccounts are recommended mainly for independent software vendors (ISVs) to separate usage from their different customers. They may also be a better fit for customers who already have a large number of existing Twilio phone numbers and short codes, or for those using reporting APIs to organize their usage outside of Console.

Subaccounts can be created and accessed via Console, but can also be managed via the REST API. For more details, please see our article View and Create New Twilio Subaccounts.

Comparison

  Projects Subaccounts
Who is it for? All Twilio customers  ISVs
Why should you use it? Segregate production and dev environments, new use cases, or new products like Flex and <Pay>. Separate usage from your customers, while keeping only 1 billing account.
How is it billed? Each Project has its own balance. Subaccounts are owned by a single Project with a single shared balance.
Where is it managed? Twilio Console Twilio Console, or the REST API
How many can I have? 5 maximum * 1,000 maximum *

*If you're worried about approaching this limit, please contact our Support team to inquire about raising it.

Have more questions? Submit a request
Powered by Zendesk