Know when your federated graph changes, the moment it changes

Cosmo detects schema updates across all subgraphs and dispatches notifications to every configured channel immediately. Webhooks, Slack, per-channel event filtering, and actor attribution built in.

No polling. No custom infrastructure. Events delivered in under a second.

The problem

Federation teams miss changes they need to know about

Subgraphs evolve independently. Downstream consumers find out about changes when their integrations break, not before.

Schema changes happen without warning

Multiple teams publish subgraph updates on their own schedules. Downstream consumers have no way to know a change occurred until something breaks.

Manual monitoring is unworkable at scale

Checking the schema registry by hand for each subgraph across multiple namespaces is not sustainable. Teams miss changes. Coordination breaks down.

Generic tools have no federation context

HTTP monitors see traffic, not schema events. They cannot tell you which subgraph changed, whether errors occurred, or who made the change.

Our solution

A notification hub for the whole federated graph

One system handles detection and dispatch. Configure webhooks for programmatic integrations and Slack for team visibility. Each channel gets its own event subscription. Every payload is signed and carries actor attribution.

From event to notification

1. Cosmo monitors your federated graph for schema changes and other significant events.
2. When an event occurs, the system dispatches notifications to all configured channels immediately.
3. Webhooks receive HMAC-SHA256 signed HTTP POST requests with structured JSON payloads.
4. Slack integrations receive formatted messages directly to your chosen channel via the Slack API.
5. Each channel has its own event subscription, so different teams receive only the alerts they care about.
6. Payloads include the federated graph ID, name, namespace, error status, and an optional actor ID for attribution.

Configure once. Every change reaches the right channels automatically.

Alerts & Notifications

Before & After

Notification channels

Two delivery mechanisms

Webhooks - HTTP POST to any endpoint. HMAC-SHA256 signature in X-Cosmo-Signature-256. Versioned JSON payload with graph details and actor ID.

Slack - OAuth 2.0 authorization. Posts formatted messages directly to any channel. No middleware, no custom bots, no code to write.

How Cosmo Notifications works

1. Detect - Cosmo monitors your federated graph for schema changes and other events. When any subgraph publishes an update that affects the federated schema, the event is captured immediately.
2. Dispatch - Notifications are dispatched to all configured channels in real-time. Webhook requests are sent with HMAC-SHA256 signatures. Slack messages are posted directly via the Slack API.
3. Filter - Each notification channel has its own event subscription. Subscribe a channel to FEDERATED_GRAPH_SCHEMA_UPDATED and it receives only those events. Other channels can have different subscriptions.
4. Attribute - Payloads include the federated graph ID, name, namespace, and error status. An optional actor_id field identifies the person or system that triggered the event, supporting audit and compliance use cases.

What's included

Built into every Cosmo plan

• Webhooks and Slack, both available on Free, Pro, and Enterprise.
• Event-driven dispatch - Notifications go out the moment a schema event occurs. No polling interval, no scheduled check. Sub-second delivery to all configured channels.
• HMAC-SHA256 verification - Every webhook request carries a signature in the X-Cosmo-Signature-256 header. Verify it in your endpoint to confirm the payload is authentic and untampered.
• Per-channel event filtering - Each webhook and Slack integration subscribes to specific event types independently. Teams receive only the alerts relevant to them.
• Actor attribution - Event payloads include an optional actor_id field identifying who triggered the change. Feeds audit logs and compliance reports without additional instrumentation.

Set up schema change notifications

Configure webhooks or Slack from the Cosmo Studio. Events start flowing the moment you save.

FAQ

Alerts & Notifications on Cosmo

• What events does Cosmo notify on?
• What does the event payload contain?
• Can I have multiple notification channels?
• How do I verify webhook payloads are authentic?
• Can I filter notifications to specific events?
• Is there a delivery guarantee or retry mechanism?

Full details in the notifications documentation.