Blueprints
A blueprint is an installable Ren setup for a project, space, or organization. It can include skills, custom MCPs, instructions, an environment, and schedules.
The Software Factory blueprint creates a space with Plan, Build, Review, QA, and Monitoring projects. Each project has instructions and skills, and their shared machine includes the required tools.
Apps are blueprints too: each one adds a single tool to a project.
What installing adds
Installing creates editable spaces and projects in your organization. Later blueprint changes don’t update those copies, though attached skills and custom MCPs still use their latest versions.
- A space blueprint creates a new shared space. A project blueprint adds a project to a space you pick.
- Projects get the blueprint’s instructions, permissions, and default model.
- Ren attaches skills and custom MCPs to the projects.
- Schedules are created paused, so nothing runs until you turn them on.
- Databases, artifacts, and starter tasks are added where the blueprint defines them.
Installing doesn’t overwrite existing resources. In an existing project, Ren appends the blueprint’s instructions and keeps your settings.
Ren lists the remaining setup after installation. Connect the required accounts and add the listed channels, like Slack channels or GitHub repositories.
Install a blueprint
Browse blueprints in Marketplace → Blueprints in the app. The public Blueprints catalog lists apps. To add an app, see Add an app to a project.
Install space and project blueprints through Ren, the CLI, or MCP.
Open Marketplace → Blueprints, select a blueprint, and ask Ren to install it.
Ren lists what it created and what you still need to connect. Turn on any schedules you want from Scheduled.
ren registry blueprints listren blueprints add --source software-factory--source takes the blueprint’s slug. A project blueprint also needs --pod-id for the space to add it to.