Offer CloudGrid as part of your own product.
For enterprises, startups, and service providers that want a branded observability and AI-evaluation foundation inside their SaaS, platform, or managed service. CloudGrid provides the source-available product base; commercial licensing covers hosted and white-label use.
Use CloudGrid when observability is part of your offer.
The strongest fit is a product team that needs a branded telemetry workspace and wants control over deployment, customer data, and integration points.
Offer CloudGrid as the telemetry workspace inside an internal developer platform, private cloud, customer success environment, or managed service portfolio.
Use CloudGrid as the observability foundation behind a focused product instead of rebuilding OTLP ingest, project isolation, storage, dashboards, and AI evaluation from scratch.
Bundle a branded CloudGrid deployment with implementation, hosting, support, compliance work, or vertical-specific telemetry packages.
From brand wrapper to runtime ports.
White-label use goes beyond a logo swap. CloudGrid separates visible product identity, public access, private telemetry services, and infrastructure adapters so customization can happen at the right layer.
- Logo, product name, help destinations, legal links, and visible product language.
- Theme tokens such as brand colors, accents, surface treatment, and dark/light presentation.
- Authentication providers and session policy through the BFF-managed OIDC/OAuth boundary.
- Storage, message broker, and evaluation execution through adapter ports.
- Deployment packaging for your environment, tenant model, registry, ingress, TLS, and dependency choices.
- Operational runbooks, support posture, and customer-facing documentation around the branded offering.
Flexible because the bridge keeps boundaries honest.
CloudGrid's service split is what makes partner packaging practical: the public surface stays small, private services keep their ownership, and extensions happen behind message contracts and adapter ports.
The browser talks only to the TypeScript BFF. That keeps sessions, GraphQL, health, and static serving in one public boundary.
Request/reply reads, durable ingest, and live subjects move through the bridge contract instead of direct public access to storage services.
Storage-write mutates SurrealDB. Storage-read fetches telemetry and owns filtering, sorting, counts, grouping, facets, and live fanout.
Storage, bridge, auth, and execution integrations can change behind ports while service ownership and telemetry contracts stay explicit.
Scale each pressure point independently.
The modular service model lets each customer tune CloudGrid around their own workload. A write-heavy environment, a dashboard-heavy product, and a high-ingest telemetry service can each use the infrastructure shape that fits.
Scale collector capacity around OTLP traffic independently from read-path capacity.
Scale storage-write workers and durable bridge processing around write pressure, backlog, and persistence latency.
Scale storage-read and BFF capacity around dashboards, GraphQL queries, live subscriptions, and customer-facing UI load.
Customization ships faster because the interfaces are already written down.
CloudGrid comes with implementation specs, contracts, and restrictions that define the expected behavior before a customization project starts. That makes it practical to use AI agents, different programming languages, or third-party systems while keeping the white-label build focused.
Agents can read the specs first, then change branding, UX copy, adapter code, or deployment packaging against named interfaces instead of guessing product behavior.
The GraphQL schema, AsyncAPI bridge contract, error taxonomy, and architecture specs define the expected inputs, outputs, restrictions, and service ownership.
External auth, broker, storage, evaluation, or product-portfolio integrations can target documented boundaries while preserving the BFF, bridge, and storage service rules.
Specs describe implementation invariants such as data access boundaries, credential handling, public telemetry reads, live delivery, and adapter responsibilities.
Clear line between adoption and resale.
The public license supports source-available self-hosted adoption. When CloudGrid itself becomes the hosted service, white-label product, or managed observability offer, use the commercial path.
- Internal self-hosted use
- Covered by the public Apache 2.0 + Commons Clause license.
- Use inside your own product infrastructure
- Covered when CloudGrid supports your own product operations.
- Hosted CloudGrid SaaS
- Commercial license path.
- White-label resale or embedded offering
- Commercial license path.
- Managed service built substantially around CloudGrid
- Commercial license path.
Bring CloudGrid into your offer.
Start with the customization surface, then review the enterprise overview for data ownership, SSO, project isolation, and procurement answers.
