Changelog & status

What we just shipped.

Released, deployed, sealed.

Status

All systems nominal.

Every Garden service is read live from status.gardens.ml — uptime, p50 latency, and last deploy.

bean
operational
chard
operational
cabbage
operational
kale
operational
greenhouse
operational
turnip
operational
sage
operational
branches
operational
vine
operational
celery
operational
figs
operational
basil
operational
m
mcp
operational
w
webhooks
operational
Releases

What just shipped, by issue.

Spring · Issue 04

Bean closes the period.

  • ·Bean — period close with cryptographic seal
  • ·Cabbage — invoice document engine (PDF, HTML, JSON)
  • ·Greenhouse — FROST threshold signing live across supported chains
  • ·Garden Desktop — signed builds for macOS, Windows, Linux
Spring · Issue 03

Sage screens the world.

  • ·Global sanctions screening across OFAC, EU consolidated, UN, UK, and 30+ regional lists
  • ·Travel Rule message exchange for Greenhouse outbound transfers
  • ·Continuous adverse-media monitoring with delta alerts
Winter · Issue 02

Branches reaches the banks directly.

  • ·Direct ISO 20022 connectivity for institutional banks
  • ·BAI2, MT940, and Swift MT103 statement ingestion
  • ·Authoritative balance reconciliation with Bean's cash accounts
Winter · Issue 01

Vine arrives, exactly once.

  • ·Outbox-backed event delivery with strict per-tenant ordering
  • ·90-day replay window across every Garden event
  • ·Dead-letter queue with admin replay tooling
Stay informed

Subscribe to the seasons.

One long-form letter per release on what we built, why we built it that way, and what we learned from operators who run money on Garden.

Open GardenStream the event spine