Changelogs | Brainboard

Stay up to date with our product development by checking out our public roadmap changelog. We regularly ship new features and integrations, so be sure to check in weekly, monthly or quarterly to see what's new and how it can benefit you and your business.
🧼 Improved
about 6 hours ago

Brainboard Feature Changelog - Week #4 - January 2023

We're excited to share with you the latest updates and improvements to our platform. Here's a summary of what we've been working on this week:

🐞 FIXED

We've resolved reported issues that were causing occasional crashes when, for example:
Pull Request by Brainboard
  1. Specify a different brand when doing a pull request:
    • We now allow you to specify a different branch in the base branch field in the pull request modal, when creating a pull request. This means that you are able to select which branch they want to merge their changes into, rather than being restricted to a specific branch such as “main”. This feature can be useful for organizations that use multiple branches for development and testing, as it allows developers to easily collaborate on code changes and merge them into the appropriate branch for deployment. Additionally, it can help to maintain the versioning and history of the Terraform codebase.
  2. GCP VPC and Subnet: 
    • They were not containers*. Now, they are… 
    • Containers* in the cloud refers to the use of containerization technology to deploy and manage applications in a cloud computing environment. Containers are a lightweight and portable way to package and deploy applications, and they can be run on a variety of platforms, including Google Cloud. Containers are isolated from one another, which helps to increase security and reduce the chances of conflicts between different applications. 
    • Google Cloud offers a service called Google Kubernetes Engine (GKE) which allows you to easily deploy, scale, and manage containerized applications on the cloud.
    • Google Compute Network (GCN) is a virtual network that allows you to create and manage a network topology for your Google Cloud resources. It allows you to create subnets, firewall rules, and routes to control how your resources communicate with each other and with the internet.
    • Google Compute Subnetwork (GCSN) is a subnet within a GCN that allows you to segment your network into smaller, more manageable pieces. It also enables you to control the IP ranges for resources in a subnet, and apply firewall rules and routes to specific subnets.
  3. Variable type not saved:
    • Problem: This bug fix addresses an issue where a new variable is not correctly saving the type information during the creation or modification process. This can cause problems with the functionality of the application, as the type of variable is important for determining how the application should handle and interact with the variable's value.
    • Solution: The fix involves updating the Terraform code that is responsible for handling the creation and modification of variables to properly save the type information. This could involve checking for missing or incorrect type information, and adding code to handle this properly. Additionally, it also involves testing the updated Terraform code to ensure that the bug is resolved and that the new variables are being created and modified correctly with the correct type information. 
  4. Custom group TF file broken:
    • Problem: The bug fix addresses an issue with the functionality that retrieves custom group files in Terraform. The bug is related to the fact that when a group starts with 'f' or 't' the retrieval of the custom group file is broken. The issue with the Terraform configuration for the “test” group, as the test.tf file should contain the necessary information for provisioning and managing the infrastructure for that group, but it is empty. 
    • Solution: Create an architecture or a blueprint of the infrastructure using Terraform. Add 3–4 nodes on the design canvas, which are servers or machines that make up the cloud infrastructure. Change the group of 2 of the nodes to “test” group. Now, retrieve the test.tf file, which should contain the Terraform configuration for the “test” group.
  5. Scroll through a big output:
    • Problem: The bug fix addresses an issue with the performance of scrolling through the output of the “plan” in Terraform. The bug is causing the scrolling to be slow and unresponsive, with a delay of 2–3 seconds before the update or the next lines are displayed.
    • Solution: We optimized the code that handles the output display and scrolling by reducing the number of updates and unnecessary calculations. We always make sure the data is being loaded and processed efficiently.
  6. Import Multiple strings:
    • Problem: The bug fix addresses an issue with the way Brainboard import Terraform code that contains "<<EOF" and "EOF" for a field. The bug causes these characters to be changed into strings which causes issues in the interpretation of the code.
    • Solution: Update the import code to properly handle these characters. We make sure the code that reads and interpret the imported Terraform code is able to handle these characters correctly.
  7. Feedback survey:
    • Problem: We noticed that the feedback form brought aggressive prompts to you, builders and cloud architects. 
    • Solution: We've disabled it for now. Please continue to contribute to the Slack community and contact us if any improvements need to be fixed. We generally respond within 6h. 
  8. Editing node title:
    Cloud Architecture Design canvas by Brainboard
    • Problem: The bug fixes you addresses an issue with the way the editing of the title of a node behaves in Brainboard's canvas. The bug causes the title of the selected node to change when editing the title of a different node that is not selected.
    • Solution: We added a check to verify that the correct node is being edited, or by making sure the system is keeping track of the correct selected node.
