Skip to main content

Documentation Index

Fetch the complete documentation index at: https://ryvn.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

The Blueprint Marketplace is a catalog of production-ready infrastructure blueprints maintained by Ryvn. Each marketplace blueprint packages a fully configured service — like a managed Postgres database or Redis cache — with production defaults already set: deletion protection, automated backups, storage autoscaling, and encrypted connections. Marketplace blueprints work across AWS, GCP, and Azure. You configure the service once using high-level inputs (instance size, storage, high availability), and the blueprint translates that into the right resources on whichever cloud provider your environment uses.
Marketplace blueprints are the same kind/spec as custom blueprints — the difference is that Ryvn maintains them and keeps them updated as cloud providers change their managed offerings.
Browse the full catalog at ryvn.ai/marketplace, or list available blueprints with the CLI: 
ryvn get blueprint --marketplace

​
Installing a marketplace blueprint

Marketplace blueprints are referenced using the ryvn.app/ prefix. You can install them from the Dashboard, via infrastructure as code, or using the CLI.

​
From the Dashboard

  1. Open the Blueprints page and select the Marketplace tab.
  2. Click on a blueprint to view its inputs, outputs, and description.
  3. Click Actions → Install and select the target environment.
  4. Configure the inputs and confirm.

​
Via infrastructure as code

Reference marketplace blueprints in a BlueprintInstallation resource using the ryvn.app/ prefix on the blueprint name: 
# yaml-language-server: $schema=https://api.ryvn.app/v1/schemas/resources.json
kind: BlueprintInstallation
metadata:
  name: my-database
spec:
  blueprint: ryvn.app/postgres
  environment: production
  inputs:
    - name: size
      value: medium
    - name: highAvailability
      value: "true"
This is a standard BlueprintInstallation resource — the only difference from a custom blueprint installation is the ryvn.app/ prefix on the blueprint name. All the same properties apply: inputs, releaseChannel, excludedInstallations, etc.

​
Via the CLI

Create a blueprint installation from the command line: 
ryvn create blueprint-installation my-database \
  --blueprint ryvn.app/postgres \
  -e production
To see the inputs and outputs for a marketplace blueprint before installing: 
ryvn describe blueprint ryvn.app/postgres

​
Configuring inputs

Each marketplace blueprint defines a set of inputs that you can customize. Inputs with default values are optional — you only need to provide values for required inputs or when you want to override a default. To see the available inputs for a blueprint: 
ryvn describe blueprint ryvn.app/postgres
Or view the blueprint’s page in the marketplace.

​
Secret inputs

Some inputs are marked as secrets (e.g., database passwords). These are handled securely:
  • Generated secrets: If the input has a generated configuration, a value is automatically created when the blueprint is installed. You don’t need to provide it.
  • Organization secrets: You can bind a secret input to an organization-level secret using valueFromOrgSecret:
kind: BlueprintInstallation
metadata:
  name: my-database
spec:
  blueprint: ryvn.app/postgres
  environment: production
  inputs:
    - name: password
      valueFromOrgSecret:
        name: prod-db-credentials
        key: password
    - name: size
      value: medium

​
Variable groups

For map type secret inputs, you can reference an environment-scoped variable group: 
inputs:
  - name: db_credentials
    valueFromVariableGroup:
      name: db-credentials

​
Consuming blueprint outputs

Marketplace blueprints expose typed outputs — database endpoints, connection strings, credentials — that your services can reference directly. When outputs change, any services that reference them are automatically redeployed.

​
Environment variables

Use valueFromOutput to inject blueprint outputs into your service’s environment: 
env:
  - key: DATABASE_HOST
    valueFromOutput:
      blueprintInstallation: my-database
      name: host
  - key: DATABASE_PORT
    valueFromOutput:
      blueprintInstallation: my-database
      name: port

​
Secrets

Secret outputs (like passwords and connection strings) must be consumed via valueFromOutput: 
secrets:
  - name: db-connection
    values:
      - key: connection_string
        valueFromOutput:
          blueprintInstallation: my-database
          name: connectionString
      - key: password
        valueFromOutput:
          blueprintInstallation: my-database
          name: password

​
Template syntax

Non-secret outputs can also be referenced in configuration templates: 
config: |
  database:
    host: {{ (blueprintInstallation "my-database").outputs.host }}
    port: {{ (blueprintInstallation "my-database").outputs.port }}
Secret outputs (isSecret: true) are not available via template syntax. Use valueFromOutput to consume them.

​
Updating marketplace blueprints

Marketplace blueprints are versioned and maintained by Ryvn. When the Ryvn team updates a blueprint — for example, to support a new Postgres version or update cloud provider defaults — your installations pick up the changes on the next deploy. To view version and detail for a specific marketplace blueprint: 
ryvn describe blueprint ryvn.app/postgres
To list all available marketplace blueprints and their versions: 
ryvn get blueprint --marketplace