Deployment · Google Cloud Platform

Google Cloud runs your content. Reveille runs the watch.

Your Enterprise Content Management (ECM), Intelligent Document Processing (IDP), and automation platforms moved to Google Cloud. The workflows running on them still need an independent watcher. Reveille operates inside your Google Cloud environment — on GCP Windows Server instances and Google Cloud SQL for PostgreSQL — then feeds Google Cloud Logging and the tools your team already uses. Independent of the platform vendor. Native to the cloud.

Native to your cloud GCP Windows Server · Cloud SQL · Cloud Storage Deployment-agnostic by choice
At a glance · Reveille on Google Cloud

Content Observability that runs natively on Google Cloud — the facts.

  • Compute
    Runs on Google Compute Platform (GCP) Windows Server instances
  • Database
    Google Cloud SQL for PostgreSQL
  • Storage
    Monitors Google Cloud Storage performance and availability
  • Native services
    Cloud Storage, Cloud SQL for PostgreSQL, Cloud Logging, and Workspace
  • Containers
    Collectors run as OCI-compatible sidecar containers (RedHat OpenShift certified)
  • Email & SSO
    Google Workspace email over OAuth 2; SAML 2.0 SSO with Okta, Ping Identity, Entra ID
  • Security
    FIPS-compliant AES-256 with a customer-managed credential encryption key
  • Independence
    Independent of your ECM/IDP cloud vendor; native to Google Cloud
How it deploys

One observability layer, wherever your content lives.

Reveille is deployment-agnostic by choice. Run it entirely in Google Cloud, split it across the cloud boundary, or span a hybrid estate — the collectors carry the content-layer signal back to the Reveille server over a compressed, encrypted TLS session, and out to the Google Cloud services you already operate.

GOOGLE CLOUD Users & content apps Reveille collectors Reveille server on GCP VM Google Cloud Logging Event & log integration Cloud SQL for PostgreSQL Reveille & User Analytics DB Google Cloud Storage Storage performance & availability Google Workspace Email over OAuth 2 TLS
01

Fully in Google Cloud

Reveille and your content platform both run in Google Cloud. The Reveille server and collectors live on GCP Windows Server instances, the databases on Cloud SQL for PostgreSQL — one cloud-native estate, watched from inside.

02

Split across the boundary

Reveille collectors in Google Cloud with the Reveille server on-premises, or the reverse. Collectors send data compressed and encrypted over TLS, with an optional client-side certificate.

03

Hybrid estate

Content on-premises or in another cloud, Reveille in Google Cloud — or any mix. The same observability layer crosses the boundary single-vendor monitoring stops at.

Native Google Cloud services

Reveille feeds the Google Cloud tools you already run.

Reveille doesn’t bolt a separate console onto your cloud. It generates the content-layer signal your Google Cloud tooling can’t produce on its own, then feeds it straight into the services your team already operates.

Google Cloud Storage

Monitor Google Cloud Storage performance and availability, so the object storage your content depends on is observed too.

Cloud SQL for PostgreSQL

Host the Reveille and User Analytics databases on Google Cloud SQL for PostgreSQL.

Google Cloud Logging

Send Reveille events into Google Cloud Logging (the Google Log Service) for centralized search, retention, and correlation.

Google Workspace & Email

Google email server support with OAuth 2 authorization for Reveille notifications and reporting.

OCI ContainersContainers

Run Reveille collectors as Windows or Linux OCI-compatible sidecar containers; RedHat OpenShift is a certified target.

Connectors & RESTAlerting

Route alerts through PagerDuty, Slack, Teams, Datadog, and ServiceNow, and integrate Reveille data via 170+ REST API methods with OAuth 2.

Independent by structure

Reveille operates inside your Google Cloud — and answers to you.

Native to the cloud. Independent of the vendor. Reveille is the only observability layer not built, sold, or operated by the platforms it measures. Platform SLA is not workflow SLA — and your vendor can’t grade their own homework.

Questions

Reveille on Google Cloud — answered.

Does Reveille run on Google Cloud?
Yes. Reveille supports operation on Google Compute Platform (GCP) Windows Server instances, with full capability inside the Google Cloud environment. Reveille uses native Google Cloud services including Google Cloud Storage, Google Cloud SQL for PostgreSQL, Google Cloud Logging, and Google Workspace.
Which Google Cloud database service does Reveille support?
On Google Cloud, Reveille supports Google Cloud SQL for PostgreSQL for the Reveille and Reveille User Analytics databases. Reveille also supports SQL Server, Oracle, and PostgreSQL more broadly across on-premises and other cloud environments.
Can Reveille monitor Google Cloud Storage?
Yes. Reveille monitors Google Cloud Storage performance and availability, so the object storage your content services depend on is observed alongside the rest of the workflow.
Does Reveille integrate with Google Cloud Logging?
Yes. Reveille sends events to Google Cloud Logging (the Google Log Service). Because Google Cloud has no single native notification service equivalent, Reveille routes alert and incident notifications through its connector library — PagerDuty, Slack, Microsoft Teams, Datadog, ServiceNow, and others — and through Google email over OAuth 2.
Can Reveille run in containers on Google Cloud?
Reveille collectors run as Windows or Linux OCI-compatible sidecar containers, and the Reveille Platform collector runs as a separate Linux OCI container. RedHat OpenShift is a certified sidecar target, alongside Amazon EKS and Azure AKS. The Reveille Platform server itself runs on a GCP Windows Server instance rather than in a container, because of third-party ECM/IDP system API dependencies.
Does Reveille have to run in the same cloud as my content platform?
No. Reveille is deployment-agnostic. You can run Reveille and your content platform both in Google Cloud, run Reveille collectors in Google Cloud with the Reveille server on-premises (or the reverse), or span a hybrid estate. Reveille collectors bridge the boundary, sending data compressed and encrypted over an HTTP/HTTPS TLS session with an optional client-side certificate.
How does Reveille secure credentials and sign-in on Google Cloud?
Reveille encrypts all application credentials in its database with a FIPS-compliant AES symmetric algorithm using a 256-bit key, secured by a customer-managed credential encryption key. The Reveille User Console supports SAML 2.0 single sign-on with certified identity providers including Okta, Ping Identity, and Azure Entra ID, and the Reveille REST APIs support OAuth 2 authorization across 170+ methods.

The content layer is where your business runs. Reveille makes sure it holds.

See Content Observability running inside your Google Cloud environment — on your compute, your databases, your services.