We apologize for any inconvenience this may have caused, and thank you for bringing it to our attention.
Please note that the above issues have been fixed in the latest version of Brainboard and should no longer occur. If you continue to experience any issues, please reach out to our support team on our Public Slack Channel.

🧼 IMPROVED

We've made some performance enhancements to the:


  1. CI/CD Engine: We've just introduced a feature for approval tasks, which allows users to request and receive approval before deploying code changes to a production environment. This can be useful for ensuring that code changes have been reviewed and tested properly before they are deployed to a live environment, and can help to prevent errors or issues that could negatively impact the performance or functionality of the system.
  2. Import: We continue to improve the import feature. This week, we've focused on database use case. Now, you can import schema and documentation. A schema is the structure of the database and the rules on how the data should be organized, while a document is a single unit of data stored within the database.
  3. Deleting cloud architectures: When soft-deleting cloud architectures, we now soft delete all related objects including workflow(s), pipelines, jobs, deployments, git integrations, and terraform settings.
This should result in faster load times and a smoother user experience.

As always, we value your feedback and suggestions. If you have any thoughts or ideas on how we can improve Brainboard, please don't hesitate to reach out to our support team.

📆 Replay: Understand CI/CD strategies & Best Practices 


You can now watch last Tuesday's webinar on the details and implications of what CI/CD means for the cloud infrastructure. This is a short preview of what you will learn in less than 70 minutes: 
🧼 Improved
7 days ago

Brainboard Feature Changelog - Week #3 - January 2023

We're excited to share with you the latest updates and improvements to our platform. Here's a summary of what we've been working on this week:

🐞 FIXED

We've resolved reported issues that were causing occasional crashes when, for example:

Modules' catalog in Brainboard.


  1. Storage Container already exists issue:
    • Problem: When creating a new Storage Container in Brainboard, if the container already exists in AWS or Azure, the application would fail.
    • Solution: We have implemented a check that verifies if the container already exists in the specified cloud provider before attempting to create it. If the container already exists, Brainboard will no longer fail and will instead display a message indicating that the container already exists.
  2. Git Personal Token Editing Error:
    • Problem: When editing only one field in the Git Personal Token, an error occurred and the changes were not saved.
    • Solution: We have identified the problem and fixed the issue with the Git Personal Token editing process. Users should now be able to edit any field in the token without encountering errors.
  3. Terraform Block Removal:
    • Problem: When importing Terraform files, such as backend.tf that contains a Terraform block and many providers block, the Terraform block was automatically removed.
    • Solution: We have identified the problem and fixed the issue with the Terraform block removal during import. The Terraform block should now be retained and not removed during the import process.
  4. Map variable syntax issue:
    • Problem: When importing a Terraform file that contains a map as the type of variable and the values are defined in terraform.tfvars, the values were changed and replaced with an invalid Terraform syntax, causing the plan to fail,
    • Solution: We have identified the problem and fixed the issue with the map variable syntax. The values should now be imported correctly and retain their original syntax.
  5. Validation Block Import:
    • Problem: When importing from Git or files, for example, a Terraform code that contains a validation block, the variables validation block was not imported in Brainboard.
    • Solution: We have identified the problem and fixed the issue with the validation block import. The variables validation block should now be imported correctly and be visible in Brainboard.
  6. Terraform Variables Modal:
    • Problem: The Terraform variable modal was changing every time it was opened or when doing a pull request. This caused confusion and made it difficult to track changes.
    • Solution: We have made changes to the Terraform variable modal, so it will no longer change every time it is opened or when doing a pull request. This will make it easier to track changes and manage variables.
  7. Default Terraform Code File:
    • Problem: The default Terraform code file was main.tf, but it was causing confusion when working on a different resource file.
    • Solution: We have changed the default Terraform code file to be the resource file that the user is currently working on. This will make it easier to manage multiple resource files and keep track of changes.
We apologize for any inconvenience this may have caused, and thank you for bringing it to our attention.
Please note that the above issues have been fixed in the latest version of Brainboard and should no longer occur. If you continue to experience any issues, please reach out to our support team on our Public Slack Channel.

