Key conceptual difference
Render’s approach: all-in-one service definitions
In Render, each service is a complete, self-contained deployment unit. If you want the same application in test and production, you create two separate service definitions with duplicated build commands, even though the code and build process are identical. This leads to repetition and makes it harder to maintain consistency across environments.Ryvn’s approach: separation of concerns
Ryvn separates what you’re building (services) from how you’re deploying it (installations):- Services: Define the source code, repository, and build process once
- Installations: Configure deployment-specific settings like resources, scaling, and environment variables per environment
Quick mapping reference
Service definition (build time)
Installation configuration (deploy time)
Environment variables
Web service example
Cron job example
Migration steps
- Create variable groups for your Render environment groups
- Define services as resource YAML files with build configuration
- Add environments with provider configuration
- Create installations per environment with runtime config
- Configure Git Sync in Ryvn Dashboard
- Push and deploy
Key differences to remember:
- Repository format:
owner/reponot full GitHub URL - Build commands go in service definition
- Start commands go in installation config
- Resources must be explicit (no “plan” names)
- Web services need explicit ingress configuration