About projects

A project is the root resource from which all else flows in Hiphops. They allow you to create segregated environments, with only billing shared between them.

Everything in Hiphops is tied to a specific project, other than billing.

• Registries are linked one-to-one with projects (every project has one and exactly one registry)
• All permissions and identities exist within the bounds of a project
• Permissions cannot reference or impact other projects, even if they share an owner

They’re useful for strict segregation, for example creating dev and prod environments.

All projects share the current subscription plan of the owner - this is the only bridge between them.

Sharing a plan means your test environments can enjoy the exact same features as production, without needing to purchase two enterprise or team subscriptions.

Project management via API

Project endpoints require a user login (rather than tokens issued by Hiphops projects themselves). We do expose and document these endpoints via the API, but given the auth restrictions you may find them unsuitable for automation.

In this way, a project in Hiphops is similar to the initial account in other infra provider services. We just make it easy for you to create multiple instances of them without having to mange multiple logins.

Project endpoints are self explanatory, and the primary use is via the dashboard. As such, we won’t expand further on API flows here.

Project actions

• Projects can be created via the dashboard here
• Deleting a project is done on the project’s own home page
• A project name can be edited on the project’s home page, just hover over the name heading
• You can see all projects you have access to on the dash here