🧼 IMPROVED

  1. Terraform Code Generation: We have made significant improvements to its Terraform code automatic generation process, making it 2x faster and more reliable. By optimizing the code generation algorithms, Brainboard has made it possible to generate Terraform code from diagrams in a fraction of the time it used to take. Additionally, the code generated is more reliable and maintainable for the long term. The generated code is now more readable and easier to understand, making it simple to read changes and updates. The new generation process also includes a new error checking feature, which identifies and corrects errors before the code is generated, ensuring that the generated code is error-free. Overall, these improvements make Brainboard's Terraform code generation process one of the best in the industry, providing users with a fast, reliable, and maintainable solution.
  2. CI/CD Plugins: We have added more available arguments and options for CI/CD plugins. This will give users more flexibility and control when integrating with their CI/CD pipeline.
This should result in faster load times and a smoother user experience.

As always, we value your feedback and suggestions. If you have any thoughts or ideas on how we can improve Brainboard, please don't hesitate to reach out to our support team.

📆 Thursday, January 24th, 2022



Don't forget our live webinar on the details and implications of what CI/CD means for the cloud infrastructure:
  • The current state of CI/CD solutions and how they work
  • The challenges associated with it and how they impact your process
  • What are the best practices that apply to the infrastructure automation
  • What changes are needed to have a successful implementation
  • The most important part: what is expected from a CI/CD solution that is cloud infrastructure specific
🧼 Improved
13 days ago

🔁 Highlight the code per resource configuring

When working with Brainboard, users can navigate between the visual representation of their infrastructure (the "resource") and the code that defines it (the "configuration") in a seamless way. 

Before

When a user selects a node in the visual representation of their infrastructure, they may not know where in the code for that specific node is located. 

Now

When a user clicks on a resource in the visual interface, Brainboard solves this problem by automatically highlighting the corresponding section of code when a node is selected, making it easy for the user to find and understand the configuration for that node. This feature allows for more efficient and intuitive management of infrastructure.

For more information, check this video ⬇️
Highlight the code per resource configuring.mov 96.52 MB


One step forward in the bidirectional way of working the infrastructure - Design & Code - on Brainboard
🧼 Improved
13 days ago

⧮ Improve PR/MR* creation flow with clear error messages!

*
PR = Pull Requests
MR = Merge Requests

Brainboard's tech team has significantly improved the error messaging experience when performing pull or merge requests.

To accomplish this, we have changed the backend to provide more detailed and informative error messages. These error messages are now displayed directly on the front end, making it easy for you to understand and resolve any issues that may arise. We have also made improvements to the modal's User Experience (UX) to make it more intuitive and user-friendly. 

These enhancements will make it easier for you to manage and troubleshoot your code changes.


About

Merge requests (MRs) & pull requests (PR) in a version control system (VCS) like Git can save your cloud infrastructure project by allowing you to:

  1. Collaborate effectively with team members: PR/MR provide a way for team members to propose changes to the infrastructure codebase and review and discuss them with other team members before merging them into the main branch. This allows for better collaboration and communication within the team.
  2. Implement code review and testing processes: PR/MR provides a way to implement a code review process, where other team members review changes to the infrastructure codebase before being merged. This can help identify and fix bugs and issues before they are deployed to production.
  3. Track changes to the infrastructure codebase: PR/MR provides a way to track changes to the codebase, including who made the change and why making it easier to understand how the infrastructure has evolved.
  4. Rollback changes: PR/MR provides a way to roll back changes to the infrastructure codebase if something goes wrong. This can be done by reverting the merge commit or using version control tools like Git to revert specific changes.
  5. Isolate changes: PR/MR provides a way to isolate changes, meaning that changes are committed and tested in a separate branch before merging into the main branch. This allows for keeping the main branch stable and ready to deploy at all times.
  6. Implement automated testing and integration: PR/MR provides a way to implement an automated testing and integration process. This can be done by integrating the VCS with a continuous integration and deployment tool, which can run automated tests and deploy changes to different environments.

One step forward binary way of working the infrastructure on Brainboard
🧼 Improved
13 days ago

🔥 Id card is constantly improving

The ID card in Brainboard is a feature that enables users to easily configure cloud resources by dragging and dropping them onto the design canvas. These resources are not just visual representations but are actual, actionable resources that can be configured and deployed to the cloud. One step forward in breaking down the barriers between low-code and code-based approaches to cloud infrastructure management.

