Visually design and orchestrate your deployment workflows without a single line of code.
Connect your automation ecosystem with OPA, Infracost, Checkov, or Terrascan…
Centralize your custom automation strategies and remote-run deployments.
Execute, optimize and manage workflows for successful outputs.
One of the biggest added values in terms of deployment is that Brainboard manages the upgrades and maintenance of the supported plugins: Infracost, OPA…
During this summer, the development team wasn't on vacation. No no. They were working on improving every aspect of Brainboard. One, doubtfully the most awaited feature of it all: ✏️ Import from Azure (open to the public) We're offering you 50 free credits to import 50 Azure cloud resources and turn your Azure infrastructure into Terraform code and a live diagram. If you need more credits, let us know 🤫
Your experience with configuring each cloud resource with the id card just got revamped. We've completely rethought the concept of configuring a cloud resource, as it's an action you do repeatedly when building your architecture diagram.
I just tried it -- and combined with the new Design to Code mentioned above -- it's definitely a smoother experience.
Fixed: The location/Region field does not reflect the real value Fixed: Keep variables locals’ value during clone Fixed: The reminder form seems broken Fixed: Custom code field unusable Fixed: Architecture clone must keep the locals too Fixed: The deletion of modules from the catalog doesn’t always work
At Brainboard, we've worked hard to take your experience with the Cloud to the next level, especially while managing Git credentials in teams.
We've enabled you to:
As an individual contributor, you can add personal git tokens for any supported git provider - Azure DevOps, Gitlab, Bitbucket - and specify the scope of the creds and have visibility on where they are used.
As the owner of the organization, you can add Github app integration and users perform git actions based on their authorization on Github.
What do you need to do:
The Git credentials of your organizations are assigned to the owner of the organization. So you need to add your personal token in order to do pull requests.
If you use GitHub, there is nothing to do. Your pull requests work as before.
Pull requests: Choose the git provider to use from the supported ones - Azure DevOps, Gitlab, Bitbucket, GitHub, and add the description, project, folder, and base branch within the service.
Modules: You can choose which git credentials you want to use to import your private modules and use them.
Generate your diagram from the terraform code: Choose the git credentials you want to use and import your existing terraform code.
Both categories, git apps and personal tokens, are available on the 'Account' configurations, here:
This new set-up capability enables the seamless performance of tasks without switching between accounts and re-authenticating accesses, and so work independently and well.
Fixed: When I delete my current architecture, the interface freezes / infinite loop with error in console
Fixed: When I add an Azure virtual network for e.g. and I remove a chip from tags, the interface resets, the code generated is completely broken and I have no way to open the resource again to fix it.
Fixed: We can’t change the selected TF file to another one (other group tf file, variables, outputs, …)
Fixed: When a user configure a block (set) then deletes all the value the block is generated empty.
Fixed: Subnet IDs double added
Fixed: Automatically generate the connectors between resources when I reference an existing resource.
Fixed: when I connect, it shows the owner as an extra user
Fixed: With some attribute type like SelectList (array), changes do not trigger the TF code refresh
Fixed: Sign up page on Safari browser
Fixed: In the README modal, the save button doesn’t work at all, so if I write content it is automatically saved and there is no need for this button.
✅ 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.mp429.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.
When the same person connects from different tabs, Brainboard showed many times its Avatar in the top bar. Now, the connected users shows up only once.
SSOSingle Sign-On is an authentication scheme that allows a user to log in with a single ID to any of several related, yet independent, software systems. True single sign-on allows the user to log in once and access Brainboard services without re-entering authentication factors.
When I change the version of Terraform into a newer one, the backend prompts me to migrate the state. The version of Terraform is not updated in the frontend. To do my actions: plan, apply & destroy
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.
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
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.
🔥 Cloud architects, network architect & DevOps people build cloud infrastructures in a way that allow others to reuse their work with the minimum interaction possible → and if they use Terraform, they do it through modules.
✅ In Brainboard.co (YC W22), we allow you now to scale this workflow: - Import any module by just providing its source path
- You build your internal module's catalog 💪 you build your self-serve modules
- Combine modules to build cloud infrastructures that are aligned with your workflows 🔥
- Customize the icon of every module you import to make understandable diagrams 😍
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.
Information security is a reason of concern for all of us, and has been in our DNA and a top priority from day one.
With that in mind, we’re on our way to getting our SOC Certification 🔒
We strive to make our platform seamless and secure for all of our users and partners.
We’ve been working with Vanta to help achieve our #SOC2 certification.
We use Vanta’s automation platform to continuously monitor different security aspects across the organization, be it internal security controls, employee training, secure development, etc. against the recommended standards.
As per Terraform definition: Data sources allow Terraform to use information defined outside of Terraform, defined by another separate Terraform configuration, or modified by functions.
They are heavily used in architecture to reference and/or get information about a resource already deployed. Data resources could be
A common resource shared between multiple architecture
For security reason (read-only access)
Managed by another team
⚠️ Note that each provider may offer data sources alongside its set of resource types.
Turn your Terraform code into an actionable Diagram in seconds! 🎉
This feature is brand-new to the Brainboard app, enabling everyone to upload the Terraform .tf code and auto-generate a diagram. It eases migration into Brainboard.
Please note, this feature is new and will definitely be improved 🙂
Please don't hesitate to share your feedback, and we'll make sure to take it into consideration for further updates 😉
We've seen some of you needing to use Modules in your diagrams. With this feature, you are able to reuse any modules you find online / you create yourselves as a brick of reused codes directly from the Design brick of Brainboard. We made it easy to import, drag & drop and configure your modules directly on your dashboard. Let us know what you think 😇
We already had GitLab on our pool of integrated tools, and it's finally time to release GitHub!
With this new native integration, you can push your code (which is automatically generated by Brainboard once you design your infrastructure) to your trusted repository, GitHub or GitLab.
Brainboard continues to integrate your infrastructure with today’s workforce, without jumping your whole team into Gits.
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.png6.42 KB
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.
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.
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.
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.
