As we’ve written about in the past, balena uses an “Intentional Work Framework” where we pitch our ideas to the team in the form of “bets” and try to select the ones that will be most impactful for the coming cycle.
SAML now available to all paid plans
Last summer we introduced Enterprise Single Sign-On (SSO) via SAML for our Enterprise users. During our recent cycle, we expanded the availability of this feature to all of our standard paid plans.
Balena achieves ISO 27001 Certification
We’re excited to announce that balenaCloud is now officially ISO 27001 certified! This cycle marked the end of a long journey towards certification but was also a big step forward in our dedication to building a comprehensive security framework, and a trusted, responsible, forever company.
Balena publishes a Trust Center
Although balena has always been committed to ensuring the confidentiality, integrity, and availability of our customer’s data, we had no public documentation of these efforts. This cycle, we introduced the Balena Trust Center which details how we protect customer information and comply with industry standards and regulations.
Documentation Improvements
We constantly evaluate our documentation for clarity and accuracy, so with that in mind, we completely updated the documentation for our NVIDIA Jetson flashing tool known as Jetson Flash. Since each Jetson device can have slightly different flashing instructions and steps, we broke out all 14 devices to their own page and added images and extra details to make them as clear as possible.
Documentation and client components updated to use API v7
In this cycle, not only did we release Balena API v7, a significant update that provided new features, improved error handling, and important changes to our API functionality, but we also updated our documentation and other components to consume this new API. These other components include our Python SDK, JavaScript SDK, the balena CLI, and the balenaCloud UI. (By the way, there is no rush to update to API v7; v6 and older clients will continue to work perfectly!)
Balena’s Move to Stripe
In this cycle we announced a significant upgrade to our billing infrastructure: our transition to Stripe, a trusted leader in the online payment and billing space.
External contributors enabled for balenaOS device types
In this cycle, we completed the conversion of balena-os repositories from Jenkins to Github Actions for CI/CD workflows. This means that external contributors to these repositories can now see why tests are failing and make any necessary changes. It also makes it easier to retry failing tests and is an important step towards making it easier to fork balenaOS repositories with the related CI pipeline intact.
Fleet load times and device statuses massively improved
We announced a major update to balenaCloud that delivers significant performance improvements for users managing large fleets containing tens of thousands of devices or more.
User Interface (UI) Spring Cleanup
As our UI has evolved over the years, occasionally one of our vigilant UI developers will notice a tiny issue that is too small to tackle on its own so it gets added to a list of things to work on later. Well, this cycle “later” finally arrived and we tackled over 30 of these items in an intense three day sprint.
That’s a wrap on our most recent development cycle! We look forward to sharing details about our next cycle in the coming weeks. In the meantime, feel free to reach out on our forums, add a feature request, or check out our balena Getting Started Guide.
The post balena cycle roundup – November 2024 appeared first on balena Blog.