With the ID card, Brainboard is pushing the boundaries of visualizing cloud infrastructure to help you understand the bigger picture of your projects, environments, cloud architecture, and workflows. This makes it easier for users to manage your cloud resources and have a clear infrastructure overview. This can also help users to identify patterns, dependencies, and potential issues, making it easier to optimize your infrastructure.

Here at Brainboard, we constantly spot errors and improvements and focus on tackling them first. 
  • One of the improvements is that it eliminates missing fields when configuring specific cloud resources. You no longer have to worry about missing important information when setting up your cloud infrastructure. 
  • The ID card allows for multi-block everywhere, allowing for better customization options. This can be achieved by using hardcode, a powerful tool for making changes to the infrastructure. 

Overall, these improvements make it easier for you to configure and manage your cloud resources with Brainboard.
🧼 Improved
20 days ago

🌦️ Upgrade Terraform Providers

Cloud providers supported in Brainboard (AWS, Azure, OCI, GCP) were upgraded to its latest versions. 

Latest Terraform Providers' versions:  

AWS: VERSION 4.49.0
Azure: VERSION 3.38.0
OCI: VERSION 1.5.3
GCP: VERSION 4.48.0

For more information, check the official Terraform Providers registry.

🧼 Improved
about 1 month ago

≈ Variables in multi-region AWS diagram design

In Brainboard, this applied for all cloud providers supported (Azure, OCI, GCP, Scaleway)
You can now use variables in multi-region AWS diagram design :)

Terraform variables in Brainboard can be used to create a multi-region AWS diagram design in several ways:
  1. Use variables to define the regions you want to deploy your infrastructure in: By using Terraform variables; you can specify which regions you want to deploy your infrastructure in and make it easy to change or add regions in the future.
  2. Use variables to define the specific resources in each region: By using Terraform variables, you can specify the specific resources you want to deploy in each region. This allows you to create different resource configurations for different regions easily.
  3. Use variables to define the AMI ID: By using Terraform variables, you can specify the AMI ID (Amazon Machine Image) you want to use in each region. This allows you to use different AMIs for different regions.
  4. Use variables to define the subnets and availability zones: By using Terraform variables, you can specify the subnets and availability zones that you want to use in each region. This allows you to use different subnets and availability zones for different regions.
  5. Use variables to define the security group: Terraform variables can specify the security group you want to use in each region. This allows you to use different security groups for different regions.

Here is an example of how you can use Terraform variables to define a variable for the region:
variable "region" {
  default = "us-west-2"
}

You can use this variable in your resource definition like this:
resource "aws_instance" "example" {
  ami           = var.ami
  instance_type = "t2.micro"
  region        = var.region
}
🧼 Improved
about 1 month ago

🔐 We improved web socket* error handling in the CI/CD Engine!

All-in-one


Improve the error handling in the CI/CD (Continuous Integration/Continuous Deployment) engine of Brainboard. Specifically, the improvement is related to the handling of errors that occur during the use of web sockets.
*Web sockets are a technology that allows for real-time, two-way communication between a client and a server over a single, long-lived connection. In the context of CI/CD, web sockets may facilitate communication between Brainboard's CI/CD engine and other system components, such as the version control repository or the deployment pipeline.
The improved error handling in this feature ensures that any errors that occur during web sockets are handled more effectively, allowing a seamless CI/CD process to continue functioning even in the event of an error.
🧼 Improved
about 1 month ago

🔏 Single Tenant*

A brand new Single Tenant version with CI/CD included and up-to-date versions is available for enterprises.
Please contact us if interested.
*Single tenant refers to a software as a service (SaaS) solution where each customer or client has their dedicated instance of the software running on a separate infrastructure. This contrasts with a multi-tenant SaaS solution, where multiple customers or clients share the same software instance, running on a shared infrastructure.


In a single-tenant SaaS solution, the customer's data and configuration are isolated from other customers and not shared with any other organization. This provides a higher level of security, compliance, and customization. Customers have more control over their data, and the software can be tailored to the customer's specific needs.


Single-tenant SaaS solutions are typically used by larger organizations with more stringent security and compliance requirements or organizations requiring a high level of customization. They may also be used by organizations with sensitive data that they do not want to share with other organizations.


It's important to note that Single tenant solutions are often more expensive than multi-tenant solutions because the hardware and infrastructure costs are spread across fewer customers. Additionally, because each customer requires its own infrastructure, there are more operational costs to manage and maintain the different instances.
🧼 Improved
3 months ago

The template catalog is on prod 🚀

One feature that enables engineers to create repeatable templates of cloud architectures is using infrastructure as code (IAC) tools such as Brainboard.


