38 min read

What "Transparent Pricing" Actually Means on Singdata's AWS Marketplace Listing

An operational look at Singdata Lakehouse pricing on AWS Marketplace: the published CRU, storage and transfer rates, what the listing leaves open, how software charges differ from AWS infrastructure costs, and a procurement checklist for validating TCO claims.

What "Transparent Pricing" Actually Means on Singdata's AWS Marketplace Listing

The Singdata Lakehouse listing on AWS Marketplace publishes unit rates, contract durations, a free trial and a starter tier. That is more than many listings disclose, and it is still not the same thing as knowing what the platform will cost you. A lakehouse bill is a composite: a software charge metered in compute resource units, storage and outbound transfer, plus the AWS infrastructure the deployment runs on, plus whatever terms you negotiate privately. This article sets out an operational definition of transparency, walks through what the listing actually states, and gives procurement a checklist and a validation method. Scope: the Singdata listing and AWS Marketplace buyer and seller documentation as of November 2026. Singdata's performance and TCO figures are treated throughout as vendor-reported claims to be tested, not as established results.

Defining transparent pricing operationally

A working definition: pricing is transparent to the extent that the fields governing your bill are inspectable before you sign. Four categories carry most of the weight — the metering dimensions and their unit rates, any included allowance or free tier, the contract duration and renewal behavior, and the EULA plus cancellation mechanics. On the Singdata listing, the first three are published: compute per CRU hour at two edition rates, storage per GiB per month, transfer per GiB with a monthly outbound allowance, and 1-month and 12-month contract options. The fourth is partly published — the listing links the vendor EULA and states "cancel anytime" — but the refund consequences sit in AWS documentation rather than the listing.

The other side of the line is what AWS calls a private offer: negotiated pricing and EULA terms that, in AWS's words, "aren't publicly available." Volume discounts, committed-use terms, custom EULA amendments and payment schedules belong there. Transparency does not require that these be public. It requires that you know which bucket a given question falls into, so a missing answer on the listing is not mistaken for a hidden one — and a published rate is not mistaken for a total.

What the Singdata listing discloses before you sign

The listing's pricing table defines three ongoing dimensions plus a trial. Compute is billed at 1.86 USD per CRU hour for the Enterprise edition and 1.24 USD per CRU hour for Standard, and applies to all virtual clusters and ingestion jobs. Storage is billed at 0.025 USD per GiB per month "beyond any included allowance." Data transfer includes 30 GiB of outbound internet traffic per month at 0.12 USD per GiB beyond that. The Starter Package gives 30 days of full platform access for $1, and a 14-day free trial covers basic features with community support. The listing states that prepaid credits transition to pay-as-you-go billing based on actual consumption, with no minimums, and points to Singdata's own pricing page for detail.

