Terasky — Customer Success Report

1. Cloud FinOps — Monthly Customer Reporting

Description: Terasky delivers automated monthly FinOps review emails to their managed cloud customers across AWS, GCP, and Azure. Each report pulls real-time data from Anodot Cost and CloudHealth, including total spend, top services, month-over-month changes, marketplace charges, and cost-optimization recommendations. A separate quarterly report covers savings plan and RI commit performance.

Business problem solved: Manual FinOps reporting at MSP scale is unsustainable — Terasky manages dozens of customers across multiple cloud providers. Blink eliminates the manual effort of pulling cost data, formatting reports, and sending emails, allowing the FinOps team to deliver consistent, timely reporting at scale.

Integrations: Anodot Cost, CloudHealth, AWS SES (SMTP), Email

2. Cloud FinOps — Cost Anomaly & Spend Alerting

Description: Real-time and scheduled alerting to Terasky's end-customers whenever unusual cloud spend patterns, cost trend anomalies, new marketplace purchases, or new region activations are detected. The Umbrella-integrated webhook pipeline dispatches alerts per-customer based on their subscriptions. A weekly trend summary consolidates total cost and linked-account spend changes.

Business problem solved: Cloud cost overruns often go unnoticed until month-end billing surprises. This use case gives Terasky's customers proactive, near-real-time financial governance signals without requiring any manual monitoring effort.

Integrations: Umbrella (Anodot Anomaly Detection), AWS Cost Explorer, Azure Cost Management, Email (AWS SES)

3. Cloud FinOps — Customer Registry & Sync

Description: Terasky maintains a central registry of their managed cloud customers spanning AWS, GCP, Azure, and Anodot Cost. Blink keeps this database continuously synchronized: discovering new organizations and linked accounts, assigning Anodot Cost mappings, maintaining contact details, and alerting when data quality gaps are found. This registry powers all downstream FinOps reporting and alerting.

Business problem solved: As an MSP managing hundreds of cloud accounts across multiple providers, Terasky needs a single source of truth for customer identities. Manual reconciliation across AWS Organizations, GCP billing, Azure EA, and Anodot Cost would require constant manual effort.

Integrations: AWS Organizations, GCP Billing, Azure, Anodot Cost, Blink Tables

4. Cloud FinOps — Reservations & Savings Plans Tracking

Description: Tracks AWS Reserved Instances and Savings Plans across Terasky's entire managed customer portfolio. Automations fetch and store current reservations weekly, alert customers when commitments are within 30 days of expiration, monitor Terasky's own TSP (Terasky Savings Plan) utilization daily, and provide on-demand RI savings analysis.

Business problem solved: Expiring cloud commitments that go unrenewed result in customers paying on-demand rates. Terasky needs a scalable way to proactively track expirations and savings plan performance across all managed accounts without logging into each individually.

Integrations: AWS Cost Explorer, AWS STS (cross-account role), Email (AWS SES)

5. Cloud FinOps — Instance Optimization Recommendations

Description: A suite of on-demand automations that generate rightsizing and upgrade recommendations for EC2, RDS, ElastiCache, and OpenSearch instances. Each automation queries Anodot Cost for spend by instance type, identifies instances with upgrade potential, prices alternatives via the AWS Pricing API, and returns ranked recommendations. GCP recommendations are pulled via the native Recommender API.

Business problem solved: Manually identifying underutilized or over-provisioned instances across all customer environments requires significant engineering time. This use case automates the discovery-to-recommendation pipeline.

Integrations: Anodot Cost, AWS Pricing API, AWS STS, GCP Recommender API

6. AWS Playground Environment Management

Description: Terasky operates internal AWS and GCP playground environments for their engineering team. Blink automates the complete lifecycle: provisioning personal and lab accounts via AWS Service Catalog, nightly cleanup of wasteful resources (idle EC2 instances, unused EBS volumes, unattached EIPs, old snapshots, idle NAT gateways), automatic closure of expired lab accounts, and monthly cost reporting per account.

Business problem solved: Engineering sandbox environments generate significant cloud waste when resources are left running. Manual cleanup is unreliable. Blink's nightly automation drives down internal cloud costs and enforces hygiene without engineer intervention.

Integrations: AWS Organizations, AWS Service Catalog, AWS SSO, AWS STS (cross-account), GCP, Anodot Cost, Slack, Email

7. AWS Service Awareness & Tagging Governance

Description: Keeps Terasky's customers informed of relevant AWS platform changes and enforces cloud governance. Monthly Amazon product announcements are filtered by service relevance and delivered per customer. Service deprecation alerts are checked weekly. Cost allocation tags are managed on-demand, including activation, status reporting, and deployment of the Auto Tagger tool. GCP resource tagging changes are reported weekly to specific customers.

Business problem solved: AWS releases hundreds of service updates monthly; customers cannot track what is relevant to them. Tag governance failures lead to unallocated cloud costs. This use case ensures customers stay aware and their cost attribution remains accurate.

Integrations: AWS (Cost Explorer, Organizations, STS), Anodot Cost, GCP BigQuery, Email (AWS SES)

8. Aqua Security License Monitoring

Description: Monitors Aqua Security license expirations across Terasky's managed customer environments. A daily scheduled automation assumes cross-account IAM roles, checks active license end dates, and proactively notifies account teams when licenses are approaching expiry.

