What your AWS costs, hour by hour

qloudpulse shows what your AWS accounts cost each hour, what changed, what you could change to spend less, and how it compares with your bill. It reads through a read-only role, and never sees what is stored in your accounts.

Sign up

Free during early access. No card needed. See pricing

The start page of the reports: a chart of the cost per hour over the last 14 days, the cost per month over the last 13 months, and a card with the savings found so far, $1,374 a month.
The start page of the reports. Every screenshot here shows made-up data.

What it does

Reports from your AWS accounts

qloudpulse collects from your accounts on a schedule and draws reports your whole team can read in a browser: what you spend, what is running, and what you could stop paying for.

Split the way you work

Break any cost down by account, environment, service and resource, and filter to the part you care about. The link holds the view, so a colleague who opens it sees what you see.

Reports of your own

Build your own report on the same data, with no code: pick the blocks and the columns, or make a copy of any report and change it.

Benefits

Cost hour by hour

AWS delivers the bill about a day late and keeps revising it until the month closes. The run rate does not wait: it says what your running resources cost this hour.

  • Compare with 24 hours or 7 days ago, and see which resources moved.
  • It names the cause where it can, such as a fleet going from 4 to 12 instances.
  • A collection run that failed shows as a gap, never as a zero.

At AWS list price, excluding VAT. Data transfer, snapshots and request charges cannot be measured per hour, so they come from the bill if you connect it. Credits, refunds and tax are only on the bill.

A report's headline: the cost per hour is 28% higher than this time yesterday. Below it, the resource reports-batch is marked as the largest change, with its usage going from 4 to 12 instances.

Savings recommendations

A to-do list of what to change to spend less, largest saving first, worked out again every day.

  • It finds gp2 volumes that could be gp3, unattached volumes, idle load balancers and NAT gateways, older instance generations and DynamoDB capacity above use.
  • Each kind of change says what it is, what to do, what to watch out for and how much work it takes.
  • Where one command does it, you get that command to preview and to apply. You run it: qloudpulse changes nothing.
  • Changes you have made move to a done list, with what they save.

Savings are at list price, before discounts and Savings Plans, so the bill may show less.

The savings report: 9 changes would save $1,374 a month. Under it, a numbered list of actions, each saying what it is, what to do and what to watch out for, with the resource and the saving per month.

Your run rate compared with your bill

Connect your bill, and each day's run rate sits beside what AWS charged for the same services and resources, with the difference between them.

  • A steady gap usually means a discount or usage we do not measure. A sudden one is worth a look.
  • See it by service and by resource, to find where the two part ways.

Connecting the bill is optional. Only services the run rate prices are compared, and only days at least two days old, as the bill lags.

Two lines over three months, the daily run rate and the daily bill, with the bill a little lower. Below them, a table by service with the run rate, the bill and the difference.

You decide what we build next

qloudpulse is young, and what the people using it ask for is what gets built. Asking takes a minute, from any page of the reports.

  • Ask from any page. Suggest a feature is in the top bar of every report. Say in a line what you need, and paste a screenshot if it helps to show it.
  • Hear back from the people who build it. Every request is read and answered, and you follow it in the app: received, planned, built, or not planned and why.
  • See where it stands. Your company's requests are on one page, with every answer we gave.
Suggest a feature

Not using qloudpulse yet? Tell us what it would need to do for you: support@qloudpulse.com

How it works

Early access shows the reports on sample data for now. Connecting your own AWS accounts comes next, and this is how it will work.

  1. Add a read-only role

    You create one IAM role in each AWS account you want to include. It can only read, and it trusts our collector only with an ExternalId that belongs to your company. There is no agent to install.

  2. We collect every hour

    Every hour the collector lists what is running, reads its usage from CloudWatch and prices it from the public AWS price list. If you connect your bill, it reads that once a day.

  3. Read your reports

    Open them in your browser and invite your colleagues. What you see is what the last run stored: opening a page asks nothing of AWS.

What we read and do not read

We read

What runs, and how much it is used.

  • What is running: EC2 instances, EBS volumes, RDS, ElastiCache, DynamoDB tables, EKS clusters, load balancers, NAT gateways and the like, with their sizes, versions and tags.
  • How much it is used: CloudWatch usage metrics.
  • How it is connected: VPCs, subnets, route tables and security groups, and whether buckets, snapshots and images are public.
  • Names and settings, never contents: S3 buckets, secrets, KMS keys, log groups and alarms, as some carry a monthly fee.
  • Your bill, if you choose to connect it, through a read-only role of its own.
  • The AWS price list, which is public and needs no access to your account.

We do not read

What is stored in it. The role denies these outright, so a broader policy attached later still could not open them.

  • Your files in S3
  • Items and rows in your databases
  • Secret values and parameters, and it cannot decrypt with your KMS keys
  • Log events
  • Stream records and queue messages
  • Instance user data, console output and passwords
  • Container images
  • Anything inside your Kubernetes clusters

And it changes nothing. The role holds read calls only. You create it yourself, so you can read every line of its policy first, and deleting it ends our access. Premium's flow logs need a second role, which can only create and delete flow logs tagged for qloudpulse in the VPCs you choose.

Free early access

  • Freeduring early access
  • No cardneeded
  • 30 daysnotice before any charge

Early access is a test. It shows the reports on sample data for now, so it touches nothing in your AWS accounts and adds nothing to your AWS bill.

After early access, qloudpulse is $30 a month per company, or $150 for Premium, with every AWS account included and the first month free. On-prem, in your own Kubernetes cluster, is coming at $300 a month. See what each plan includes.

Support is by email and best effort, and there is no uptime promise during early access.

Anyone can create a login, but during early access a company is opened only for email addresses we have listed. If you would like to try it, or have a question, write to us.

Get in touch support@qloudpulse.com