Singdata Lakehouse published software unit rates (USD) Horizontal bar chart of the four published per-unit software rates: Enterprise compute at 1.86 USD per CRU hour, Standard compute at 1.24 USD per CRU hour, storage at 0.025 USD per GiB per month beyond any included allowance, and outbound internet transfer at 0.12 USD per GiB beyond the 30 GiB monthly allowance. Units differ across dimensions, so bars compare rate magnitudes only, not total cost. Singdata Lakehouse published software unit rates (USD). horizontal bar data: Compute — Enterprise (USD per CRU hour) 1.86; Compute — Standard (USD per CRU hour) 1.24; Outbound transfer (USD per GiB beyond 30 GiB/month) 0.12; Storage (USD per GiB per month beyond allowance) 0.025.Source: Singdata Lakehouse — AWS Marketplace listing Accessed 2026-11-12. Singdata Lakehouse publishedsoftware unit rates (USD) Compute —Enterprise (USDper CRU hour) 1.86 Compute —Standard (USDper CRU hour) 1.24 Outboundtransfer (USDper GiB beyond... 0.12 Storage (USD perGiB per monthbeyond... 0.025 Source: Singdata Lakehouse — AWS Marketplacelisting (Accessed 2026-11-12)

Published unit rates from the Singdata Lakehouse AWS Marketplace listing, accessed 12 November 2026. These are per-unit software charges only; they exclude the separate AWS infrastructure bill and any negotiated private-offer terms. The listing does not state the size of the included storage allowance, so the point at which the $0.025/GiB-month rate begins is not determinable from the listing alone.

Two silences matter for budgeting. The listing does not state the size of the storage allowance, so the point at which the 0.025 USD rate begins to apply is not determinable from the listing alone. And the pricing table's "Cost/month" column shows $1.00 against Compute, Storage and Data Transfer alike — a display artifact, not a monthly cap; the per-unit rates in the description column are the operative figures. Confirm both points in writing before you model anything.

Why the Marketplace line item is not your total bill

AWS Marketplace charges for software appear on your AWS bill, and AWS pays the seller from that. Infrastructure is separate: AWS's buyer documentation states you also receive a bill for usage of infrastructure services such as Amazon Elastic Compute Cloud, and the Singdata listing carries the standard line that additional AWS infrastructure costs may apply, directing buyers to the AWS Pricing Calculator. A lakehouse estimate therefore has two layers. The software layer is CRU hours × edition rate, plus GiB-months of storage above the allowance, plus outbound GiB above 30. The infrastructure layer is whatever the deployment path consumes — compute instances or clusters, object storage, and the data-transfer charges AWS applies to egress and cross-AZ traffic.

Because the two layers are metered by different parties on different dimensions, the software line item alone understates total cost of ownership, and the size of the gap depends on architecture choices the listing cannot see. Build the infrastructure estimate from your own deployment design in the Pricing Calculator, then add the software layer. Tag the resources so the two can be reconciled after the first invoice; AWS cost allocation tags group resource costs by business category once activated, and tags can take up to 24 hours to appear in the Billing console.

A pricing-transparency checklist for procurement

Organize the work by where each answer comes from, and keep the buckets separate.

From the listing. Unit rates for both editions; the metering dimensions and what each covers; the 30 GiB monthly outbound allowance; the trial and starter terms; the 1-month and 12-month contract options; the linked EULA; the cancellation path for your agreement type.

From the vendor, in writing. The size of the included storage allowance; volume discount thresholds and how they are triggered; committed-use terms and what happens at expiry; overage treatment above any contract quantity; metering cadence and the dispute process if a metering record looks wrong; renewal pricing.

From your own workload model. CRU-hour consumption across clusters and ingestion jobs at expected concurrency; storage growth per month including replicas and snapshots; egress patterns, especially anything leaving the region or the cloud. Run each as a low, expected and high case, and state which assumptions the vendor must confirm.

Questions to ask the vendor — and which ones the listing already answers

The listing answers more than buyers expect: the two edition rates, the fact that storage and transfer are billed identically regardless of edition, the 30 GiB outbound allowance, the $1 starter month, the 14-day trial, and the existence of 1-month and 12-month contracts. It does not answer the storage allowance size, discount structure, custom EULA amendments, payment schedules or renewal pricing — those require a private offer, which AWS describes as negotiated pricing and terms the seller creates for a designated account.

Four red flags are worth naming. A rate published without a stated allowance, so the threshold is unknowable. "Cancel anytime" presented without the refund caveats AWS documents — cancellation stops future charges but does not automatically refund issued invoices. Performance or TCO figures offered without a validation path. And pricing detail that exists only in a sales conversation with nothing in writing. The first two are present in some form on this listing and should be resolved in writing; the last two are tests to apply to any vendor.

Exit cost and lock-in under a Marketplace contract

AWS documents three cancellation routes. Pay-as-you-go subscriptions, public or private, can be cancelled self-service in the console at any time. Public offers with contract pricing have no self-service path; within 48 hours of purchase, AWS Customer Service can cancel and process a full refund without seller involvement. All other cases — public contracts after 48 hours, and private contracts — are seller-initiated: the seller requests cancellation and you approve or deny it. In every case, cancelling stops future charges but does not automatically refund invoices already issued; for usage-based subscriptions you remain responsible for usage already incurred.

Exit cost is wider than the cancellation button. Data egress charges apply when you move data out, and migration effort is real regardless of contract terms. The listing's "open architecture" and lock-in-avoidance positioning is a vendor claim; test it by confirming that your data lands in open table formats you can read with other engines before you commit volume to the platform.

Validating vendor performance and TCO claims before you commit

Singdata's published claims — up to 4x faster than Snowflake, 10x faster than Spark, 50% lower TCO — are vendor-reported and should be validated in your environment. A workable method: define the workload and the baseline you are comparing against; run a bounded pilot on representative data rather than a synthetic benchmark; measure the same quantities the vendor claims, on the same units and the same concurrency; then reconcile the software line item against the full infrastructure bill for the pilot period. If the claim is a cost ratio, the denominator must include both layers described above, or the comparison is not like for like.

The trial and the $1 starter month exist to make this possible before committed spend. Treat the pilot's measured CRU hours and storage growth as the input to your production model, replacing the vendor's assumptions with your own.

How Marketplace procurement changes the review path

Marketplace shortens the administrative path: charges consolidate onto the AWS bill, existing payment and purchase-order processes apply, and standardized contracts such as the SCMP need legal review once rather than per purchase. What it does not change is who you are contracting with. AWS states plainly that it is not a party to the agreements governing software use; the seller remains the counterparty, and the EULA, refund terms and any private offer terms carry the same weight they would in a direct purchase.

Carry this acceptance checklist into the procurement conversation: unit rates and dimensions confirmed against the listing; storage allowance size confirmed in writing; both contract durations priced; infrastructure estimate built in the Pricing Calculator from your deployment design; EULA reviewed; cancellation route and refund position identified for your agreement type; pilot results reconciled against the vendor's claims; and every negotiated term captured in a private offer rather than an email.

FAQ

Can I see all Singdata pricing without contacting sales? No. The listing publishes compute, storage and transfer rates, the trial and the starter tier, but volume discounts and enterprise contracts require contact with the vendor, and negotiated terms arrive as a private offer.

What does a CRU cover? A compute resource unit measures processing capacity; compute is metered per CRU hour across all virtual clusters and ingestion jobs, accruing while clusters run and jobs execute. The listing does not publish a conversion between CRU and a specific instance type, so size your model from pilot measurements.

Does cancelling stop my AWS infrastructure bill? No. Cancelling the Marketplace subscription stops software charges; the AWS services the deployment uses are billed separately and continue until you terminate them.

When do I need a private offer? When you want negotiated pricing, committed-use terms, a custom EULA or a payment schedule — anything AWS describes as not publicly available.

Previous posts

https://www.singdata.com/

https://www.singdata.com/company

https://singdata.com/trending/powerbi-date-difference-dax-calculations/