NEW
New: Deploy your application in minutes with Shard AI
All resources
Metrics and alerts

Monitor project metrics with the same dashboard charts

Shard Cloud shows RAM, CPU, and network usage beside each project with the same metric graphics used in the application dashboard. Watch recent resource pressure, choose a time range, and compare received and sent traffic.

Monitor project resources and define alert rules from the same data

RAM

memory usage

vCPU

CPU usage

Network

network traffic

5 alerts

per-project rules

Connected outcomes

Monitor project resources and define alert rules from the same data

Your dashboard turns live resource usage into charts, thresholds, and notifications for the selected project.

Explore capabilities

RAM, vCPU, and network

Real-time monitoring out of the box, zero setup needed.

Create sustained thresholds

Each rule combines a metric, a limit, and a minimum duration, reducing noise from short spikes.

Notify before users notice

Alert rules turn dashboard signals into notifications when a project stays above a defined limit.

Built to operate

Essential metrics and alerts that reduce noise.

RAM, CPU, and network telemetry feed the same alert engine that draws your dashboard charts, so a rule you create runs on data you're already looking at.

Memory

Track RAM pressure across recent intervals.

CPU

Identify saturation and changes in compute usage.

Network

Compare received and sent traffic in the same period.

Sustained thresholds

Combine metric, value, and duration to reduce noise.

Actionable notifications

Receive context when a project remains above its threshold.

Progressive setup

Set a rule once. Let it watch.

Pick a metric, set a limit and a minimum duration, and the rule runs continuously against the same telemetry your dashboard already shows.

Get started
01
Choose the metric
Open the metrics tab for RAM, CPU, network ingress, network egress, or total traffic.
02
Define the threshold
Set the limit and how long usage needs to stay above it before the rule fires.
03
Receive the context
The rule stays quiet until both conditions are met, then sends a notification you can act on immediately.

From connection to the first decision, in one flow.

Frequently asked questions

How this resource works in practice.

RAM, CPU, network ingress, network egress, and total network traffic — five metric types per project.

Ready to move forward

Turn capacity into a more predictable operation.

Enable metrics and alerts that help your team act at the right time.

Guided setup with no commitment

RAM, CPU, and network in one view
See resource pressure the moment it starts building.

Alerts with a minimum duration
Reduce noise from short spikes with sustained thresholds.

Set up your first alert
Pick a metric, a limit, and get notified before users do.

Connected ecosystem

Connects to the workflow your team already uses

GitHub

Connect repositories and keep every release linked to its source code.

Docker

Ship your own images with a consistent process across environments.

PostgreSQL

Connect data and applications without losing operational service context.

Shard Edge

Bring caching, TLS, and global delivery closer to your users.

Shard AI

Investigate signals and execute actions with workspace context and approval.

OpenTelemetry

Connect standardized signals to expand visibility whenever needed.

Source, data, delivery, and automation stay connected so your team can operate without switching context.

Explore connected resources
Build on Core

Start with the plan built for your next production service.

Launch your first application with the Core plan, then keep deployment, operations, and connected resources in one place.

Start with Core