Oobeya Docs
  • GETTING STARTED
    • Welcome to Oobeya!
    • Get Started with Oobeya
    • Playground: Live Demo
    • Oobeya Quick Onboarding Guide
  • TEAM INSIGHTS & SYMPTOMS
    • Symptoms Catalog
      • S1- Recurring high rework rate
      • S2- Recurring high cognitive load
      • S3- High weekend activity
      • S4 - High Code Review Time
      • S6- High technical debt on Sonar
      • S7- High vulnerabilities on Sonar
      • S8- High code quality bugs on Sonar
      • S9 - Unreviewed Pull Requests
      • S10 - Lightning Pull Requests
      • S11 - Oversize Pull Requests
      • S12- High Lead Time For Changes (DORA)
      • S13- Low Deployment Frequency (DORA)
      • S14- High Change Failure Rate (DORA)
  • SECURITY
    • 🔐Security at Oobeya
    • Oobeya Managed SaaS
  • INSTALLATION
    • 🐳Oobeya Docker Installation Tutorial & Requirements
    • 🐳Oobeya Version Upgrade For the docker-compose Installations
    • Oobeya Version Upgrade for Kubernetes Installations
    • 🐳HTTPS Configuration For Docker Installations
  • PRODUCT DOCS
    • ⭐Oobeya Release Notes
      • 🎁Oobeya 2024 Q1 - Release Notes
      • 🎁Oobeya 2023 Q4 - Release Notes
      • 🎁Oobeya 2023 Q3 - Release Notes
      • 🎁Oobeya 2023 Q2 - Release Notes
      • 🎁Oobeya 2023 Q1 - Release Notes
      • 🎁Oobeya Nov & Dec '22 Updates
      • 🎁Oobeya September 2022 Updates
      • 🎁Oobeya August 2022 Updates
      • 🎁Oobeya July 2022 Updates
      • 🎁Oobeya June 2022 Updates
      • 🎁Oobeya Apr & May 2022 Updates
      • 🎁Oobeya March 2022 Updates
      • 🎁Oobeya Feb 2022 Updates
      • 🎁Oobeya Jan 2022 Updates
      • OOBEYA-2.0.8 - Release Notes
      • OOBEYA-2.0.4 - Release Notes
      • OOBEYA-2.0.0
      • OOBEYA-1.4.6
      • QAD-1.0 - 1.4
    • ▶️Product Tour
    • ❇️Metrics List
    • ☀️Developer Experience Metrics
  • INTEGRATIONS
    • Integration Catalog
      • SCM & CI/CD Integrations
        • Azure DevOps Integration
        • Bitbucket Cloud Integration
        • Bitbucket Server Integration
        • GitHub Integration
        • Step-by-Step Integration Instructions for the Oobeya GitHub Application
        • GitLab Integration
        • Jenkins & Cloudbees Integration
        • Octopus Deploy Integration
        • TeamCity Integration
      • Quality & Security Integrations
        • SonarQube Integration
        • SonarQube Cloud Integration
        • Veracode Integration
      • Project Management Integrations
        • Jira Cloud Integration
        • Jira Server Integration
      • APM / Monitoring Integrations
        • AppDynamics Integration
        • Azure Application Insights Integration
        • Dynatrace Integration
        • Elastic APM Integration
        • New Relic Integration
        • Sentry Integration
    • Installing An Addon
    • Adding A New Data Source
    • Updating and Deleting Data Sources
  • ADMINISTRATION
    • User Management, Single Sign-On, Auth Settings
      • Microsoft Entra (Azure AD) Integration
      • LDAP / Active Directory Integration
      • Importing a New User From LDAP / Active Directory
      • Bulk User Import in Oobeya Using CSV
      • Adding a New User
      • Deactivating a User
      • Understanding Roles in Oobeya
    • License Management
      • Updating The License Key
  • DEVELOPMENT ANALYTICS - GITWISER
    • Git Analytics - Metric Definitions
      • Coding Impact Score
      • Impact Ratio (team-level)
    • Setting Up Development Analytics And DORA Metrics
    • Git Analytics Exclusions
    • Setting Automated Reanalyze For Gitwiser
    • Deployment Analytics (DORA Metrics)
    • Merging Contributor Accounts
  • DORA Metrics
    • DORA Metrics Introduction
      • Lead Time For Changes (LTC)
      • Deployment Frequency (DF)
      • Change Failure Rate (CFR)
      • Mean Time To Restore Service (MTTR)
    • Failure Detection (For Change Failure Rate & MTTR)
    • How To Calculate DORA Metrics for GitHub
    • Updating Team Scorecard configuration to display DORA Metrics
    • How To Start Deployment Analytics (DORA Metrics) For An Existing Gitwiser Analysis
  • Project Analytics - AgileSpace
    • Agile Analytics - Metric Definitions
    • Agile Board Analytics Intro
    • Starting an Agile Board Analytics
    • Board Overview
    • Sprint Reports
    • Update the Agile Board Analytics
  • QUALITY ANALYTICS
    • Total Code Quality Index (TCQI)
  • Guides
    • Azure DevOps Guides
      • How To Calculate DORA Metrics for Azure DevOps
      • Best practices for integrating Oobeya with Azure DevOps Scrum Boards
  • PROFILES
    • Introduction
    • Adding A Profile
    • Developer Scorecard
    • Adding A Related Account Information To Oobeya Profile
  • Team Health
    • Adding A Team
    • Team Scorecard
    • Project Analytics (Scrum Teams) Widget
  • Test Quality Report Widget
  • CUSTOM DASHBOARDS
    • Adding A New Dashboard
    • Adding A New Widget
    • Updating And Deleting Widgets
    • Adding Jira Sprint Progress Widget
    • Adding Jira Board Metrics Widget (Metrics With JQL)
  • SUPPORT
    • Support Request Workflow
    • Customer Success & Support Guide
