Telescope finds the waste
A read-only scan of your fleet, classified by real CPU / memory / network / disk utilization — not sticker size.
Free Cloud Health Check · 雲端健檢
A free, read-only self-assessment of every GCE / EC2 instance you run. Know exactly where you are before you change anything — the same way you'd get a check-up before any surgery.
What the check-up tells you
You run it yourself on a viewer-role service account you create. No writes, ever.
Telescope is Apache 2.0 on GitHub. No sign-up, no sales call to get your report.
If the report shows waste, we size a consolidation plan. If it doesn't, you've lost nothing.
Five minutes, zero risk
No credentials needed for the demo scan. For a real scan, a viewer-role service account is all Telescope ever gets.
# build from source (Go, Apache 2.0)
$ git clone https://github.com/FootprintAI/telescope && cd telescope
$ go build -o telescope ./cmd/telescope
# no cloud creds? see what a report looks like on synthetic data
$ ./telescope scan --provider mock
# real scan — GCP, with the read-only service account you created
$ ./telescope scan --provider gcp --projects my-project \
--credentials ./readonly-sa.json --lookback 14d \
--output csv --out report.csv
# or AWS
$ ./telescope scan --provider aws --regions us-east-1 \
--lookback 14d --output csv --out report.csv
GCP scans need only roles/compute.viewer,
roles/container.viewer, and
roles/monitoring.viewer — no write permissions, ever.
If the check-up finds waste
The treatment only comes after the diagnosis — and only if you want it. Containarium doesn't replace your cloud provider; it runs on it. Right-sized boxes on the GCE / EC2 capacity you already pay for, driven by the workflow you already have.
A read-only scan of your fleet, classified by real CPU / memory / network / disk utilization — not sticker size.
Under-used VMs collapse into fewer, right-sized Containarium boxes on the same cloud account — real Linux, real sudo, real systemd.
ssh, terraform, systemd, your existing CI — all still point at the same provider. Apache 2.0, self-hostable, no lock-in.
Case study
A client came to us running six VMs — 16 cores, 64 GB RAM, and 1 TB disk each, every one sized for peak. Their check-up showed the headroom; consolidating onto Containarium took 20% off the bill, same workloads.
We moved six peak-sized VMs onto Containarium and cut the bill by 20% — without giving up performance. Our ops team still maintains and upgrades everything the same way it always has.
That fleet was six busy machines — 20% was their number. Fleets carrying redundant or idle instances have more headroom. Your health check tells you yours.
FAQ
A self-assessment of your own cloud fleet that you run yourself, with Telescope, a free open-source (Apache 2.0) scanner. It reads metrics through a viewer-role service account you control and classifies every GCE/EC2 instance and GKE/EKS node by real utilization — CPU-bound, memory-bound, network-bound, disk-bound, or idle. You see the report first; what to do about it is a separate, later decision.
Telescope is a free, open-source (Apache 2.0) scanner. You point it at a read-only service account on your GCE or AWS account, and it classifies every instance by real utilization — CPU-bound, memory-bound, network-bound, disk-bound, or idle. It never writes to your infrastructure.
No. Telescope only reads metrics through a viewer-role service account you create and control — on GCP that's just roles/compute.viewer, roles/container.viewer, and roles/monitoring.viewer; on AWS a read-only policy over EC2, EKS, and CloudWatch. It doesn't touch your VMs, your CI, or your deploy pipeline. Consolidation only happens later, and only if you choose to act on the report.
It depends on what the health check finds — which is exactly why the check-up comes first. Telescope measures how much of each instance's CPU, memory, network, and disk you actually use, and we size the consolidation plan from that measured data. One client with six peak-sized VMs saved 20%; fleets carrying redundant or idle instances have more headroom. Your number comes from your own report, not a generic estimate.
No. Containarium boxes run on your own cloud provider account, driven by the same ssh / terraform / systemd / CI workflow you already use. No re-architecture, no code changes. You can also self-host Containarium yourself under Apache 2.0 — no lock-in.
Run the free Cloud Health Check. If the report shows waste, send it over — we'll size the fix. The surgery is optional; the check-up is free.