Customizable

Make CloudGrid fit your brand, product, and runtime.

Customization is bigger than technical adapters. CloudGrid can adapt visible identity, packaging, auth, bridge, storage, alert delivery, and evaluation execution so it can run as your internal platform, customer deployment, or licensed white-label foundation.

Customization starts with the product your customers see.

Adapters are one part of the model. The larger idea is that CloudGrid can be branded, packaged, and extended as a source-available observability foundation. With the Commons Clause license, internal self-hosted use stays straightforward, while SaaS, resale, and white-label offerings use a commercial agreement.

01
Brand and product identity

Replace the visible product identity with your logo, naming, support links, legal links, and product copy for the audience you serve.

02
Color and visual system

Adapt the interface theme to your brand tokens while keeping CloudGrid's operational layout, accessibility baseline, and telemetry workflows intact.

03
Deployment and packaging

Run CloudGrid in your environment, product cloud, customer VPC, or managed tenant model using the same self-hosted service boundaries.

04
Adapters and runtime ports

Swap or extend storage, message bridge, auth, and evaluation execution boundaries while keeping the public BFF focused.

What can be customized

  • Visible identity: logo, product name, support destinations, legal links, and product language.
  • Design tokens: colors, brand accents, and theme variables while preserving telemetry workflows.
  • Runtime dependencies: storage, bridge, auth providers, alert delivery, and evaluation execution through explicit ports.
  • Deployment posture: self-hosted, managed customer environment, or commercial white-label SaaS by agreement.

How the modular model helps

Brand layer

Logo, naming, colors, product copy, help links, and packaging.

Access layer

OIDC/OAuth providers, BFF-owned sessions, project membership, and tenant-aware access rules.

Bridge layer

Request/reply, durable ingest, live subjects, and alert delivery dispatch behind the message broker port.

Data layer

Storage-read and storage-write own telemetry query and persistence semantics.

Execution layer

Evaluation targets, scorers, and external workflows can integrate through an execution adapter.

Adapters are real extension points inside the broader customization model.

CloudGrid keeps technical dependencies behind contracts so brand and business customization keeps the architecture strong. The BFF stays public-facing; private services keep storage and telemetry semantics; the message broker is the bridge between them.

Storage
v1
storage-read · storage-write
SurrealDB
  • filter & facet pushdown
  • idempotent persistence
  • live trace fanout
Implement the port. Ship a new adapter. The v1 is one of many.
Message bridge
v1
request/reply · streams · live · alert dispatch
NATS JetStream
  • durable ingest
  • typed request/reply
  • ephemeral session fanout
Implement the port. Ship a new adapter. The v1 is one of many.
Alert delivery
v1
dispatch request · delivery result
in-app · email · webhook
  • core-owned alert state
  • safe summaries only
  • provider adapters over bridge
Implement the port. Ship a new adapter. The v1 is one of many.
Auth provider
v1
OIDC/OAuth · session boundary
GitHub · Google · Entra ID
  • BFF-managed cookies
  • provider tokens stay server-side
  • claim canonicalization
Implement the port. Ship a new adapter. The v1 is one of many.
Evaluation execution
v1
run · score · optimize
adapter-backed
  • W3C trace context preserved
  • provider refs stay controlled
  • idempotent retries
Implement the port. Ship a new adapter. The v1 is one of many.
Building a commercial white-label or SaaS offering?

The public Commons Clause license is for source-available self-hosted adoption. Hosted resale, white-label packaging, and product-portfolio use are handled through a separate commercial path.

White-label solution