Powered by GitBook
On this page
  • Oobeya Managed SaaS (Private Cloud) offering provides a single-tenant SaaS environment for each customer.
  • How does Oobeya preserve the data? Where and how the data is hosted?

Was this helpful?

  1. SECURITY

Oobeya Managed SaaS

Learn more about Oobeya Managed SaaS offering.

Oobeya Managed SaaS (Private Cloud) offering provides a single-tenant SaaS environment for each customer.

This means each customer has their own dedicated instance of the software and its supporting infrastructure. Unlike a shared tenant (multi-tenant) model where multiple customers' data and resources are hosted on the same server/cluster, a single-tenant architecture ensures that your data is isolated from other customers' data. This isolation provides several benefits:

  • Enhanced Security: By not sharing resources with other tenants, the risk of data leakage or cross-tenant attacks is significantly reduced. Each tenant's environment can be secured according to their specific security policies and compliance requirements.

  • Customization and Control: Since the environment is exclusive, customers have greater flexibility to customize the software and infrastructure according to their unique business processes and needs. This includes the ability to implement custom security policies, compliance measures, and integrations with other tools.

  • Performance Reliability: In a single-tenant setup, customers do not have to worry about the "noisy neighbor" effect, where the activities of one tenant can impact the performance of others on the same server. Each customer enjoys the full resources of their dedicated environment, leading to more predictable and reliable performance.

How does Oobeya preserve the data? Where and how the data is hosted?

Oobeya preserves customer data by hosting it on MongoDB in a single-tenant SaaS environment. This setup provides a secure, isolated database and network for each customer, ensuring data integrity and security. Here's how Oobeya manages data preservation and security:

  • Isolated Databases: Each customer's data is stored in a separate MongoDB database. This isolation not only enhances security by separating your data from that of other customers but also allows for tailored database management practices that align with individual security and compliance needs.

  • Secure Hosting Environment: The data is hosted and managed within a secure, single-tenant environment. This means that each customer's data storage and processing resources are not shared with others, minimizing the risk of unauthorized access or data breaches.

  • Compliance and Security Customization: Given the isolated nature of each tenant's environment, customers have the ability to implement their own security measures and comply with specific regulations. Oobeya's infrastructure supports customization in terms of access controls, and other security protocols.

  • Integration with SDLC Tooling: For customers integrating Oobeya with their software development lifecycle (SDLC) tools, such as GitHub, Azure DevOps, Jira, Jenkins, and Sonar, Oobeya ensures that the data flowing from these integrations is securely managed and preserved within the isolated, single-tenant environment. This approach allows for seamless and secure data exchange between Oobeya and your software engineering ecosystem, ensuring that all relevant data is accurately captured, stored, and available for your team's use.

In summary, Oobeya's approach to data hosting and preservation is designed to ensure maximum security, performance, and flexibility for its customers. By leveraging a single-tenant SaaS model and hosting data on MongoDB within this isolated environment, Oobeya offers a secure, customizable, and reliable solution that meets the diverse needs of its customers.

PreviousSecurity at OobeyaNextOobeya Docker Installation Tutorial & Requirements

Last updated 6 months ago

Was this helpful?