# Platform roundup: July 2025

Here's what's new in July.

We made several platform enhancements designed to improve your experience managing machines and data with Viam. Here's what's new this month.

## **Data region support**

We now support [specifying a data region](https://docs.viam.com/dev/reference/changelog/#data-regions-for-organizations), giving you control over where your machine data is stored. Combined with our recent ISO certifications and expanded EU presence, Viam provides enterprise-grade security and compliance for global deployments. To select your organization's configured region, go to Org Settings → Data Region, and select US or EU.

[Watch the video](https://www.youtube.com/watch?v=Nj7Qila45iE)

## **Add notes to your machine config**

You can now add freeform notes directly to resources in your machine’s config—including components, services, and even those defined in fragments. Leave reminders for yourself, explain the purpose of a configuration, or jot down alternative values to test later. Notes are saved with the config and visible to all machine owners, making collaboration and iteration easier.

## **Organize your configuration’s resources into folders**

You can now group components and services into folders within your machine’s config. Use folders however makes sense for your workflow—by component type, team ownership, physical layout (like “left arm” and “right arm”), or anything else that helps you stay organized. It’s a flexible tool to make complex machines easier to navigate.

## **No more outdated meta.json in cloud builds**

Based on user feedback and to help avoid mistakes or confusion, we've updated our GitHub build action to automatically run **viam module update** before starting a cloud build. This ensures that any changes to meta.json are reflected in the cloud.

## **Config resources statuses**

We’re giving you more insight into your machines. We now display resource configuration failures, making it easier to spot and resolve the root of any issue.

## **Capture DoCommand output as tabular data**

Developers can now  capture the output of [custom commands implemented via DoCommand](https://docs.viam.com/dev/reference/sdks/docommand/) providing enhanced flexibility for extending resource capabilities beyond API specifications. Select "DoCommand" as the resource's configured data capture method and provide your payload of choice.
