Overview

Product video
Pi FinOps is a cloud financial management and FinOps solution designed to help organizations gain visibility, control, and optimize their AWS cloud spending. It provides a unified view of AWS costs across accounts, services, workloads, and environments, helping teams understand where cloud spend is going and identify opportunities to improve cost efficiency.
With capabilities for cost allocation, cost analysis, forecasting, budgeting, governance, and optimization, Pi FinOps helps FinOps, finance, engineering, and cloud teams make informed decisions about AWS consumption. It helps identify cloud waste, track savings opportunities, improve accountability, and continuously optimize AWS costs while maintaining visibility across the organization.
Highlights
- AWS Cost Visibility & Analysis Analyze AWS costs and usage across accounts and services to identify major cost drivers, idle resources, and underutilized workloads.
- Cost Optimization & Savings Opportunities Identify actionable savings opportunities through rightsizing, Savings Plans, Reserved Instances, and removal of unnecessary cloud resources.
- FinOps Governance & Cost Control Improve tagging, cost allocation, forecasting, and FinOps governance to strengthen financial accountability and continuously optimize AWS spend.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Description | Cost/unit/hour |
|---|---|---|
Hours | Container Hours | $0.001 |
Vendor refund policy
Himanshu Shah Contact +1 (469) 678-0615 (US) | +91 9137343313 (India)
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Container Image
- Amazon ECS
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Initial release of Pi FinOps on Microsoft Marketplace, enabling organizations to gain visibility into cloud spend, identify cost optimization opportunities, strengthen FinOps governance, and improve cloud cost efficiency.
Additional details
Usage instructions
PI FINOPS ON ECS/EC2 (us-east-1, 60-90 min) ALB (80) routes to frontend (3000), backend (5000) and PostgreSQL (5432), each on a t3.micro in one ECS cluster.
PREREQUISITES
- Admin access, VPC with 2 public subnets, active subscription, the 3 image URIs, Cost Explorer enabled
- DB password: 8-64 chars, letters, digits, _ and - only
- ECS AMI ID: aws ssm get-parameter --region us-east-1 --name /aws/service/ecs/optimized-ami/amazon-linux-2023/recommended/image_id --query Parameter.Value --output text
- IAM ROLES
- finops-ecs-instance-role (EC2): AmazonEC2ContainerServiceforEC2Role
- finops-task-execution-role (ECS Task): AmazonECSTaskExecutionRolePolicy
- finops-backend-task-role (ECS Task): inline read-only: ce:Get*, ce:Describe*, cost-optimization-hub List*/Get*, tag:GetTagKeys, tag:GetResources, aws-marketplace:MeterUsage
- SECURITY GROUPS (in order; no SSH)
- finops-alb-sg: TCP 80 from your IP range
- finops-frontend-sg: 3000 from alb-sg
- finops-backend-sg: 5000 from alb-sg
- finops-db-sg: 5432 from backend-sg
-
CLUSTER AND INSTANCES Create cluster finops-cluster (no ASG). Launch 3 t3.micro (ECS AMI, no key pair, same public subnet, public IP on, profile finops-ecs-instance-role): finops-frontend-instance (frontend-sg), finops-backend-instance (backend-sg), finops-postgres-instance (db-sg). User data: ECS_CLUSTER=finops-cluster in /etc/ecs/ecs.config, plus ECS_INSTANCE_ATTRIBUTES={"tier":"frontend"} or {"tier":"backend"}. DB instance: add /dev/sdf, 20 GiB gp3, encrypted, Delete on termination = No. User data formats XFS if blank, mounts /ebs/postgres, creates /ebs/postgres/data (chown 70:70, chmod 700), sets tier data. Confirm all 3 in the cluster; note the DB private IP.
-
LOAD BALANCER Target groups (Instances, HTTP, 30s interval/deregistration):
- finops-frontend-tg: 3000, path /finops/frontend, codes 200-399
- finops-backend-tg: 5000, path /api/finops, codes 200-499 ALB finops-alb: internet-facing, 2 AZs, alb-sg, HTTP:80, default 302 redirect to /finops/frontend. Rules: priority 10 /api/finops and /api/finops/* to backend-tg; priority 20 /finops/frontend and /finops/frontend/* to frontend-tg. Note the ALB DNS name.
- TASK DEFINITIONS (bridge, EC2, memoryReservation 512, no-new-privileges)
- finops-postgres: DB image, 5432; POSTGRES_USER=postgres, POSTGRES_PASSWORD, POSTGRES_DB=finops; host path /ebs/postgres/data mounted at /var/lib/postgresql/data; pg_isready health check
- finops-backend: backend image, 5000; DB_URL=postgresql://postgres:<PASSWORD>@<DB_IP>:5432/finops; both roles
- finops-frontend: frontend image, 3000; API_URL=http://<ALB_DNS>/api/finops; AWS_ENABLED/AZURE_ENABLED/GCP_ENABLED true/false
- SERVICES (EC2, 1 task, min 0%/max 100%; in order, wait for 1/1)
- finops-postgres-service: attribute:tier == data, no LB
- finops-backend-service: tier == backend, ALB to backend-tg, grace 60s
- finops-frontend-service: tier == frontend, ALB to frontend-tg, grace 60s Open http://<ALB_DNS>/finops/frontend (503 = wait 2-3 min; charts may be empty up to 24h).
SENSITIVE DATA DB password is plain text in the postgres and backend task definitions; restrict access. DB data is on the encrypted EBS volume at /ebs/postgres/data.
OPERATIONS Production: narrow alb-sg, add HTTPS (ACM + 443). Back up with EBS snapshots. Update via new task definition revisions. Never change the DB password after first start or terminate the DB instance without a snapshot.
TROUBLESHOOTING Instance missing: profile, public IP, IGW route, cluster name. No matching instance: tier. Image pull fails: subscription, region, URI. 503: service events, SG ports, rules, health paths. DB unreachable: DB IP, password, db-sg. No data: API_URL, Cost Explorer.
REMOVAL: services, ALB, target groups, instances, EBS volume, cluster, SGs (db, backend, frontend, alb), IAM roles.
SUPPORT: Pibythree, with region, step and error text (never the password).
Resources
Vendor resources
Support
Vendor support
Himanshu.shah@pibythree.com +1 (469) 678-0615 https://pibythree.com/contact-us +91 9137343313
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.