Brainboard is a tool that allows you to define, provision, and manage infrastructure as code. You can use Brainboard to create templates, called modules, that define specific cloud architecture patterns and configurations. These modules can be shared with other team members, allowing them to use the same templates to provision and manage their own infrastructure.


With Brainboard, engineers can create repeatable templates. These files can be version controlled and shared through various means, such as Git. This allows other team members to view, use, and modify the templates, making it easy for them to spin up similar infrastructure quickly.


Brainboard allows you to use variables, which can be defined in a separate file (tfvars) or passed through the command line, making it easy to parameterize the templates and adjust them to specific use cases or environments.

🧼 Improved
3 months ago

🔐 We are SOC2 compliant. We'll be certified in few week

We are happy to announce that we are working very hard in getting SOC2 certified.

In the meantime, we are SOC2 compliant.

A glimpse of our security.

soc2.png 66.66 KB
🧼 Improved
4 months ago

💣 Import from Microsoft Azure (public)

This summer, while many were enjoying their vacations, the development team at Brainboard was hard at work. They were focused on enhancing every aspect of the platform, and one of the most highly-anticipated features was the ability to import from Azure, now available to the public.

Introducing Import Azure

To celebrate this new feature, we are excited to offer you 50 free credits to import 50 Azure cloud resources and transform your Azure infrastructure into Terraform code and a live diagram. If you require additional credits, please don't hesitate to let us know. We are here to help you every step of the way.
🧼 Improved
4 months ago

✏️ Design to Code

The transition between design and code has been made easier, more responsive and more flexible. Cloud resources can be opened and closed to focus on designing the architecture diagram and Terraform code can be opened and closed to focus on configuration. This new feature was recently developed by our front-end experts and I was impressed with it after trying it out. It's truly amazing and I wanted to share it in this month's newsletter. Try it out for yourself!


Discover the new Design to Code area on Brainboard.
🧼 Improved
4 months ago

🔥 Switching tabs

🧼 Improved
4 months ago

🚀 Code to Deploy

Brainboard have made significant improvements to the process of configuring cloud resources, specifically in regard to the identification and management of each resource. This is an essential task when building an architecture diagram, and we recognized the need for a more streamlined and efficient approach.

We have completely redesigned the concept of configuring a cloud resource, with a focus on simplifying the process and reducing the number of steps required. This has been achieved through the integration of more advanced automation techniques and the use of more intuitive user interfaces.

In addition to this, we have also made improvements to the design to code feature, which allows for a more seamless transition between designing the architecture diagram and configuring the relevant code. The combination of these two features results in a much smoother overall experience for the user.

I have personally tested these new features and can confidently say that it is a significant improvement from the previous version. I highly recommend giving it a try for yourself and see the difference.

Design to Code within the hour on Brainboard.
id-card.gif 716.25 KB
🧼 Improved
4 months ago

🖼 Use your own icon for any resource

This feature release pertains to the new id card that has been introduced in the Brainboard cloud management solution. With this new feature, users are now able to directly edit the icon of any resource when configuring it.

To do this, the user simply needs to hover their cursor over the existing icon and a prompt will appear, allowing them to upload a custom icon. This feature allows for a greater degree of customization and organization when building and managing architecture diagrams within Brainboard. Additionally, it gives users the ability to easily identify resources in diagrams by custom icons.

Start configuring your cloud resources with Brainboard.

Edit the resource's icon from the id card directly.
🧼 Improved
4 months ago

🪄 Import from files improved

This feature release pertains to the import feature in the Brainboard cloud management solution. The development team has been working on improving the user experience and the output of this feature.

A new and improved version of the import feature has just been released. With this new version, users are now able to start configuring their cloud resources while they are dragging and dropping them onto their architecture diagram. This means that users no longer have to complete the configuration process after the resources have been imported, they can now do it in real-time as they are adding resources to the diagram. This allows for a more efficient and streamlined workflow, and can save users valuable time.

The team is encouraging users to try out this new feature and provide feedback on their experience with it. This will help the team continue to improve the product and provide the best experience for the users.

 
Import your Terraform files on Brainboard.
Import from terraform file(s)
🧼 Improved
5 months ago

🌈 UX redesign - idcard

This feature release pertains to the redesign of the id card in the Brainboard cloud management solution. The development team has completely rethought the concept of the id card to improve productivity and readability for the users.

