Predictika · Aerospike editions and pricing model · order forms
An AI agent prepares an order form for an Aerospike database deal, on the Community Edition, the Enterprise Edition or Aerospike Cloud, and states its own billing figures. Before the form is submitted, the agent sends it to Predictika’s validator, which checks it against the edition limits and the pricing structure, recomputes the agent’s figures, and returns a verdict (allow, needs sign-off or block) with every reason at once. The same check works on an order form assembled by a person.
This validator checks an order form for the Aerospike Community Edition, Enterprise Edition or Aerospike Cloud against the structure Aerospike publishes: edition limits, unique-data pricing, feature uplifts and paper type. It handles any order form involving those editions, not just the scenarios shown below.
Aerospike publishes no list prices, so the validator checks structure in TB, nodes and percent and uses no dollar amounts. The discount threshold, the claim tolerance and the example uplift percentages are an example policy (configurable), not Aerospike’s actual policy. The validator does not price the deal or negotiate it; the edition, cluster, data volume, terms and figures come from the order form.
7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Illustrative agent statement. The validator receives the structured request below.
Proposing agent: AI sales agent (scripted)
Before sending, the agent must call Recorded run
What this means
Our assessment of what typical rules-based order automation (product rules, approval workflows and validation rules in a quoting tool) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator caught | Typical rules-based automation | Predictika |
|---|---|---|
| Billable volume is unique data, not raw storage | Only with workarounds A quantity field takes whatever is typed. Dividing stored data by the replication factor needs custom calculation, and nothing compares it with the billed volume. | The unique data is computed from stored data and replication factor, and the billed volume is compared with it. |
| Edition limits on nodes and data | Easy A threshold validation on the edition handles node and data limits. | The same limits, returned with every other finding in one answer. |
| Duplicate lines for the same feature | Only with care Catalogs can hold several SKUs for one feature, so a repeated line passes unless someone is vigilant. | Each feature is counted across the whole form and a second line is blocked. |
| Cloud and self-managed paired correctly | Only with care Product flags can keep a cloud product away from a node count, but pairing edition, hosting and pricing basis takes several rules kept in step. | Edition, hosting, node count and pricing basis are checked together on every call. |
| Paper type against terms and use | Only with care Clause rules can route custom terms to legal, but online MSA, custom MSA, $0 form, support level and production use have to be combined by hand. | Paper, terms, support and use are checked together; custom terms hold for legal approval. |
| Figures the form states itself | Only with workarounds The billable volume and total on a form are usually taken as given unless custom code recomputes them. | Each figure is recomputed from the form and blocks on a mismatch. |
| Every problem returned in one answer | Only with workarounds Rules tend to stop at the first failing check, so reasons surface one resubmission at a time. | All findings come back together, whatever order the choices arrived in. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the order form; sign-off findings need a person; everything else is computed. Thresholds are an example policy (configurable); Aerospike publishes no list prices, so figures are in TB-equivalent units.
| 1 | A Community Edition cluster has at most 8 nodes (blocks) |
| 2 | A Community Edition cluster holds at most 2.5 TB of data (blocks) |
| 3 | An Enterprise Edition cluster has at most 256 nodes (blocks) |
| 4 | Enterprise-only features (cross datacenter replication, Kubernetes Operator, TLS, access control lists, Aerospike Connect integrations) cannot appear on a Community Edition form (blocks) |
| 5 | Billable volume is the unique (non-replicated) data: stored data divided by the replication factor (blocks) |
| 6 | Every line is priced by unique data volume; there is no charge per core, node or operation (blocks) |
| 7 | Additional-licensing features (multi-site clustering, strong consistency, transactions, encryption at rest, compression) are sold as a percentage uplift on Enterprise Edition only (blocks) |
| 8 | Aerospike Cloud includes all features in the service price, so it carries no feature uplift lines (blocks) |
| 9 | Each feature gets a single uplift line; a second line for the same feature is blocked (blocks) |
| 10 | The uplift percent must match the example rate card for the feature (blocks) |
| 11 | Aerospike Cloud is fully managed: no customer node count; Cloud and self-managed editions cannot be paired with the wrong hosting (blocks) |
| 12 | The Community Edition is free: only a $0 order form applies, and no commercial support (blocks) |
| 13 | A $0 order form covers only the Community Edition or non-production use of a paid edition (blocks) |
| 14 | An online MSA is for standard terms only (blocks) |
| 15 | Custom MSA terms need legal approval (needs sign-off) |
| 16 | A discount above the example threshold needs approval (threshold set in the example policy) (needs sign-off) |
| 17 | Unique data, uplifts, billing total and net total are computed from the form (computed) |
| 18 | The billable volume and billing total the form states must match the validator figures (blocks) |
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. Submitting the order form for Larkspur Payments: Enterprise Edition on an online MSA, 24 nodes, 96 TB billed, with strong consistency and transactions, priced per node, 10 percent discount. The billing total is 120 TB-equivalent.
Verdict: Blocked.
The agent's request. Submitting the order form for Larkspur Payments: Enterprise Edition on an online MSA, 24 nodes, 48 TB billed, with strong consistency and transactions, priced by data volume, 10 percent discount. The billing total is 60 TB-equivalent.
Verdict: Allowed.
The agent's request. Submitting the order form for Harborview Insurance on the online MSA: Enterprise Edition, 12 nodes, 30 TB stored at replication factor 2, with 2 custom clauses and an encryption at rest uplift, 10 percent discount. The billable volume is 15 TB and the billing total 16.5 TB-equivalent.
Verdict: Blocked.
The agent's request. Submitting the order form for Harborview Insurance on a custom MSA: Enterprise Edition, 12 nodes, 30 TB stored at replication factor 2, with 2 custom clauses and one encryption at rest uplift, 10 percent discount. The billable volume is 15 TB and the billing total 16.5 TB-equivalent.
Verdict: Needs approval.
The agent's request. Setting up a free Community Edition cluster for Pinecrest Labs: 10 nodes, 6 TB stored at replication factor 2, TLS enabled, on a $0 order form with community support.
Verdict: Blocked.
The agent's request. Setting up a free Community Edition cluster for Pinecrest Labs: 6 nodes, 4 TB stored at replication factor 2, on a $0 order form with community support.
Verdict: Allowed.
The agent's request. Submitting the order form for Cobalt Streaming on Aerospike Cloud: 60 TB stored at replication factor 3, 12 nodes, priced per core, with a compression uplift, 15 percent discount. The billable volume is 20 TB and the billing total 22 TB-equivalent.
Verdict: Blocked.
The text of the narrated walkthrough, step by step.