A running log of platform improvements. Newest first.
The changelog is the record of what actually shipped, with enough technical detail that an engineering team or a procurement reviewer can verify it. Each entry covers a coherent batch of work (compliance, billing, free-tier scope, security hardening, analytics, UX) rather than individual commits. Items are written in the past tense and describe behavior the user can verify in the dashboard or via a curl test.
We keep the changelog public because the platform is sold to brands, retailers and printers who need to verify what they're paying for. Compliance teams can cross-check that the cookie banner, GDPR controls and data-residency posture match what the security and privacy pages claim. Engineering teams can confirm that the rate limits, magic-byte upload validation and webhook idempotency are real, shipped behavior rather than aspirational marketing copy. Product teams can see what's been added recently before signing up.
Roadmap items deliberately don't appear here. The changelog is a record of shipped work, not a list of intentions. When something ships, it lands in the changelog within the same business day, with a tag that lets readers filter by area: compliance, pricing, free-tier, forms, analytics, security, UX. New entries are added in reverse-chronological order at the top.