Manage your platform
Organizations, projects, billing and the interface itself.
What sits outside a project
An organization is the boundary for identity and billing. It holds the team members who can reach Data Platform, the certificates and domains shared across projects, the quotas that cap what projects may consume, and the billing accounts the consumption is charged to. Every project belongs to exactly one organization.
A project is created from the organization, in a chosen cloud region, and is deleted from there too. Its subdomain and configuration identifiers are what external tools and code use to address it, so they turn up in almost every API call and connection string in this documentation.
Pricing explains what is metered and what is not: the compute unit, the components that hold it, storage and query volumes, and where to watch cost before it becomes a surprise.
Permissions for these actions are not granted here. Creating and deleting projects, inviting people and changing organization settings are all governed by the Identity Access Manager.
Navigate the platform→
Homepage, sidebar and header, and how to move between projects.
Understanding Data Platform pricing→
What is metered, what is not, and where to watch cost.
Organizations and user profiles→
The identity and billing boundary every project belongs to.
Projects→
What a project contains and how it is isolated.
Go further
If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.
Ask questions, give your feedback and interact directly with the team building the Data Platform on the dedicated Discord channel.
If you need support with your OVHcloud services, create a request in our Help Centre.
Join our community of users.