Business problem solved: Expired security tool licenses result in gaps in customer protection — and potential SLA violations for Terasky as the managing partner. Automated daily checks eliminate the risk of missed expirations across large customer portfolios.

Integrations: AWS STS (cross-account role), Email

9. AWS Account Lifecycle Management

Description: Manages end-to-end creation of new AWS accounts within Terasky's MSP customer organizations, including STS role validation, existing-org checks, Organizations API provisioning, and confirmation loops. A monthly report delivers an overview of newly onboarded linked accounts.

Business problem solved: Manually creating and configuring AWS accounts through the Organizations console is error-prone and slow. This use case enables Terasky's operations team to spin up new customer accounts programmatically with audit-ready logging.

Integrations: AWS Organizations, AWS STS, Email (AWS SES)

10. Amazon Deals Publishing

Description: An automated pipeline that fetches Amazon marketplace deals weekly, stores them in a Blink table, and publishes them to a Telegram channel every two hours. Ended deals are purged weekly to keep the dataset current.

Business problem solved: Manually sourcing and posting deals is time-consuming and inconsistent. Blink automates the full pipeline from discovery to publication, ensuring timely and continuous deal delivery to subscribers.

Integrations: Amazon (HTTP), Blink Tables, Telegram

11. FinOps CRM Sync (Monday.com)

Description: Syncs cloud spend metrics — total spend, month-over-month growth, customer tier, and per-service costs — from Anodot Cost into Monday.com boards. Runs on the 10th of each month, enabling Terasky's account management team to track portfolio health without leaving their project management tool.

Business problem solved: Switching between cost management platforms and CRM/project boards to prepare for customer calls wastes account manager time. This use case brings cloud spend directly into Monday.com where it is immediately actionable.

Integrations: Anodot Cost, Monday.com

12. Platform Operations

Description: Internal platform maintenance automations. Blink automations are backed up weekly to S3 to preserve configuration state. A monthly inventory of all Route53 domains across playground accounts is compiled and emailed to the platform team.

Business problem solved: Platform configuration drift and DNS sprawl are silent risks. Weekly automation backups ensure recoverability, and the DNS inventory prevents orphaned domains from accumulating.

Integrations: Blink API, AWS Organizations, AWS Route53, Email

13. Customer Self-Service Portal

Description: On-demand workflows that expose Terasky's internal services to customers: requesting new automation development, submitting benchmark test requests, and opening support cases. These are customer-facing touchpoints backed by Blink automation routing and email notification.

Business problem solved: Customer service requests that arrive via email or informal channels are hard to track and prioritize. Exposing them via Blink creates a structured intake with automatic routing and acknowledgment.

Integrations: Email

14. Onboarding & Tutorial Workspaces

Description: Multiple workspaces containing Blink getting-started tutorials and example playbooks (Hello World, Input Parameters, Loops, HTTP, Slack, AWS integrations). These appear across many workspaces with identical content, suggesting new workspace provisioning for team members or training environments.

Business problem solved: Onboarding new users and workspaces to Blink's automation platform.

Integrations: Core (Python, Bash), HTTP, Slack, AWS

Strengths

MSP-scale FinOps automation backbone. The core value Terasky extracts from Blink is running their managed cloud services practice at scale. The monthly FinOps review pipeline alone logged 171 executions — meaning Blink is the delivery mechanism for Terasky's primary customer deliverable. Anomaly and trend alerting add another 717 customer-facing alert deliveries on top of that.

Deep multi-cloud footprint. The automation inventory spans AWS (Organizations, EC2, RDS, ElastiCache, OpenSearch, Savings Plans, Route53, SES), GCP (Billing API, BigQuery, GKE, Recommender), Azure (Billing EA, Cost Management), Anodot Cost, CloudHealth, Monday.com, and Telegram — demonstrating broad platform investment across the entire MSP technology stack.

High-volume, proven production workflows. The playground cleanup automation running 1,442 times per year on individual accounts demonstrates Blink being used for critical, high-frequency infrastructure operations — not just occasional automation. The AWS Linked Accounts Helper at 388 executions further confirms this.

Internal ops coverage. Beyond customer-facing work, Terasky uses Blink for their own internal operations: playground environment lifecycle, automation backups, CRM synchronization, and DNS inventory. This indicates deep platform trust.

Gaps

Instance optimization recommendations not yet in production. Twelve playbooks covering EC2, RDS, ElastiCache, OpenSearch, and GCP rightsizing recommendations show zero executions. This is a high-value capability that is built but not yet operationalized — potentially representing a significant unrealized delivery opportunity.

Quarterly savings report pipeline inactive. The quarterly Savings Plan and RI commit savings reports have zero executions despite the monthly reporting pipeline being active. Customers are not yet receiving this dimension of their financial review automatically.

Customer self-service portal unused. The three portal workflows (Request New Automation, Request Instance Benchmark, Open Support Case) have never been executed. The intake channel may not have been communicated to customers.

CloudHealth reporting path dormant. Send Monthly FinOps Review to CloudHealth Customer has zero executions while the Anodot Cost path is active. Customers on CloudHealth are not receiving automated FinOps reviews.

Integration Ecosystem