Issue No. 20 | May 2026 

In this issue, we dive into the transformative power of Agentic AI and its integration with Trimble Connect Workflows and File Service to turn massive datasets into actionable answers. We also highlight key infrastructure enhancements, including the rollout of enhanced regional API deployments in the Cloud Console and the launch of the Platform-AI-Toolkit to provide better context for our AI tools. Rounding out this month’s updates are important security upgrades for Trimble ID and a "vibe coding" session with Modus and the new Modus MCP servers.

🧠 AI in Connect Workflows

Trimble Connect Workflows is evolving and taking the lead in the AI space. Our goal is to make it easier than ever to design workflows and orchestrate tasks that effortlessly achieve your goals. Check out the video below to see the difference in action: we walk through a real-world use case using a standard low-code/no-code approach, and then show you how AI tackles that exact same challenge.

Watch the video on Charlie:

🚀 Enhanced Regional API Deployments in Cloud Console

The API Cloud Platform team has rolled out an enhancement to API deployment workflows in the API Cloud Console. API providers can now deploy a single API version across multiple regions with a simpler and more flexible experience.

Read more on Charlie:

File Service and Agentic Platform partners to create a Single Powerful AI Platform

File Service stores billions of customer files across Trimble — the single largest footprint of customer data in our industry. The Agentic AI Platform powers the orchestration layer that turns data into answers. Separately, each is powerful. Together, they are transforming what Trimble AI can offer.

Watch the video on Charlie:

Evolving the SDLC: AI-Native Evolution in the Trimble Platform Organization

We believe that a major factor in AI productivity is context—AI tools are only as effective as the information they have about our specific services. To assist with this, we’ve launched a Platform-AI-Toolkit in the trimble-oss GitHub organization.

Read more about this exciting initiative on Charlie:

🌊 Vibe coding with Modus

Last week I sat down with Mitch Ray, senior product manager for Modus, and explored vibe coding Modus based apps with the Modus MCP server. Let us know what you think of this podcast style approach, we'll refine and improve as we make more of these. Enjoy!

Watch the video:

📅 UPCOMING EVENTS

App Xchange: Agent V2 for Vista

The App Xchange Agent is being upgraded to Version 2 for Vista, along with enabling the Connections feature. This process will be completely automated for current Vista customers using the V1 agent.

Staging - coming soon

Production - coming soon

Trimble ID: Region selection guidance during new-user creation

Trimble ID (TID) is enhancing the region selection step during new user creation. This improvement aims to better guide users, featuring updated instructional text and a link to new help documentation.

Staging - May 21, 5:30 AM UTC

Production - May 26, 5:30 AM UTC

Trimble ID: Upcoming Security Update - Enhancing Our Encryption Standards

As part of Trimble ID’s (TID) commitment to elevated security standards, TID is upgrading its secure connection protocols.

The CloudFront security policy is being updated from TLSv1.2_2019 to TLSv1.2_2025. This enhancement ensures that all connections to services utilize the most modern and robust encryption ciphers available, protecting your data against evolving cyber threats.

Staging - May 6, 5:30 AM UTC

Production - May 24, 5:30 AM UTC

🚨 DISASTER RECOVERY

Profiles: Disaster Recovery Drill in Staging

Profiles will conduct a Disaster Recovery drill in Staging on May 12, 2025, between 2:30 am UTC and 6:30 am UTC . During the DR drill, the integrators using our staging environment will experience downtime/disruption while switching from Primary to Secondary region and vice versa . A rollback is in place in case of any issues.

Staging - May 12, between 2:30 AM and 6:30 AM UTC

🚀 RELEASE NOTES

🛡️ Trimble Identity

April was a busy month for Trimble Identity, highlighted by the wide-scale activation of the redesigned MFA workflows, major security compliance upgrades, and infrastructure refactoring.

MFA & User Experience Redesign

• Redesign Activation: Feature flags are now active across both the backend and UI (Login and MyProfile), fully launching the redesigned MFA workflows.
• Streamlined Login Navigation: Introduced a "More options" menu within login MFA prompts, backed by new logic to handle alternative authentication methods.
• Passkey Security: Removed the "Skip" option for recovery codes during first-factor Passkey logins to enforce a stronger security posture. Rate limiting was also added to Passkey workflows to prevent abuse.
• Localization & Copy Updates: Implemented full translations for the MyProfile redesign, native user sign-in errors, and new MFA management emails. The Cookie Policy link and TOTP Recovery Code page titles were also updated.

Security & Compliance

• FIPS Compliance: Enabled FIPS compliance for AWS CloudFront and API Gateway to meet stringent federal security standards.
• Certificate & Config Maintenance: Completed the annual mTLS certificate rotation for APICloud and removed expired SAML certificates from the codebase.
• Token Hardening: Added DPoP (Demonstrating Proof-of-Possession) support for third-party token store integrations to better secure token exchanges.

Architecture & Infrastructure

• Centralized Configuration: Shifted critical settings (like User Throttling and Data Portability variables) out of Lambda environment variables and into a centralized database.
• New Relic Rollout (Phase 1): Initiated a transition to New Relic monitoring, enabling it in Staging and deploying it to Production (currently dark behind a feature flag) alongside legacy logs.
• Code Optimizations: Completed the first phase of the UI Backend Refactor (focusing on Email Management) and optimized log handling for "MFA Correction" events.

API Cloud

April was a high-impact month for API Cloud, centered on the rollout of regional deployment standards, enhanced validation tools, and a shift toward Agentic AI.

Multi-Regional Deployment & Standards

• Regional Infrastructure: Deployed Cloudfront domains across all supported regions and implemented logic to derive gateway URLs based on regional deployment details.
• UI Enhancements: Updated the Regional Standards UI and added visibility for regional consumption endpoints to improve transparency.
• Linting & Compliance: Introduced support for multi-version specification linting. All published APIs have been re-evaluated against the new v2026.1 API Standards.
• Deployment Controls: Implemented restrictions to prevent redundant regional deployments across different providers.

Security & Infrastructure

• mTLS Rotation: Completed self-signed mTLS bundle certificate rotations across Dev, QA, Stage, and Production environments.
• Cost Optimization: Transitioned Lambda@Edge log groups to "infrequent access" to reduce operational overhead.
• Platform Maintenance: Officially deprecated the legacy API Management and Approval tabs.

Access Control & Intelligence

• New Administrative Roles: * Added a specific role for managing "Public" visibility status in the Developer Console.
• Introduced a dedicated role for TAM Policy updates.
• Agentic AI Migration: Migrated existing specifications from Trimble Assistant LLM techniques to more advanced Agentic AI frameworks.
• Notifications: Automated email alerts are now triggered upon new Product creation.

📂 File Service

The latest File Service update focuses on more granular access controls and expanded event tracking.

Enhancements

• Advanced Permissions: ContentManagers now have the authority to manage permissions directly on root folders.
• Version-Specific Sharing: The limitedViewer role has been upgraded to support sharing for specific file versions.
• Expanded Monitoring: Event service coverage has been extended to include Objects, providing better visibility into data actions.

Need to join the mailing list for this newsletter or know someone who does? Let us know by filling out this very short form: