Hiphops developer docs

We think shipping and running customer hosted software should be as easy as deploying to your own cloud.
We’ve started by creating a registry that’s built from the ground up to get your images into your customer’s hands.

Concepts

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.

Registries are tied to a specific project, all permissions are defined within a project (and cannot impact another project, even if they share an owner), identities are scoped within a project.

Access management

Hiphops access management is simple yet powerful. You’re able to create custom roles granting access to specific resources, in addition to being able to create identities for which you can mint JWTs. All of this is accessible via our API, meaning you can even automate customer access to your private images.

Registry

The registry is where you store your docker images, especially those you wish to share with customers, but not make public.

A Hiphops registry is created instantly upon project creation. A registry consumes no resources until it actually contains images, but is fully functional straight away.

API

The developer docs are intentionally high level, mostly aimed at orienting new users and explaining concepts and flows.

Our API Reference docs should be considered the primary source of truth. They’re interactive and if you’re signed in will use your credentials to make live calls.

If you’re unsure of how something works, we’d highly recommend creating a test project to just give it a go via the interactive docs. All of the endpoints are scoped to a project, so you won’t impact anything outside of the project you choose. Remember to delete the project when you’re done and everything will be cleaned up 🧹.