The new id card has been redesigned with the goal of providing a more efficient and streamlined workflow when configuring cloud resources. One of the key changes is that users can now start configuring their cloud resources while they are dragging and dropping them onto their architecture diagram. This eliminates the need to switch back and forth between configuring resources and adding them to the diagram, allowing for a more efficient workflow.

In addition to this, the new id card has been optimized for smoother readability. This includes improvements to the layout, typography, and color scheme. The new design is intended to make it easier for users to quickly and easily identify the relevant information for each resource, which can save valuable time when building and managing architecture diagrams.

The new id card also includes advanced automation techniques and more intuitive user interfaces which makes the overall process of configuring cloud resources faster and more user-friendly.


Overall, the redesign of the id card is aimed at improving the productivity and readability of the Brainboard cloud management solution, and providing a better experience for the users.

Start configuring your first resources on Brainboard.

id-card.png 107.04 KB
🧼 Improved
6 months ago

🔐 Manage auth with Keycloak*

*Keycloak is an open-source identity and access management solution. It is designed to provide a centralized location for managing user authentication and authorization. Keycloak provides features such as Single Sign-On (SSO), user management, and access control for applications and services.
The feature being mentioned in the statement is the integration of Keycloak with Brainboard, a cloud management solution. With this integration, users of Brainboard have the ability to use Keycloak as the authentication system for their Brainboard account. This allows users to use their Keycloak credentials to log in to Brainboard, rather than having to create and manage separate login information.

By using Keycloak as the authentication system, Brainboard users can take advantage of Keycloak's advanced security features and user management capabilities. This can improve the security of the Brainboard platform and make it easier for users to manage access to their cloud resources.

In summary, the integration of Keycloak with Brainboard allows users to use Keycloak as the authentication system for their Brainboard account, which improves security and user management capabilities.
🧼 Improved
6 months ago

♦️ idcard - Multiple time the same block

  • You have the ability to add blocks easily
  • You have the ability to use multiple time the same block 
  • You have the ability to upload files in the idcard
  • ALL lifecycle are supported

🧼 Improved
6 months ago

📥 Import templates

✅ Import templates that you or your team have created into the same design and combine them to create complex architectures and use-cases 😱 The Terraform code is instantly & automatically created.

👉 In this video:
clone-in-arch.mp4 29.19 MB

- I was creating an #AWS bastion
- Then I added a serverless stack to it
- I also added a layer of a landing zone
All in the same design...and I can keep building it this way.

😍 Turn your complex workloads into a collaborative diagram + code where anyone in your team can understand it & work on it without pain.

👉 The future is already here: https://app.brainboard.co
🧼 Improved
6 months ago

Weekly W29 🔥

Here is the summary of what we released:
  • Split nodes into different files
  • Import tfstate now is automatic and part of importing files
  • Remove credentials in the module source URL -> security improvement
  • Clone templates in the same architecture
  • Fix graphical bugs to make the user experience enjoyable
  • Allow emoji / any char in names (architecture, env, team, ...)
🧼 Improved
7 months ago

⏳ Improve Bitbucket support

We added git integration (Push to GIT) but now we also need to support Bitbucket in:
  • Import module
  • Import from GitHub/GitLab/…
  • Everywhere else we support GitHub/AzureDevops
🧼 Improved
7 months ago

🎸 Improve Bitbucket support

We added git integration (Push to GIT) but now we also need to support Bitbucket in:
  • import module
  • import from GitHub/GitLab/…
  • Everywhere else we support GitHub/AzureDevops
🧼 Improved
7 months ago

🗂 Predictable TF code

When pushing the code into Git, users expect and will have a predictable Terraform file.
Adding a creation order allows having this predictability as the new resources will be always at the end of the file.
It’s confusing now with the code and design in the same tab to not understand where are the new resources added.
🧼 Improved
7 months ago

🛟 Auto save idcard

We noticed that users often forget to click on apply so they lose their changes.

Making editing the ID card saves the configuration automatically without clicking on the apply button. 
We also give the possibility to cancel/roll back the changes if the user wants it.
🧼 Improved
8 months ago

⛪️ Block non-desktop devices

You won't have access to the sign-up page and the app for non-desktop users.
You will be able to provide your email to be reminded. 


🧼 Improved
8 months ago

👔 Add custom module icon

You can now specify your module icon for the leftbar
🧼 Improved
8 months ago

♻️ Frontend reload system*

