Engineering
How we cut p99 quote latency by 38% without changing the algorithm
A long look at the Caffeine + Redis ratesheet cache, the Bucket4j hot-path, and the OpenTelemetry traces that found two redundant deserializations.
Updates from RateStack
Subscribe to the things you actually want to read.
No firehose, no growth-hacked drip campaign. Pick your topics, pick your cadence, and skip the rest. Your inbox will thank you.
What subscribing gets you
Just-enough emails, written by the people building this.
Choose what you hear about
Six topic streams. Subscribe to one, all, or anything in between. Toggle anytime — your preferences ride on each email.
Choose how often
Weekly for engineers shipping integrations. Monthly for everyone else. Quarterly summaries or material-only — your call.
Privacy by default
First-party only. No marketing-automation pixels, no third-party trackers in the email body. We respect Do-Not-Track and Global Privacy Control.
One-click unsubscribe
Every email has a one-click unsubscribe link. No retention policy theater — clicking it removes you within 24 hours.
Existing customers automatically get security advisories regardless of cadence — those are critical and not optional.
What past issues looked like
Examples of recent topics.
A representative cross-section. Subscribers got these in their inbox; everyone gets them on the blog.
Market commentary
Bid-tape variance is up 30 bps month-over-month
What we're seeing in the secondary feeds: variance, dispersion, and what it means for hedge desks pricing into the next FOMC.
Compliance
ECOA-aligned pricing audits, end to end
How the per-rule trace, hash-chained audit log, and historical replay combine into an auditor-defensible packet — with the SQL queries to extract it.
Frequently asked
Subscription questions, answered.
Can I unsubscribe anytime?
Yes. Every email has a one-click unsubscribe link in the footer. We honor unsubscribes within 24 hours and confirm in writing.
Will you sell or share my email?
Never. Your email stays inside RateStack and the email-delivery vendor we name in the subprocessor list. We do not run paid lookalike audiences off our subscriber list.
How is this different from the in-product changelog feed?
The in-product changelog and the /changelog feed are exhaustive — every shipped change. The newsletter editorializes: what matters, why, and what to do about it. Subscribing to product-updates gives you the editorialized view, not a firehose.
Do you do double opt-in?
If your operator has wired NEWSLETTER_FORWARD_URL to a double-opt-in provider (Mailchimp, ConvertKit, HubSpot, etc.), you'll get a confirmation email. If not, we record your consent timestamp and source IP in the audit log — that's the source of truth.
Where can I read past issues?
Newsletter archives ship in the public blog with the same content. Subscribing just gets you a notification when a new piece lands; nothing exclusive.
What if I'm a customer — should I still subscribe?
Yes. Customers get product updates through the in-app changelog and quarterly business reviews; the newsletter is the channel for market notes, engineering deep-dives, security advisories, and event invites that don't fit those surfaces.