// Phase 1 — Cloud & FinOps
Idle infrastructure is easy to create and hard to notice. We build open-source tools that make it visible — starting with the cloud, where the waste is measurable and the bill arrives monthly.
tellury — one binary that scans AWS, Azure and GCP, finds resources nothing is using, and prices each one per month.
$ typeone --mission
Waste accumulates quietly. A disk outlives the machine it was attached to, an address is reserved and never used, a VM is sized for a load that never came — each one small, none of them noticed, all of them billed. We build tools that find these and say what they cost, with the evidence attached.
Cloud infrastructure is where we started, because the waste there is measurable and the feedback loop is a monthly invoice. The same problem exists in energy and logistics, and it is harder to measure there. One thing at a time.
$ █
The name comes from the Kardashev scale, proposed in 1964 to rank civilizations by the energy they can actually put to use. A Type I civilization is one that makes full use of what is available to it on its own planet. Nothing idle, nothing spilled, nothing burned for no reason.
We treat it as a framework rather than a forecast — the simplest available description of what we are building toward. Every tool we ship is a step in that direction.
[ Kardashev Scale — Wikipedia ↗ ]Analyzing systemic resource imbalances, algorithmic efficiency, and energy dynamics.
Developer-first, CLI-driven, zero-overhead utilities built for immediate integration and zero waste.
Uniting systems architects, quant engineers, and researchers to solve infrastructure bloat.
A single-binary CLI that finds unused and overprovisioned cloud resources and tells you what each one costs per month — a disk nothing is attached to, an address nobody routes to, a VM sized for a load that never arrived. No dashboard, no daemon, no agent to deploy.
Rules are deterministic: every finding resolves to true or false against data the provider actually returns, and carries the evidence and the SKU behind its dollar figure. A rule that cannot evaluate a resource says why instead of guessing.
AWS, Azure and GCP — inventory, metrics and live pricing on all three, with eleven rules. Scan one account, one subscription, one project, or a whole organization: findings roll up through the hierarchy each cloud actually has.
$ tellury scan --aws-account 123456789012 --aws-regions eu-west-1
RESOURCE RULE SEVERITY MONTHLY WASTE instance/i-0a1b2c3d4e5f underutilized_ec2 HIGH $8.32 address/52.18.213.207 unassociated_eip MEDIUM $3.65 ---------------------------------------------------------------- TOTAL 2 findings $11.97
$ tellury scan --azure-subscription 0000… --azure-resource-group rg-prod
RESOURCE RULE SEVERITY MONTHLY WASTE instance/vm-batch-01 underutilized_vm HIGH $67.16 address/orphan-ip unassociated_public_ip MEDIUM $3.65 disk/orphan-disk unattached_managed_disk MEDIUM $1.54 ------------------------------------------------------------------- TOTAL 3 findings $72.35
$ tellury scan --gcp-organization 123456789012
RESOURCE PROJECT RULE SEVERITY MONTHLY WASTE instance/etl-worker-3 data-platform underutilized_instance HIGH $48.60 disk/old-cache ml-training detached_disk MEDIUM $20.00 address/reserved-ip-01 data-platform unused_reserved_ip MEDIUM $7.30 ---------------------------------------------------------------------------------- TOTAL 3 findings $75.90
// every figure traces to the SKU that priced it