*Frontend reload system refers to a technology that allows for automatic updating of the front-end (client-side) of a web application. It is used to ensure that users always have the most recent version of the application, without the need for manual updates.
The feature being mentioned in the statement is that Brainboard, a cloud management solution, has implemented a frontend reload system. This means that when updates are made to the application, the frontend of the application will automatically reload and update to the newest version. This ensures that users are always working with the most recent version of the application, which can improve the stability and security of the platform, and provides users with the latest features and improvements.

One of the advantages of this feature is that it eliminates the need for users to manually update their application, reducing the chances of errors and downtime. It also makes it easier for the development team to roll out new features and bug fixes, as users will receive them automatically, without the need for manual intervention.

In summary, the frontend reload system is a technology that allows for automatic updating of the front-end of a web application, ensuring that users always have the most recent version of the application, and making it easier for the development team to roll out new features and bug fixes. Brainboard has implemented this feature, which ensures that users always have the newest app version.
🧼 Improved
8 months ago

🚚 Add Locals

  • The locals part is added at the end of the variables table 
  • Only name, scope, value, and description are used and visible 
  • The description should be a comment before the local in the generated Terraform file
🧼 Improved
8 months ago

🔄 Synch Architectures

You can replicate with an automatic sync the same diagram in different environments.

This is useful in cases where you want to have the same architecture diagram on multiple environments: dev, staging, and production... and any graphical change you make to either environment will be automatically replicated into the other ones.

To do it, click on the switch of syncing architectures in the cloning wizard as follows

🧼 Improved
8 months ago

🗃 Import modules from files

Allow users to add modules via files upload

1️⃣  Click “+” to add #Terraform modules
2️⃣  Choose “From files” under the source
⚠️ One or multiple modules are supported
3️⃣ Add a custom icon


🧼 Improved
8 months ago

🙌 Team Management

  • Ask a mandatory team to invite member
  • The default team is Admin on the default project
  • UX improved for project create/update 
🧼 Improved
9 months ago

🌐 Remote backend per architecture

Allow the user to change the remote backend setting at the architecture level.
ℹ️ For users/clients that want to manage multiple clients over multiple clouds and use a dedicated remote backend per client.

Remote Backend.png 205.83 KB
🧼 Improved
9 months ago

✌️ New Sign up / Sign in

🧼 Improved
9 months ago

🌸 Architecture selector

Manage your projects, environments, and architectures in a whole new way!
https://youtu.be/VPP1-1aKVIU
Brainboard - The architecture selector .mp4 9.64 MB

🌸 Architecture selector
🧼 Improved
9 months ago

New pricing 💰

Optimized to manage your Multi-Cloud Architectures, Terraform Environments & Teams as never before!
How to Set-up your payment in Brainboard?

Brainboard Pricing
🧼 Improved
9 months ago

👁 Set Terraform provider’s setting

Allow you to add custom CP settings

Example of setting you can add in this block: 
Customize Terraform CP provider.mp4 3.36 MB


This feature is mainly for users that won’t deploy within Brainboard but already have their git and some TF provider settings.

Custom Terraform provider
🧼 Improved
10 months ago

🗯 Resource tab

🧼 Improved
10 months ago

☁️ Latest CP versions

NB. For both AWS and Azure it’s a major version release so please check the upgrade guide!

🧼 Improved
10 months ago

🦮 Guided Tour

We updated your onboarding process to include more explanation materials at first login, accessible anytime, directly from your interface. We’ve also launched a brand-new tutorial gallery so that anyone can learn how to build their cloud architecture, more efficiently.

Enjoy 🤩

🧼 Improved
11 months ago

🤑 Pricing: starter with 14d trial on signup

Introduction of a 14-day Pro trial for all new sign-up users! 
Screenshot 2022-03-04 at 12.54.28.png 177.41 KB
🧼 Improved
11 months ago

✚ Start in 4 ways with Brainboard

🧼 Improved
about 1 year ago

🔗 ☁️ Import Terraform V02

This feature is a tool that allows users to import Terraform, a tool used for infrastructure as code, and manage it visually. We've been collecting feedback from users since its release last month and has been making improvements and releasing new versions daily. 

Reverse Terraform is a feature of Brainboard that allows users to automatically generate Terraform diagrams and code from an existing Terraform file, a public or private repository, and connect to their cloud provider's credentials. This feature enables users to create visual representations of their infrastructure and quickly understand the relationships between resources, as well as generate Terraform code for those resources, making it easier to manage and maintain their infrastructure. Additionally, by connecting to cloud provider credentials, Brainboard can also pull in information about existing resources and use that to generate the Terraform code, allowing users to easily import their existing infrastructure into Terraform.

