Skip to main content
The Ryvn Registry is a managed container registry service that automatically stores and manages container images for your applications. When you deploy applications from GitHub repositories or Dockerfiles, Ryvn builds your containers and stores them in this secure registry.

​
How It Works

When you create a service from a GitHub repository or Dockerfile, Ryvn:
  1. Automatically creates a dedicated repository in the Ryvn Registry
  2. Builds your container image
  3. Pushes the image to your dedicated repository
  4. Deploys the image to your environment
Each service gets its own dedicated repository in the Ryvn Registry, ensuring isolation and security between different applications.

​
Benefits

Zero Configuration

No need to set up or manage your own container registry

Automatic Repository Creation

Repositories are created automatically when you create a service

Secure by Default

Images are stored with end-to-end encryption

Integrated Release Management

Seamless integration with Ryvn’s release channels

​
Technical Details

The Ryvn Registry is built on Amazon Elastic Container Registry (ECR), providing:
  • High availability and durability
  • Fast image pulls and pushes
  • Compatibility with standard container tools
  • Automatic vulnerability scanning

​
Using the Ryvn Registry

The Ryvn Registry is used automatically when you: You don’t need to configure anything - Ryvn handles all the registry management for you.

​
Registry Selection

When creating a service, you can choose to use the Ryvn Registry (default) or specify your own container registry:
1

Create Service

Start creating a new service in the Ryvn Dashboard
2

Select Source

Choose GitHub or Dockerfile as your source
3

Registry Selection

The Ryvn Registry is selected by default, but you can choose your own registry if needed

​
FAQ

No, the Ryvn Registry is a managed service that’s only accessible through the Ryvn platform. This ensures security and simplifies management.
The Ryvn Registry includes storage for all your services as part of your Ryvn subscription. There are no additional charges or explicit limits.
Images are retained for the lifetime of your service. When you delete a service, its associated images are also removed after a grace period.
Yes, you can choose to use your own container registry when creating a service. See Deploy from a Registry for details.