Predictika · cloud infrastructure quotes: compute, databases, storage, egress and commit terms
An AI sales agent prepares a monthly cloud quote for a fictional customer, with the monthly total it expects to charge. Before the quote goes out, the agent sends it to Predictika’s validator, which checks it against compute, database, storage and commit rules, compares the total the agent states with the one it computes, and returns a verdict with every reason.
This validator models quote-time pricing and eligibility for four product lines in the style of Oracle Cloud Infrastructure: Compute, Autonomous Data Warehouse, PostgreSQL and Object Storage. It handles any combination of lines, shapes, license, capacity and commit choices the model supports, not just the scenarios shown below.
It does not cover other cloud services (Kubernetes, Exadata, networking products), other cloud providers, real Oracle prices or contracts, or any real customer.
8 scenarios in workflow pairs · click one to switch
Illustrative agent statement. The validator receives the structured request below.
Before sending, the agent must call
What this means
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ or Revenue Cloud) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator catches | Typical rules-based CPQ | Predictika |
|---|---|---|
| Shape limits that depend on several choices | Only with workarounds OCPU range, memory per OCPU, burstable baseline and preemptible capacity interact per shape, so each shape family tends to need its own set of rules. | Each shape row carries its limits and every check reads them together, in any order the choices arrive. |
| Which shapes can be preemptible or burstable | Only with care A simple flag per shape works, but the combined case (burstable and preemptible) is a separate rule that is easy to miss. | Both flags are evaluated on every line and each failure is returned with its reason. |
| License-dependent database rates | Only with care The bring-your-own-license rate depends on a customer fact held elsewhere; the quote often prices it without checking. | The license field is part of the request, and the rate is blocked when the licenses are not on file. |
| Discount bands tied to the commit | Only with workarounds Discount authority comes from the annual commit amount, so a discount, a commit and the projected usage must be read together. | Allowed discount, commit and usage are computed once and every related check reads the same figures. |
| Line items that add up to the total | Only with workarounds Egress after a free allowance, a negative discount line and a support minimum are easy to get out of step between lines and total. | The same computed figures feed the line items and the total, so they reconcile exactly. |
| The total the agent states | Only with workarounds Comparing a stated total with a computed one means a separate rule per quote layout, and price rules rarely run on stated figures. | The stated monthly total is a field in the request and is checked against the computed total. |
| Every problem returned in one answer | Only with workarounds Rules tend to fire as the quote is saved, so a rep often fixes one error and meets the next. | All findings come back together, whatever order the choices arrived in. |
Every rule is checked on every call, in whatever order the choices arrive, and one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.
| Rule | Effect | What it checks |
|---|---|---|
| 1 | block | Each compute shape has an OCPU range and a memory range (1 to 64 GB per OCPU, and a per-shape maximum) |
| 2 | block | GPU and bare-metal shapes cannot run as preemptible capacity; preemptible instances are billed at half the on-demand rate |
| 3 | block | A burstable baseline (50 or 12.5 percent) is allowed only on the Standard3, E4 and E5 flex shapes, and a burstable instance cannot also be preemptible |
| 4 | block | Autonomous Data Warehouse needs at least 2 ECPUs and storage from 1 TB in 1 TB steps |
| 5 | block | The bring-your-own-license rate needs existing Oracle Database Enterprise Edition licenses on file |
| 6 | note | Auto-scaling can bill up to 3 times the base ECPUs, so the validator notes the worst-case monthly charge |
| 7 | block, note | PostgreSQL nodes need 1 to 64 GB of memory per OCPU; a single node has no standby, which is noted |
| 8 | note | Object Storage classes have minimum retention periods (Infrequent Access 31 days, Archive 90 days); earlier deletion is billed as if kept to the minimum, which is noted |
| 9 | computed | The first 10 TB a month of internet egress is free; the rest is billed per GB |
| 10 | block | A quote with no service lines is empty and cannot go out |
| 11 | block | Discounts come only with a Universal Credits annual commit: 25 percent from a $250,000 commit and 35 percent from $1,000,000; pay-as-you-go is list price |
| 12 | block | An annual commit needs a commit amount |
| 13 | note | A commit below projected usage, or more than 10 percent above it, is noted with the amounts involved |
| 14 | note | Support Rewards for on-premises Oracle support need an annual commit; pay-as-you-go earns none |
| 15 | computed | Every line is priced from its own rates; line charges, egress, the deal discount and support add up to the monthly total, year-1 total and agreement total |
| 16 | block | The monthly total the agent states must match the validator total within $1 |
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.
The agent's request. A 1-year pay-as-you-go quote for two BM.GPU.H100.8 bare-metal GPU nodes on preemptible capacity, support included. Monthly total $58,400.00. Ready to send.
Verdict: Blocked.
The agent's request. A 1-year pay-as-you-go quote for two BM.GPU.H100.8 bare-metal GPU nodes on on-demand capacity, support included. Monthly total $116,800.00. Ready to send.
Verdict: Allowed.
The agent's request. A 1-year pay-as-you-go quote for one Autonomous Data Warehouse with 16 ECPUs and 10 TB of storage at the bring-your-own-license rate, with auto-scaling on, support included. Monthly total $1,248.75. Ready to send.
Verdict: Blocked.
The agent's request. A 1-year pay-as-you-go quote for one Autonomous Data Warehouse with 16 ECPUs and 10 TB of storage at the bring-your-own-license rate, with the customer's Enterprise Edition licenses on file and auto-scaling on, support included. Monthly total $1,248.75. Ready to send.
Verdict: Allowed.
The agent's request. A 1-year Universal Credits quote with a $1,000,000 annual commit for two BM.GPU.H100.8 nodes on-demand, with a 40 percent deal discount. Monthly total $70,080.00. Ready to send.
Verdict: Blocked.
The agent's request. A 1-year Universal Credits quote with a $1,000,000 annual commit for two BM.GPU.H100.8 nodes on-demand, with a 30 percent deal discount. Monthly total $81,760.00. Ready to send.
Verdict: Allowed.
The agent's request. A 1-year pay-as-you-go quote: six VM.Standard.E5.Flex instances (8 OCPUs and 64 GB each), 20 TB of Object Storage Standard, and 25 TB of outbound transfer a month, support included. Monthly total $2,134.08. Ready to send.
Verdict: Blocked.
The agent's request. A 1-year pay-as-you-go quote: six VM.Standard.E5.Flex instances (8 OCPUs and 64 GB each), 20 TB of Object Storage Standard, and 25 TB of outbound transfer a month, support included. Monthly total $2,264.64. Ready to send.
Verdict: Allowed.
The text of the narrated walkthrough, step by step.