Rely.io
  • 📌What is Rely.io?
  • 💡How Rely.io works
  • 📑Getting Started Guide
    • Create an account for your organization
    • Add your first plugin
    • Import services into the Service Catalog
    • Make the Software Catalog your own
    • What's Next?
  • 🌈Basic Concepts
    • Entities
    • Blueprints
    • Property Data Types
    • Catalogs
    • Data Model
    • Plugins
    • User Blueprints vs Plugin Blueprints
    • Actions and Automations
      • Automation Rules
      • Self-Service Actions
    • Home Pages
    • Scorecards
  • 📚Guides & Tutorials
    • Enhancing Deployment Visibility through Gitlab Pipelines and Rely's API
  • 🖥️Software Catalog
    • Overview and Use Cases
    • Usage Guide
      • Creating a new Entity
      • Updating an Entity
      • Tracking Entity Changes
      • Customizing an Entity's Page
      • Customizing a Catalog
      • Creating a new Blueprint & Catalog
      • Updating a Blueprint
      • Tracking Blueprint Changes
    • Relevant Guides
    • Troubleshooting
  • 🥇Scorecards
    • Overview and Use Cases
    • Usage Guide
      • Creating a Scorecard
      • Updating a Scorecard
      • Evaluating Performance
    • Scorecard Examples
      • Production Readiness Scorecard Example
      • DORA Metrics Scorecard Example
      • Operational Maturity Example
  • 🎨Home Pages
    • Overview and Use Cases
    • Usage Guide
      • Creating a New Tab
  • ⚡Self-Service Actions
    • Overview and Use Cases
    • Usage Guide
      • Configuring your Self Service Agent
      • Managing your Actions Catalog
      • Self-Service Actions as Code
      • Running Actions
      • Tracking Action Runs
  • ↗️Plugins & Automation
    • What happens when you install a Plugin?
    • Self-Hosting Plugins using Galaxy
    • 🤖Automation Rules
      • Overview and Use Cases
      • Usage Guide
        • Creating an Automation Rule
        • Updating an Automation Rule
        • Tracking Automation Changes
        • Managing Automation Suggestion
    • 🔌Plugin Installation Guides
      • ⭐AWS
      • Bitbucket
      • ⭐Flux
      • GitHub
      • GitLab
      • ⭐Google Cloud Platform (GCP)
      • ⭐Kubernetes
      • ⭐OpsGenie
      • ⭐PagerDuty
      • ⭐Snyk
      • ⭐SonarQube
  • 🌐Public API
    • Audit Logs
    • Automations & Self-Service Actions
    • Automation Suggestions
    • Blueprints
    • Dashboards & Views
    • Entities
    • Scorecards
    • Self-Service Action Runs
    • Time Series
    • Users
    • Webhooks
  • ⚙️Invite Users
  • 🛡️Security & Compliance
    • Single Sign-On (SSO)
      • SAML with Google Workspace
      • SAML with Microsoft Entra ID
      • SAML with Okta
      • OIDC with Okta
      • OIDC with Google Workspace
  • 🏥Troubleshooting
  • ❓FAQ
Powered by GitBook
On this page
  • Leaderboards
  • Use Cases

Was this helpful?

  1. Scorecards

Overview and Use Cases

PreviousScorecardsNextUsage Guide

Last updated 7 months ago

Was this helpful?

Scorecards in Rely.io allow you to establish consistent standards for your services, helping you answer critical questions about your application as a whole. They simplify complexity and reduce firefighting, giving developers more time to focus on building new features. By customizing scorecards to reflect your organization’s priorities, you can ensure alignment on what matters most.

Why Scorecards? Operational efficiency has always been a priority for engineering teams, but with tightening budgets, it’s now essential. Bugs, security incidents, and unreliable services can slow your team down and divert resources from strategic initiatives. Rely.io helps you minimize these distractions by setting clear, measurable standards for your services, so you can focus efforts where they’re most needed and spend less time putting out fires.

How Scorecards Work -> Scorecards automatically assess entities against predefined criteria and assign a performance rank — bronze, silver, or gold — based on these evaluations. Each rank comes with specific rules, leveraging properties from across your tool stack to measure compliance and identify areas for improvement. For example:

  • Are teams meeting production readiness standards?

  • Are services aligned with DORA metrics and operational best practices?

  • Are on-call escalation policies and runbooks documented?

Drive engineering xxcellence with Rely.io's Scorecards, you can define and track KPIs and standards across various dimensions like quality, production readiness, and team productivity, fostering a culture of engineering excellence. By making these metrics visible, engineering leaders can:

  • Promote best practices: Easily share and track the adoption of organizational standards such as production readiness, operational maturity, and observability.

  • Encourage continuous improvement: Use Scorecards to assess, rank, and improve the maturity of services across teams, providing a clear path toward achieving top performance.

  • Streamline compliance monitoring: Automate compliance checks and gain visibility into how well services align with security, operational, and quality standards.

Watch a quick overview on how to use scorecards in Rely.io to define and track best practices across your organization 👇

Leaderboards

Once you set up a scorecard, you're already halfway there. The other half is ensuring teams and team members actually follow the guidance and best practices that the scorecards are tracking.

Use Cases

Organizations use scorecards in various situations, but their main purpose is to track the implementation and execution of strategic goals. Here are a few examples of how we've seen customers using them.

  • Compliance Monitoring: Platform teams can set compliance targets and automatically evaluate entities against these standards, ensuring adherence to best practices.

  • Performance Tracking: Entities are ranked based on predefined criteria, allowing teams to track performance and identify areas for improvement.

  • Standard Enforcement: By defining rules and ranks, platform teams can enforce organizational standards and practices, fostering a culture of quality and reliability.

With this in mind, created leaderboards. These leaderboards not only let engineers and team leads know how their teams are performing but also allow them to compare against other teams. This introduces gamification into the product, driving people to focus more on achieving the defined goals. Let's face it, no one wants to be last, right?

🥇
Rely.io