Dated, user-visible changes to the hosted service — pricing, metered billing, the platform, and eventually GA itself. The self-hosted engine has its own CHANGELOG.md in the repository; this one tracks the Cloud product specifically.
Up to now, tracking what changed about Hopskip Cloud meant diffing the pricing page by hand. This page is the fix: one dated entry per user-visible change to the hosted product (pricing, billing, the console, and eventually GA itself), kept separate from the engine’s own changelog, which tracks the self-hosted core.
Subscribe instead of checking back: Atom or RSS, whichever your reader prefers.
Publishing a rate card is easy; metering honestly is the hard part. Now, every billable event (workflow starts, activity dispatches and completions, signals, timers fired) is classified from an explicit table and committed to the same hash-chained, Merkle-committed log the engine already keeps for its own history. An event type the table doesn’t recognize is never billed, by construction.
This is what makes the pricing page’s boldest claim true rather than aspirational: a customer can count their own Actions, in the console or in SQL, and verify the count against published partition roots. A billing dispute resolves with an inclusion proof, not a support-ticket standoff.
Still early access, and still pre-invoice: the ledger exists and is correct, but nothing is charging a card yet.
The usage ledger records every billable event and can export JSONL “for ingestion by an external billing system”, but nothing did the ingesting, so the path from “we counted it” to “they were invoiced” still ran through a person and a spreadsheet.
The new hopskip-billing sidecar closes that gap: a scheduled process
that reads the
usage ledger, resolves each namespace to an account through Cloud’s
Postgres control plane, and reports usage to Stripe. The Stripe credential
lives in its own process, isolated from the engine by the dependency
graph, not just by convention. This crate is Cloud-only; self-hosted
builds never link it, and never need to.
The pipe now runs end to end. What’s still ahead of GA: the first invoice running through it for real, and the multi-tenant hardening review the pricing page already says hasn’t happened yet.
Hopskip Cloud moves from “deferred” to planned. The pricing page now publishes every meter’s intended GA rate (Actions, pooled compute, hot/cold storage, egress) instead of hiding them behind a call. Nothing is invoiced yet; there’s no service to invoice for. What’s real today is the number itself and the reasoning behind it.
The waitlist is open. Early-access customers who show up now get a 12-month rate lock at GA in exchange for the risk of showing up early: rates may still move before then, and no SLA or compliance certification is claimed before it’s real.
The full rationale, including why Cloud is consumption-priced where self-hosted isn’t, is on the pricing page.