The new versions include features such as: 
  • Private Repositories (Only GitHub): This fix allows users to connect to their private GitHub repositories and import their Terraform code. This is useful for users who want to keep their infrastructure code private and only accessible to authorized users.
  • Supports count, timeouts, depends_on (add connector with the dedicated connector.link.type): This fix enables the tool to support count, timeouts, and depends_on Terraform resources, which are used to create multiple instances of a resource, set timeouts for resources, and specify dependencies between resources. The tool also allows users to add connectors with the dedicated connector.link.type.
  • Supports terraform functions (like format, substr, ...), string interpolation (like “aaa$[var.test]”): This fix enables the tool to support Terraform functions, such as format and substr, and string interpolation. Terraform functions are used to perform various operations on strings and variables, while string interpolation allows users to include variables within strings.
  • Some resource attributes not parsed: This refers to an issue where some resource attributes were not being parsed correctly by the tool. This fix addresses this issue, ensuring that all resource attributes are parsed correctly.
  • Create module idcard on the fly: This fix allows users to create module idcards on the fly. A module idcard is a summary of a module's inputs, outputs, and resources. This allows users to quickly understand the purpose and structure of a module without having to examine its code.
  • Import code with module fails: bad source, no version: This refers to an issue where importing code with modules would fail if the source or version was not specified correctly. This fix addresses this issue, allowing users to import code with modules correctly.
  • Git root/base repo URL doesn't work: This refers to an issue where the git root or base repo URL was not working correctly. This fix addresses this issue, ensuring that the git root/base repo URL works correctly.
  • Support EOF in resource attribute: This fix enables the tool to support EOF in resource attribute. EOF, short for End-of-file, is a control code used to indicate the end of a file or stream. This fix allows the tool to correctly handle EOF in the resource attribute.

Migrate your cloud infrastructure on Brainboard for a better process standardization. 

import your tf code .gif 1.69 MB
🧼 Improved
about 1 year ago

Variables & outputs 🔥

It's now possible to flag variables as secrets and that is also reflected on the generated Terraform code. Also, you can define outputs in Brainboard, use them and/or push the outputs.tf files into your Git repo.
Screenshot 2022-03-04 at 13.05.48.png 6.42 KB
🧼 Improved
about 1 year ago

Multi-credentials 👥

Last week, you discovered our new pricing plan, based on the number of users. You are not limited to the numbers of Infrastructures you or your team will create. Now, you'll be able to add multiple credentials for every cloud provider, especially matching: Cloud Provider = Credentials <> Project.

Screenshot 2022-02-04 at 11.08.16.png 65.87 KB
🧼 Improved
over 1 year ago

Multiple versions of cloud ☁️ providers providers

As you all know, Cloud Providers update their resources very regularly. Now, we are thrilled to announce that, starting today, you'll be able to use the newest version or/and switch from older to newest.
🧼 Improved
over 1 year ago

Clone architecture between environments ✚

With Brainboard, you can clone architecture between environments, within your organization. 
🧼 Improved
over 1 year ago

Add native versioning (like git) ✚

A native format, in the context of software applications, refers to the file format which the application is designed to work with. 
🧼 Improved
over 1 year ago

Add Terraform remote backend on S3 🧑🏻‍💻

The remote backend stores Terraform state and may be used to run operations in the Terraform Cloud.
🧼 Improved
over 1 year ago

Add contact support 🦸

Directly onto the Brainboard platform, you can now chat with our support team. 
The chat support is also available on the website and the documentation.
🧼 Improved
over 1 year ago

Add billing 🧾

In your management platform, you can add your billing info and upgrade to any plan, in just a click.
🧼 Improved
over 1 year ago

Restore any point in time version 🕰

With Brainboard, you can restore your infrastructure in any time version. 
🧼 Improved
almost 2 years ago

Multi-user edition 👥

Brainboard is provided in both single- and multi-user versions.
🧼 Improved
almost 2 years ago

RBAC System 🔒

Organize and manage your infrastructures into projects and environments within your organization.
Use some predefined RBAC roles to restrict accesses.
🧼 Improved
about 2 years ago

Sync architectures 💠

The synchronization process compares your local Designer workspace, the remote Decision Center database, and a reference that computes the state of the synchronization. This reference state is created as a connection entry in your workspace when you connect to Decision Center.