SaaS
Introduction
This document outlines the architecture and operational framework of the SaaS deployment model for Observo. It provides an overview of how the control and data plane components are managed entirely by Observo, reducing customer operational burden while enabling rapid scalability and streamlined observability.

Fully Managed by Observo Cloud
Centralized Hosting
In the SaaS model, both the Manager (control plane) and Site (data plane) components are hosted and operated by Observo within its secure and scalable cloud infrastructure. This approach allows organizations to begin ingesting and routing data without provisioning or maintaining any infrastructure.
Simplified Onboarding
Customers configure their sources and destinations directly through the Observo web interface or APIs. The entire backend—from ingestion, transformation, to export—is handled by the Observo Cloud environment.
Data Exchange and Connectivity
Secure Data Ingestion
Observo exposes public endpoints for supported data sources such as:
AWS S3
Azure Event Hub
GCP Pub/Sub
REST and HTTP-based integrations
These endpoints are secured and can ingest telemetry data directly from cloud workloads and supported services.
Routing to Customer Destinations
Data processed in the Observo Cloud can be routed to:
Cloud-native destinations (e.g., Amazon S3, BigQuery, Snowflake)
SaaS applications (e.g., Datadog, Splunk, New Relic)
Other supported HTTP or custom endpoints
Operational Advantages
Zero Infrastructure Management
Customers are not responsible for deploying or maintaining any part of the Observo system. Updates, patches, scaling, and monitoring are all handled by the Observo team.
High Availability and Scalability
Observo’s SaaS infrastructure is designed with:
Redundant failover systems
Elastic autoscaling
Global endpoint distribution for optimal ingest performance
Cost-Efficient and Fast to Deploy
The SaaS model removes the overhead of infrastructure provisioning and accelerates time-to-value. Customers can start forwarding data in minutes by configuring access to cloud sources.
Compliance and Security
Data Isolation: Each customer’s data is isolated and encrypted in transit and at rest.
Access Control: Fine-grained RBAC and audit logging are built into the platform.
Compliance: Observo Cloud is built to support industry-standard compliance frameworks such as SOC 2, GDPR, and HIPAA.
Use Cases and Ideal Fit
The SaaS model is ideal for:
Organizations with workloads primarily in the public cloud (e.g., AWS, Azure, GCP)
Teams seeking to avoid infrastructure management overhead
Environments where quick time-to-value and minimal operational load are priorities
Enterprises looking for a secure, compliant observability platform that scales with usage
Summary
Observo Cloud hosts both Manager and Site components.
No infrastructure is required from the customer’s side.
Ingestion, processing, and exporting are all handled by Observo.
Supports a wide range of cloud-native sources and SaaS-based destinations.
Delivers operational simplicity, scalability, and security.
External Dependencies
There are no external dependencies to manage or install. Customers simply authenticate and configure their sources and destinations through the Observo dashboard or APIs.
Last updated
Was this helpful?

