Managing Costs Overview

AWS infrastructure costs are billed directly to your AWS account, separate from Stacktape's subscription fee. The Stacktape Console provides cost dashboards, cost attribution by project and stage, and budget alerts to help you understand and control your AWS spend. This section also covers optimization strategies to reduce costs.

Managing costs involves three activities, each covered in a dedicated page:

ActivityQuestion it answersDetails
Viewing costsWhat am I spending and where?Dashboards, Per-resource breakdown
Controlling costsHow do I prevent overspend?Budgets
Reducing costsHow do I spend less?Optimization tips

If you are new to cost management, start by checking the overview dashboard for your current month-to-date spend, then set up an organization-wide budget alert as a safety net. Those two steps cover most teams.

Stacktape charges vs. AWS charges

Stacktape costs and AWS costs are independent charges on separate invoices. AWS infrastructure costs are charges in your connected AWS account. Stacktape subscription and billing are managed separately.

ChargeBilled byWhat it covers
AWS infrastructure costsAWS (to your AWS account)Compute, storage, networking, databases — everything your resources use
Stacktape subscriptionStacktape (to your organization)Stacktape platform subscription and plan features

AWS bills your account directly — the Stacktape Console displays AWS cost report data for connected AWS accounts but does not process AWS charges. Subscription plans and billing are managed on the Billing page.

Viewing costs

The Stacktape Console shows AWS cost data in two places: the organization overview dashboard and the dedicated costs per stack page.

The overview dashboard displays a month-to-date AWS costs KPI with a trend comparison against the previous month and a cost trend sparkline, an AWS Costs by Project chart (top 10 projects, with the remainder grouped as "Other" when there are more than 10), and an AWS Costs by Resource chart. These give you a quick spending snapshot without navigating away from the main dashboard. Budget alert status also appears on the overview dashboard, showing each configured budget with its name, scope, alert percentages, and threshold.

The costs per stack page lets you select a connected AWS account and a time range (month), then shows a table of every attributed stack with its project name, stage, region, and month-to-date costs — sortable by cost and paginated at 10 rows per page. Clicking a row navigates to the per-stage cost detail view. This is where you go to compare spend across stages or find your most expensive stack for a given month.

New stacks may take up to a day to appear in cost data after their first deployment.

For the full walkthrough of these views, see Dashboards. The overview dashboard includes an AWS Costs by Resource chart — see Per-resource breakdown for the dedicated cost-breakdown page.

Cost attribution

The costs-per-stack view shows AWS costs broken down by project and stage, generated daily from AWS Cost and Usage Reports. Stack attribution is based on Stacktape deployment metadata attached during deploy operations.

Controlling costs with budgets

A budget sets a monthly spending limit for one connected AWS account. Stacktape creates the matching AWS budget in that account and alerts your channels when actual or forecasted spend crosses percentages of the limit. A budget watches the whole account; it cannot filter by project or stage.

The Budgets page shows each budget's state this month and the alerts it sent. The Console Overview flags budgets that are over their limit or forecast to go over it.

Start with one budget for each AWS account that runs production stages, with the limit set to your expected monthly bill. To track production and development spend separately, run them in separate AWS accounts.

For setup details, see Budgets.

Reducing costs

The largest cost-reduction levers in a typical Stacktape deployment are:

  1. Right-sizing compute — matching memory, CPU, and instance types to actual workload needs rather than over-provisioning. Right-size Lambda function memory so functions do not pay for capacity they do not use. The same principle applies to container-based workloads — match CPU and memory to observed usage, not worst-case estimates.
  2. Using Lambda functions for intermittent traffic — Lambda's pay-per-invocation model is often cheaper than always-on containers for bursty or idle-heavy workloads.
  3. Choosing the right database tier — using serverless database engines for variable workloads and provisioned instances only when sustained throughput justifies the cost. See relational databases for engine options and their tradeoffs.
  4. CDN caching — offloading repetitive responses to CDN edge locations to reduce origin compute. If your API returns the same response for the same request, caching it at the edge avoids hitting your backend entirely.
  5. Cleaning up unused stages — deleting preview and dev stages that are no longer needed. Every running stage incurs costs for its databases, containers, and other always-on resources, even if no traffic is hitting them.

For concrete, actionable guidance on each of these, see Optimization tips.

Managing Costs Overview FAQ

How long does it take for cost data to appear, and how often does it refresh?

Cost reports are generated daily from AWS Cost and Usage Reports, and new stacks may take up to a day to appear after their first deployment. There is no sub-daily spend monitoring through the Stacktape Console cost views.

Are AWS costs billed through Stacktape?

No. AWS bills your AWS account directly — the Stacktape Console displays AWS cost report data for connected AWS accounts but does not process AWS charges. Stacktape's own subscription is a separate charge billed by Stacktape to your organization. See Billing and subscription for subscription details.

Can a budget watch a single project or stage?

No. Each budget watches one whole AWS account. Stacktape v3 could filter budgets by project and stage; v4 cannot create those budgets. Use the costs-per-stack view to see spend per project and stage. See Budgets for setup steps.

What AWS services typically cost the most in Stacktape deployments?

For most deployments the largest cost drivers are compute (Lambda invocations and always-on containers), databases, and networking. The exact breakdown depends on your architecture. The overview dashboard includes an AWS Costs by Resource chart that shows your actual cost distribution across AWS service categories, and Optimization tips covers how to bring each of these down.

What's the difference between the overview dashboard and the costs per stack page?

The overview dashboard shows a spending summary — month-to-date total with a trend comparison against the previous month, a cost trend sparkline, AWS Costs by Project (top 10), and AWS Costs by Resource. The dedicated costs per stack page shows attributed stacks in a table, paginated at 10 rows per page and initially sorted by month-to-date costs, with AWS account and time range selectors and navigation to per-stage detail views. See Dashboards for a walkthrough of both.