Notes

From the team

Short writeups on how SpiceGrinder thinks about domain modeling, security, and reproducibility — straight from the people building it. Looking for reference material? That lives in Docs.

• Cheap Hardware Works Great

  We already knew SpiceGrinder's engine runs on modest hardware — the benchmarks page has the numbers across six real AWS instance types, from the smallest…

• Complexity

  We recently published real benchmark numbers for SpiceGrinder. While running and analyzing our benchmarks, we ran into a small surprise: our own complexity…

• For Ops: Monitoring SpiceGrinder

  If your team runs SpiceGrinder across more than a couple of workstations — or in CI, or as a service — you've probably already asked the questions Ops always…

• Intro to SpiceGrinder

  If you work with health records, financial transactions, insurance claims, or anything else regulated, you know the problem: you need volume test data, but…

• Models As Code

  Infrastructure as code changed how teams manage servers, networks, and deployments.

• The Free Workaround We Missed

  Vital Signs 2 makes a claim we need to correct: that a plain Mix can't reliably produce a run of consecutive anomalous readings — only Perturb, a Pro-tier…

• Why Do We have a Free Tier?

  Most "free tiers" in this industry aren't free tiers. They're trials wearing a free tier's name — capped at 14 days, or throttled just enough to be annoying,…

• You Probably Need Fewer Runtime Licenses Than You Think

  Unless you're a one-person shop, if you're evaluating SpiceGrinder for real production use, you'll eventually hit this question: how many runtime instances do…