You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Today is a huge milestone for Compass - we’re officially in beta! Compass continues to evolve thanks to your continued usage, feedback and interviews, and since we moved to an open alpha our confidence that the need and desire for a product like Compass is stronger than ever before.
What does it mean to move to beta?
Compass moving to beta is all about confidence. Confidence within Atlassian that we’ve found something truly special with Compass, and a signal that we’ll begin our measured but eventual march towards general availability.
Moving to beta also means confidence for you, our users. Carrying an
alpha tag brings with it questions about the longevity of the product. Is Compass worth trying when we don’t know if Atlassian will stop investing in it? Should a team set up a pilot project if it’s unstable or not certified/compliant? By moving to beta we hope this helps answer those questions and more like it - yes, you absolutely should!
And for the record, Compass is both SOC 2 compliant and ISO 27001 certified
You’ll notice any mention of alpha replaced with beta throughout the product, but from a product perspective nothing about the way we’ve been building Compass and collaborating with you changes. We’re still committed to helping you understand and improve your distributed software architecture and building a world class developer experience for your organisation. And we want to build Compass with your help - this is a product for you, after all.
Where are we today?
Since our last update we’ve made significant progress across our three core areas. We believe many of our core capabilities are reaching a relatively stable, useful state and we see customers continue to expand the use of Compass across their engineering teams.
You can read more about product capabilities in our documentation and guides, but here are some highlights of what Compass can do today.
The component catalog helps you track all the software components your engineering team builds and operates. You can use the catalog to:
Create, import, and track different types of software components such as microservices or shared libraries, as well as data pipelines, machine learning models, websites, mobile apps, custom lambdas, APIs and much more.
Add custom data about those components using both manual and automated means with API access to everything you add. This gives developers an intuitive, unified interface to find the information they need to use a given component or operate it in a secure, compliant, and healthy way.
Search across this information using powerful filters and sorting to find groups of components or identify components that may require your attention. Smart Links in the Confluence & Jira editors make it easy to connect the dots across your tools and the pieces of your architecture it’s being applied to.
The DevOps health platform gives you a unique, scalable way to define, implement, and improve best practices across the entire software development lifecycle. This gives you a holistic view of the developer experience and helps you adopt a DevOps culture like moving testing, quality, and performance evaluations further left in your process. You can use this to:
Give each DevOps team their own dashboard, providing insight into the components they own and visibility into their health and how they can improve them.
Build custom scorecards to facilitate best practices and proactively manage component health and reduce incident severity and frequency
Let Compass aggregate data and give your teams a weekly update they can use to review the operational status of owned components through our new CheckOps ritual.
The extensibility engine gives your engineering teams the control and flexibility they need to invest in and customise their developer experience. From workflow to tooling we know every company is unique and that’s why Compass was built to be developer friendly from Day 1. You can use this to:
Access all the capabilities and data within Compass through our public GraphQL API, no ‘internal only APIs’ in sight. Automate as much as you want or wire up to your own custom toolchains.
Leverage Forge, Atlassian’s serverless app development platform, to build fully-functional apps in a few hours and extend Compass.
Integrations with Bitbucket, GitHub, Swimm, Swagger, CircleCI, and more available out of the box, making it easy to get started and automatically populate data. For example, the Bitbucket and GitHub apps automate key metrics such as Open Pull Requests, PR Cycle Time, or Deployment Frequency for any given service with a repository tied to it.
Over the next 6-12 months we will continue our focus on helping solve the painful and complex problems customers are facing with their distributed software architecture and the teams that collaborate on them.
We’ll continue to improve on the 3 core areas and explore a few exciting new ones we can’t quite share yet (but stay tuned!). In the immediate future we’ll be working on search and dashboard improvements, more integrations, and providing teams a single, holistic place to build and operate the components they own. Other highlights include:
Scorecard improvements: Adding customised data to scorecards, improving the global view to quickly find under-performing teams & components, and UX improvements to create and manage scorecards at scale effectively.
Component overview re-design: We’ve added a LOT of new information to the component overview since we launched, so we’ll be making improvements to make it easier to understand and use.
CheckOps improvements: Automating and aggregating the information your engineering teams need to make sound judgements and keep your architecture in a healthy state continuously. This means adding metrics, events, changes to components, highlighting outliers, improved actions, and notifications.
How much will Compass cost?
Compass will remain completely free to use as we move to beta and build confidence on our way to GA. Many of you have been asking about pricing and we have an early look at how we're thinking about pricing here: An early look at Compass pricing
We’re just getting started
We’re excited to reach this new beta milestone and confident that Compass can help you build, customise, and deliver a world-class developer experience so that all of your engineers are happy, productive, and creative!
Look out for more updates here in the community and don’t hesitate to contact us if you have feedback or need advice. Looking to implement and rollout a new security scorecard? Want to track key metrics across your microservices? Want to talk team structures and ownership? We’re here to help!
3 accepted answers