As we move into the second week of May, we're turning the spotlight on your organization—literally. This release supercharges the relationship graph, making it smarter, cleaner, and more navigable. With dynamic root selection and a decluttered view, you can now effortlessly explore any part of your org and uncover meaningful connections. Combined with performance and security upgrades across sessions, recipes, and deployments, this release delivers clarity, control, and confidence.
As usual if you have any questions or want to connect, join our Slack community, book time with our team, or reach out on LinkedIn, X, or BlueSky.
Spotlights
Explore Your Organization Like Never Before
The Graph just got smarter — and more navigable. We’ve made key upgrades that make it easier to travel through your org’s structure, discover hidden links, and stay focused on what matters.
What’s new:
Dynamic Root Selection: Jump into any part of the graph — now you can start from any node and explore outward.
Decluttered View: Inactive and unpublished data is now filtered out, so your graph stays clean and relevant.
Smarter Structure: We’ve improved how the graph arranges itself, making patterns and connections easier to see.
Always-On Root: No more getting lost — there’s always a clear anchor in view.
Ready to travel through your organization’s data like a map? Dive in and discover the relationships powering your systems.
Improvements & Bug Fixes
Security
Advanced session checking middleware has been implemented to further secure your interactions with our applications.
Graph Updates
We've made significant enhancements to our backend services, including how our graph database is structured and maintained. This means more reliable and faster data processing.
Resource nodes now more clearly display their type and associated application information, both on the node itself and in tooltips.
Recipes, Projects, Deployments
Fixed resource project view. The sidebar for resources now accurately displays only published and active projects.
We’ve corrected an issue where search results involving both numeric and string sort fields might not sort as expected.
