Design first. Code when needed.
ALL OF FREE PLUS
ALL OF PRO PLUS
Replacing
Auto-generate the terraform code from the design and edit the generated code
Write Terraform code manually
Multiple users can design, edit and review the changes in real time. Users can use the work of each other without reinventing the wheel through templating of architectures, modules and CI/CD workflows.
No or low collaboration between DevOps & Cloud Architects.
Create the infrastructure diagram and the IaC code that match 100% the deployed infrastructure
No live diagram view of infrastructures.
Have architectures along with their IaC configuration as templates, public or private.
Not supported.
Import your existing terraform code to visualize your resources &/or convert your legacy infrastructure into terraform code - within minutes.
6-9 months of dedicated work for a cloud architect to manually write everything.
Add, delete, use and manage Terraform modules, public or private. Modules catalog automatically created.
Only public Modules supported.
Brainboard (Terraform 100% coverage)
Diagramming + IDE + CI/CD Engine + Management Solution
Terraform variables that can be defined across organization, projects, environments and architectures
Not supported
Visually build (no YAML or specific DSL Language needed) and run pipelines and also manage dependencies between stages (external system when a condition is met)
Deployment only. No pipelines
Custom runners hosted by Brainboard that will execute the pipeline
Hosted on their infrastructure
Convert any pipeline into template and use it
Not supported
Estimate the cost of the infrastructure (based on code) using infracost
Not supported
The possibility to call an external system when a condition is met
Not supported
Approve or reject the execution of any task with a maximum granularity per task
Not supported
OIDC & SAML, Different IDP providers (Octa, Azure AD...) with federation
Not supported
Define/codify policies used to manage the infrastructure with: OPA, AWS config rules
Not supported
Role Based Access Control supported
Not supported
Supports all types of backends: AWS S3, Azure blob storage, Google GCS, Terraform cloud, Gitlab remote backend, HTTP endpoints, Brainboard remote backend
Limited & depending to local environment & hosted services.
Scan the IaC code for security with: tfsec, OPA, Checkov, Terrascan
Not supported
AWS, Azure, GCP, OCI, Azure stack, Azure DevOpos, Scaleway and more planned for 2024. Multicloud is supported.
Limited to one cloud provider or 2 major.
Unified Readme documentation, diagram, and code for everyone.
Potential drift between the design and the code.
Detect changes that either doesn't match the code or doesn't match the deployed infrastructureThe possibility to prevent drift between environments.
Not supported
Support: Gitlab, Github, Bitbucket, Azure DevOps
Git supported
Unified view of infrastructure projects, environments and architectures
Requires a dedicated management tool.
Native mechanism to synchronize enviroments for e.g. staging, QA and production (Terragrunt like)
Not supported
Use modules from Terraform registry
Not supported
Keep track of every modification you do on design / code and or go to any specific point-in-time. Native versioning or Git supported.
Not supported
"As an engineer myself, I wanted to empower engineers to focus on designing, deploying and managing cloud architectures right, with best practices and security by design, allowing anyone to understand the infrastructure. Brainboard is the solution for enterprise cloud infrastructure."
Chafik
CEO & Founder of Brainboard
Join the 20,000+ engineers designing, deploying, &
managing their cloud infrastructure on Brainboard today.
Brainboard proudly stands as the premier cloud design solution. We empower engineers like you to prioritize thoughtful design before diving into code. It's a natural approach: design first, and let the code auto-generate.
Brainboard helps you create standards and best practices that automatically applied at the design level makign it easier for both technical and non-technical stakeholders to understand.
This approach is detailed in our last webinar discussion with Chafik, our CEO and Tarak, our Growth Sales Manager!
Brainboard empowers you with the ability to effortlessly import data from various sources, including git repositories, Terraform files, and cloud platforms like Azure.
With this functionality, you can seamlessly visualize your existing cloud diagram, gaining a comprehensive overview of your infrastructure. Additionally, Brainboard generates a Terraform file based on the imported data, allowing you to conduct thorough testing and validation of your infrastructure configurations.
This comprehensive approach offered by Brainboard enables you to make informed decisions, ensure the accuracy of your infrastructure setups, and maintain a robust and reliable environment.
To try this feature, you have to be engaged in a Pro or Enterprise Plan.
Brainboard offers several key features that enhance your Infrastructure-as-Code (IaC) operations:
Data Ownership: In Brainboard, users own their data in every action they do, whether it's pull requests, git workflows, or remote back-end. Brainboard only accesses data in specific scenarios, such as designing and pushing to git, planning and pushing to git, and designing & deploying within Brainboard.
Isolated Environment for Terraform Execution: Brainboard provides several execution options for your Terraform code, including running Terraform in an isolated environment. This means that the code is executed in a separate, secure environment that is not accessible by other applications or users, providing an additional layer of security to your data during testing.
Encryption: All data stored in Brainboard, including the architecture diagram, cloud resources and configuration, variables, and credentials, are encrypted both at rest and in transit. This means that the data is stored in an encrypted format in the Brainboard database and any data transmitted between Brainboard and external systems is encrypted to prevent interception by unauthorized parties.
Role-Based Access Control (RBAC): Brainboard has implemented RBAC, a security mechanism that ensures that users have access to only the resources they need to perform their jobs. By defining IAM (Identity and Access Management) roles and policies, you can assign permissions to users based on their job function and limit access to only the resources they need to perform their work.
SOC2 Certification: Brainboard is SOC2 certified, meaning that the platform has undergone a rigorous security audit by an independent third-party auditor and has been found to meet the criteria for the SOC2 security standard. This certification demonstrates Brainboard's commitment to maintaining the highest levels of security and privacy for their customers’ data.
Brainboard is designed to be user-friendly and accessible, requiring minimal to no prior knowledge of Terraform or Infrastructure-as-Code (IaC).
Its intuitive visual interface empowers a wide range of users - from cloud architects, DevOps, and SecOps professionals to project managers and developers - to effortlessly design, deploy, and manage cloud infrastructures.
You can use Brainboard's native integration with Infracost to analyse your infrastructure cost at t=0. Our goal is to create an end-to-end solution for your cloud infrastructures.
As a side note, more open source options will be available soon in the Brainboard's CI/CD Engine.
Yes, you can import your Terraform modules into Brainboard. To manage these modules, you can navigate to the modules catalog. Here, you can see and manage all your imported modules. You can choose which ones you want to have displayed in the modules list in your design area by pinning them.
If you want to change the configuration of a module, you can select one of the modules in the list. In the module configuration, you can show the module in the design or remove it from the design by using the pin button. You can edit the configuration by using the pen button. If you want to delete the module, you can do so by using the bin button.
For a more organized modules list in your design area, it's recommended to only pin the modules that are needed for a specific architecture. If you need more modules, you can return to the modules catalog later and pin them.
Brainboard provides a variety of cloud architecture templates. These are pre-designed and standardized architectures that can be used to create and deploy cloud infrastructure. They include a set of guidelines and best practices for designing, building, and managing cloud infrastructure. The templates typically provide the design and Terraform code of the architecture and include details on the components that make up the infrastructure, such as virtual machines, storage, networks, and security.
Templates in Brainboard are designed to be reusable, making it easier and quicker to implement and manage cloud infrastructure. They can help organizations to achieve consistent deployment patterns, enforce governance policies, and reduce time and effort required to deploy cloud infrastructure.
Cloud architecture templates include AWS Well-Architected Framework, Google Cloud Architecture, Microsoft Azure Architecture, and the OpenStack Architecture.
In Brainboard, you can find two types of templates:
1. Organization Templates: These are templates that are visible and can be used only within the organization in different projects. The organization templates can be used when teams want to share their templates and reuse them in other projects or architectures of the organization.
2. Public Templates: These are usually templates published by the Brainboard team and are verified templates that are built by cloud architects that maintain and update them regularly.
You can create your own templates, modify existing ones, and use templates for your projects. When using a template, you can clone it into a new architecture or copy it into your current architecture, and then customize it to fit your specific needs. After customization, you can deploy the template to your environment.
For the moment, any signed up user is not allowed to edit the terraform code automatically generated.
Nevertheless, due to overwhelming demand, we've now added the ability to EDIT the generated code. Join waiting list.
There are 2 aspects in terms of collaboration:
1. Build: Brainboard supports real time editing of the same architecture by multiple users. All you need to do is to invite your colleagues and give them the right access.
2.Deploy: when you build your CI/CD pipeline within Brainboard, you have the possibility to request approvals from any team/person, which allows you to orchestrate the execution by involving all stakeholders.
Brainboard has an innovative visual CI/CD engine dedicated for the infrastructure, where you can execute all Terraform actions (Terraform plan, Terraform apply, Terraform destroy) within a secure sandbox and get the output in real time or build your deployment workflow and trigger it.
From Design to Production, 75% faster. Brainboard integrates natively pioneers in the Cloud Computing industry to deliver the best seamless experience in the Cloud. The new CI/CD Engine is bringing a whole new level of automations and integrations into Brainboard.
Yes, you can deploy multi-cloud environments with Brainboard. Brainboard's CI/CD engine is designed to support multi-cloud deployments, allowing you to manage and deploy your applications across different cloud environments, such as Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.
This enables you to take advantage of the unique benefits of each cloud platform and ensure high availability, scalability, and disaster recovery for your applications.
To deploy to multiple cloud environments, you can create separate workflows in the Brainboard CI/CD engine, each targeting a different cloud platform. You can then manage these workflows and deployments through a single interface, making it easier to coordinate and monitor multi-cloud deployments.
Good question!
We plan to allow triggering another architecture workflow inside our CI/CD Engine.
In the meantime, you can use any Terraform resource, even the one not directly supported in Brainboard using the resource called "Terraform custom", then you can write your own resource.
There are several ways to get in touch and get support:
Real-time Support: While using Brainboard, you can reach out in real time by clicking on the "Ask us anything" button in the top right corner. One of the team members will reply to answer your questions or assist you with any technical topic.
Slack Community: Join the Brainboard Slack Community, the whole Brainboard team and thousands of professionals are free to engage with each other!
Email Support: If you prefer asynchronous communication or if you want to schedule a call for help on a specific technical topic, you can reach out to the technical team at [email protected]. A cloud architect from the team will assist you.
Slack or Teams Support: In PRO plan, we can integrate directly into your internal communication channel to always be available whenever a question pop out.
Custom Support: We offer custom support for Enterprise level customers, featuring terraform training, to security assessments & design consulting. Book a demo with one of our professional.
Report Security Issues: If you need to report a security issue, you can reach out to the security team at [email protected].
Feature Request: If you want to request a new feature or see what the community has requested, you can check Brainboard's public roadmap.
Request a Demo: To request a demo of Brainboard, you can reach out to the sales team at [email protected].Remember, the Brainboard team loves talking to their users, so don't hesitate to reach out with any questions or concerns you may have.
Yes, we provide a self-hosted version based on eligibility criteria. If you are interested in the hosted version, please contact us.