Blueprints

Blueprints are a way to templatize common combinations of Zeet Project configuration. Blueprints build on top of Project Types and can specify any of the inputs (including Source, Networking Settings, Environment Variables and other Inputs) to a new Project in a single place. Teams can use Zeet's Blueprints to streamline their deployment workflow and iterate exponentially faster.

In simpler terms, Blueprints are templates that define how a Project is deployed in Zeet.

There are 2 types of Blueprints: Official Blueprints and Custom Blueprints. They're the same underneath, the main difference is who created the Blueprint: Zeet, or your team.

Official Blueprints are Blueprints that Zeet offers by default to all teams. There is a wide array of Official Blueprints available across all Project Types, including but not limited to, Databases, Vector Databases, common Kubernetes components, and off-the-shelf open source software tools. You can find all available Blueprints on the Zeet Marketplace.

Custom Blueprints are Blueprints that someone on your team made, for other members on your team. See our official docs for more information.

Can I deploy without a Blueprint?

Yes! Blueprints are simply a way to quickly package up common configurations. You can always start with one of our Project Types and configure everything from scratch.

When should I deploy with a Blueprint?

Blueprints are best when there's some off-the-shelf software you want to use - like a specific database, or a specific open-source application - and your team has a Blueprint enabled that captures that workload. If you're deploying your own code, you should probably just start from scratch with the right Project Type.

Updated on: 25/01/2024