Infrastructure as code in a visual
and imperative way

Prototype, script, automate, building complex workflows on top of the APIs of multiple cloud providers with a simple tool!

1. Use your browser

Create a blueprint by dragging actions from the providers list and connecting them. Drag as many actions as you want, there are no limits.

2. Test your blueprint

Run our CLI tool in server mode and let the Builder connect to it. You can then test-run your blueprint and debug it.

3. Export and use

Save your blueprint as a file and run it wherever you want, for example, in your CI pipeline!

Quick FAQ Navigation

General questions

A blueprint is a JSON file that contains the work you have done using our editor. This file can we imported into our editor for further modifications or executed with our CLI tool.
An action represents a process of some sort (API request, command invocation, etc...) that will be executed by the CLI. Some actions don't contain any additional data / settings (like the 'No Op' action), while other actions can be configured (for example, you can set how long the 'Sleep' action should make the CLI idle before executing the next action).
Providers are groups of actions that belong to a particular vendor or category. For example, the 'AWS' provider is just how we call the group of actions that allow you to perform actions using the AWS API.
There is the 'Execution control' provider, which contains a few actions used to control the behavior and the execution flow of the CLI. There is the 'Generic' provider, which contains common actions that you can use to perform common actions (like upload or download files, send an email o perform a raw HTTP request). Last, but not less important, there are all the providers related to cloud services or other APIs. Just to name a few: AWS, Azure, Google Cloud, etc... These are the actions that will allow you to perform operations with your cloud infrastructure.
The settings of some actions require specific data which might not be easy to remember / type. For example, the action that is used to create an AWS instance requires you to type the subnet ID. You can go to the AWS panel, search the subnet and copy it's ID, but that can be a cumbersome task to do for each and every field of the settings of every action. That's why you can connect the web editor to our CLI tool. If you do that, the web editor will fetch from the CLI the correct data that should be displayed in each field.
If you choose to connect the web editor with the CLI tool (more information about how to do this in the CLI section on the FAQ and in the documentation), you'll be able to run the blueprint directly on the CLI (conversion to blueprint will happen in the background automatically) while you're working on the it. Think about this feature as the usual 'Compile and run' button you'd find in any IDE.
Your blueprints are stored in our servers. They are encrypted and accessible only by you and the people you want to share them with.
Once you've created a blueprint you can upload it to our marketplace and share it with other people. You can also browse the marketplace and clone an existing public blueprint, or even import an existing public blueprint into one of your blueprints.
We actually care about your privacy. That's why we don't use any tracking at all. No cookies, no javascript code sending data to anywhere, etc... Hence we don't need the cookie banner.

Questions related to our CLI

The CLI tool is a single binary that can be used as a helper for the web editor (providing live-run and autocomplete features) or as a standalone executor of blueprint files (suitable for CI/CD environments).
The CLI tool can be executed in 'developer mode'. In that mode the CLI spins up a Web Socket server and an HTTP server and binds them to your loopback network interface. This allows the web editor to establish bidirectional connection with the CLI and provide an extra layer of features, such as live-run and autocomplete.
Once you've created your blueprint you can export it as file. You can then run that file with our CLI tool.
The CLI does not depend on our backend in order to execute a blueprint.
The CLI will mimic the behavior of the SDKs of each provider. For example, if you try to execute an action from the AWS provider, the CLI will search for the same environment variables that are used by AWS's CLI, then it will search for credentials in ~/.aws/.
That is correct. We don't store any secrets. We don't even have access to any of your secrets as the CLI doesn't send any secrets to our backend. In fact, the CLI doesn't depend at all on our backend. And while it's technically possible for you to store secrets in the blueprint by using the 'Define variable' or 'Define env var' actions, we don't recommend you doing so as that is not the intended purpose of these actions.
Blueprints are not designed as a secrets store / management system. There are software solutions designed for that purpose and we encourage you to use them. Nevertheless, blueprints are encrypted on our backend. Should there be a database exfiltration or some sort of unauthorized access to our backend, we're confident that attackers won't be able to read the content of any blueprint, thus the data in your blueprints won't get exposed.
Yes! Our CLI is completely free and open source under the AGPLv3 license and it's available in the 'Downloads' menu in the header of this website.

Questions related to the pricing model and the support

You're allowed to save only that number of blueprints in your account. Once you've reached that number of blueprints, you won't be able to create new blueprints. The same rule applies for the 'Professional' plan.
Your blueprints won't be deleted, but you won't be able to create new blueprints or edit the existing ones.
Blueprints can be kept completely private in your account, completely public (by uploading them to our blueprints marketplace) or they can be made accessible to other people by creating secondary accounts for them. Each one of these secondary accounts you create requires a seat in your main account. The number of users of your plan equals the number of available seats your account has, which equals the number of secondary accounts you can create. Note that your main account counts as a used seat, which means that the 'Hobbyist' plan doesn't offer the possibility to create secondary accounts.
Access will be disabled for as many people as required in order to comply with the users limit of the new plan. Access will be disabled starting from the oldest person that was invited.
You can create a new ticket by sending us an email to our automated system and we'll reply as soon as possible.
Absolutely, we can offer priority support via any chat / video application of your preference. You can request priority support from your control panel. Pricing starts at ???€ per hour, but we offer discounts for bulk requests.
We support a variety of payment methods, like credit and debit cards, Paypal, Google pay, Apple pay, etc...