Can we buy a managed Postgres time-series database through AWS Marketplace, and how does billing work with our AWS commit?

Most teams that are already standardized on AWS want a managed Postgres time-series database they can buy the “AWS way”: via AWS Marketplace, on their existing commit, with one consolidated bill. With TigerData’s Tiger Cloud, you can do exactly that—and still get full Postgres + TimescaleDB capabilities for time-series, events, and telemetry data.

Quick Answer: Yes, you can purchase Tiger Cloud (managed Postgres with TimescaleDB) through AWS Marketplace. Usage is metered and billed through your existing AWS account, and you can run it either pay-as-you-go or against an annual AWS/Tiger Cloud commit for predictable spend.

---

The Quick Overview

• What It Is: Tiger Cloud is a fully managed PostgreSQL service with the TimescaleDB extension, purpose-built for time-series and telemetry workloads (metrics, events, ticks) and available directly through AWS Marketplace.
• Who It Is For: Teams running on AWS that want Postgres for high-ingest telemetry data—without stitching together Kafka, Flink, and custom pipelines or managing Postgres internals themselves.
• Core Problem Solved: It gives you a managed, Postgres-native time-series database you can buy via AWS Marketplace, with transparent consumption-based billing that fits into your existing AWS commit and procurement process.

---

How It Works

At a high level, Tiger Cloud gives you a managed Postgres cluster with TimescaleDB, deployed into AWS and billed via AWS Marketplace. You keep SQL as your interface; TigerData handles partitioning, storage layout, compression, HA, and backups; AWS Marketplace handles the billing.

Under the hood:

1. You subscribe via AWS Marketplace:
   Choose Tiger Cloud from AWS Marketplace, connect it to your AWS account, and pick a pricing option—pay-as-you-go or annual commit.

2. You run Postgres + TimescaleDB for telemetry:
   Spin up services from Tiger Console, connect with standard Postgres drivers, and use TimescaleDB primitives (hypertables, compression, continuous aggregates) to handle time-based workloads.

3. Your usage is metered and billed through AWS:
   Tiger Cloud usage is measured over the month and sent to AWS for billing. You avoid per-query and per-request fees—compute, storage, and options are itemized, and charges appear on your AWS invoice, aligned with your AWS commit.

---

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
Managed Postgres + TimescaleDB on AWS	Runs Postgres with TimescaleDB as a fully managed service on AWS infrastructure, reachable via standard Postgres protocols.	Use a Postgres-native time-series database on AWS without managing clusters, upgrades, or ops.
AWS Marketplace integration	Lets you buy Tiger Cloud directly from AWS Marketplace, with charges routed to your AWS account.	Aligns database spend with your existing AWS commit and procurement workflows—no separate vendor billing system to manage.
Consumption-based pricing (no per-query fees)	Meters compute and storage usage monthly; you don’t pay for individual queries or data access.	Predictable, transparent pricing that scales with your actual usage, without worrying about query spikes or hidden I/O fees.

---

Ideal Use Cases

• Best for teams consolidating on AWS:
  Because it lets you standardize on Postgres for telemetry workloads and still keep all spend under your AWS account and commit, including Tiger Cloud charges via AWS Marketplace.

• Best for high-ingest telemetry and time-series on Postgres:
  Because it combines Postgres reliability with TimescaleDB’s hypertables, compression, and continuous aggregates, so you can ingest large volumes of metrics/events while keeping both real-time and historical queries fast—without building fragile, multi-system pipelines.

---

Limitations & Considerations

• You’re on AWS billing rails:
  This is usually a benefit, but it means your Tiger Cloud costs follow AWS Marketplace timelines and invoicing cycles. Important if your finance team expects separate, non-AWS invoices or custom payment terms.

• Commit structure matters:
  With an annual commit, usage is calculated monthly against the agreed terms. Plan ahead with TigerData sales to size a commit that fits your projected ingest, retention, and compute needs—over- or under-committing will affect your effective rate.

---

Pricing & Plans

Tiger Cloud on AWS Marketplace uses disaggregated, consumption-based pricing. You pay for the underlying resources you actually consume (compute, storage, options) with:

• No per-query fees
• No additional costs just to read or write data
• Transparent, itemized usage calculated at the end of the month

From AWS Marketplace you generally choose between two models:

• Pay-as-you-go:
  Your Tiger Cloud consumption is measured over the month and added directly to your AWS invoice at standard Tiger Cloud rates. No upfront commitment; ideal if you’re still sizing your workload or expect spiky traffic.

• Annual commit:
  You and TigerData agree on annual terms up front. Your actual usage is still calculated monthly, but it’s reconciled against that commitment, giving you predictable pricing and often better effective rates. Billing still flows through AWS, so finance sees a single vendor: AWS.

In both cases:

• TigerData confirms contract terms with you before finalizing an annual commit.
• Using self-hosted TimescaleDB and TigerData’s open-source components remains free if you eventually want to run TimescaleDB on your own Postgres installation instead of Tiger Cloud.

---

Frequently Asked Questions

Can we run Tiger Cloud entirely under our existing AWS commit?

Short Answer: Yes. When purchased through AWS Marketplace, Tiger Cloud usage is billed through your AWS account and can be aligned with your AWS commit.

Details:
Once you subscribe to Tiger Cloud via AWS Marketplace, all Tiger Cloud charges flow through AWS. For pay-as-you-go, your end-of-month usage is simply added to your AWS invoice at published rates. For annual commitments, TigerData works with you to define contract terms, and your monthly usage is applied to that committed amount. In both cases, the spend shows up as AWS Marketplace line items—your procurement and finance teams treat it as part of your AWS footprint, helping you utilize existing AWS commits.

---

How is Tiger Cloud usage calculated, and are there any hidden fees?

Short Answer: Usage is calculated at the end of each month based on your actual consumption—there are no per-query fees or extra charges for data ingest/egress beyond standard AWS networking.

Details:
Tiger Cloud uses a disaggregated, consumption-based model:

• Compute and storage are metered independently.
• Automated backups and operational overhead are included—you don’t pay extra “backup taxes.”
• There are no per-query, per-metric, or per-request charges; running more analytics doesn’t unexpectedly spike your bill.

When you buy through AWS Marketplace, this metering rolls up into a monthly usage record that AWS adds to your invoice. That makes costs “boring and predictable”: you see clearly what you used, at what rate, with no surprise performance or query-based surcharges layered on top.

---

Summary

If you’re asking whether you can get a managed Postgres time-series database through AWS Marketplace, the answer with Tiger Cloud is yes—and it works the way AWS-native teams expect. You get Postgres with TimescaleDB for high-ingest telemetry workloads, managed by TigerData, while all billing runs through AWS Marketplace, either pay-as-you-go or against an annual commit.

You keep SQL, you avoid fragile multi-system pipelines, and you keep your procurement and finance story simple: one cloud, one invoice, with transparent, consumption-based pricing and no per-query surprises.

---

Next Step

Get Started