1. Introduction

1.1. Organization

Forj is combination of 2 components:

• Maestro. Maestro’s code is managed in Forj’s forge, and published to Github under forj/maestro.
• Blueprint (s). Read by Maestro to install a forge. Those blueprints are exposed in Forj’s catalog, developed in Forj’s forge, and published to Github under forj. There is one GIT repository per blueprint.

1.2. Philosophy

Forj is vendor-agnostic. The goal is to provide integrated software development tools which solve a problem. The tools can be all Open Source, a mix of Open Source and proprietary tools, or a set of proprietary tools. As long as a tool has a way to be installed or integrated with other tools, Forj will have a way to make it part of the Forge. In other words, it is possible to integrate tools hosted in the cloud with tools installed on your own servers to create a forge.

Forj is destination-agnostic. The forge can be installed on a public or a private cloud or on premises. Forj leverages the fog library to be able to provision systems on many different clouds and thus avoiding vendor lock-in. A great benefit is that you can relocate a forge from a public cloud to a private cloud or from a cloud provider to another.