The Critter Stack's Patching API lets you modify persisted JSON documents in place -- no deserialize, mutate, re-serialize round trip. Here's the shared API across Marten, Polecat, and Fisher, what each database does underneath, and where the three genuinely differ.
CritterWatch 1.0 is watching your system for unusual conditions and trying to explain the cause and effect of anything that's going wrong.
The mechanical half of an NServiceBus migration goes fine unaided. The part that goes wrong is the decision NServiceBus used to make for you -- how each endpoint listens. Here's the same question asked twice, once with the JasperFx AI Skills installed and once without.
NServiceBus and MassTransit have both shipped welcome improvements to their message handler ergonomics. Let's give credit where it's due, then walk through why Wolverine's approach to low ceremony code — no mandatory anything, inlined dependencies, pure function handlers, cascading messages, and readable generated code — is still in a class of its own.
CritterWatch 1.0 is here — a monitoring and production-management console purpose-built for Wolverine, Marten, Polecat, and Fisher. It renders the system you actually shipped from the running code, steps through projections event by event, lets you replay dead letters and rebuild projections without a redeploy, and hands your AI agent a real, RBAC-gated control surface.
Sixty-three releases in sixteen days across Marten, Wolverine, Polecat, Fisher, Weasel, and the shared JasperFx libraries. Fisher brings event sourcing and document storage to SQLite with no server at all, the shared contracts wave means the same Wolverine handler now runs on PostgreSQL, SQL Server, or SQLite without naming a store, and a projection loader bug that silently skipped events makes this an upgrade you should not sit on.
We've run Critter Stack workshops for several teams now, and no two have been the same. One went deep on asynchronous messaging, another on Wolverine's HTTP endpoint and message handler hybrids, a third on using Marten projections to build denormalized views for reporting screens. The material is built and ready — what it turns into depends on what your team actually needs.
Most event sourcing stacks make eventual consistency mandatory: events in one database, read models in another, and a subscription in between. Marten and Polecat keep events and read models in one database, which unlocks a dial no one else offers — projections snapshotted in the same transaction as the events, FetchLatest reads that are accurate even with async projections, wait-for-non-stale queries, and test automation that makes asynchronous projections actually testable.
Every serious event sourced system eventually needs to answer 'what caused this event, and who did it?' The Critter Stack establishes correlation, causation, saga, user, and tenant metadata on Wolverine message envelopes — seeded straight from OpenTelemetry activities — then relays all of it onto the events Marten and Polecat store, with storage you can dial from lean to rich.
Real systems rarely get to standardize on one message broker. Wolverine lets a single application speak Rabbit MQ, Azure Service Bus, Kafka, and MQTT at once — and takes it one step further with a broker-per-tenant model where the tenant id is inferred from the connection a message arrived on and carried all the way into the database transaction.
Seven days, twenty-two releases across Marten, Wolverine, Polecat, Weasel, and JasperFx: a PostgreSQL injection fix under sharded tenancy, two silent data-loss bugs in Wolverine, self-managing time-series partitions, and a big wave of production hardening for projection agent distribution.
Critter Stack services can add, disable, and remove tenants at runtime — new databases and all. CritterWatch turns that capability into an operator console: a tenant lifecycle you can drive from a browser, and performance metrics broken down per tenant id.
The first release candidate for CritterWatch 1.0 — a purpose-built monitoring and operations console for the Critter Stack that shows you the system you actually shipped, watches it for you, hands your AI assistant a real control surface, and gives you a proper cockpit for the event store.
Recent Marten work widens what your LINQ Where/Select expressions translate into PostgreSQL SQL and JSONPath -- so more of your query runs in the database instead of falling back to slower client-side evaluation.
A deep look at the recent hardening of Marten's async projection high water detection -- why an in-flight transaction gap is dangerous, and how transaction evidence keeps projections from ever silently skipping an event.
Mature open-source infrastructure isn't about splashy features -- it's about compounding reliability and measured performance work. Here's how the Critter Stack keeps getting faster and more correct underneath you.
Strict message ordering usually means single-threaded consumers, distributed locks, or a lot of hand-rolled bookkeeping. Wolverine's global partitioning and re-sequencer give you ordered processing across a cluster while still scaling out — no explicit locking required.
CritterWatch 1.0.0-alpha.1 is loose on NuGet — a monitoring and production-management console for Wolverine, Marten, and Polecat that doubles as dev-time insight and an MCP control surface for your AI agents.
Polecat is an event store and lightweight document database for .NET, backed by SQL Server 2025. It brings the proven Marten development model — same IDocumentStore API, projections, and async daemon — to SQL Server shops without a database migration.
The .NET community keeps relitigating Result types vs. exceptions for error handling. With Wolverine you mostly get to opt out of that whole debate — let the framework handle the 404s, the 400s, and the OpenAPI metadata while your code stays clean of both Result wrappers and exception-as-control-flow.
CritterWatch 0.8.0 is the largest release yet — a purpose-built monitoring and operations console for the Critter Stack with production observability, development-time insight, and an MCP control surface built for AI agents.
Why the Critter Stack and Wolverine are the best foundation for vertical slice architecture in the age of AI coding agents — aggressive code compression, locality of reference, and conventions encoded in AI skill files.
Wolverine, the low-ceremony .NET application framework for asynchronous messaging, HTTP endpoints, and CQRS, just passed five million NuGet downloads — with a million in the last six weeks alone.
The Critter Stack 2026 releases have landed: faster cold starts, AOT compliance, better Serverless support, and new greenfield defaults across Marten, Polecat, and Wolverine.
JasperFx Software's officially curated AI Skills for the Critter Stack are now available for purchase — continuously improved guidance that helps AI coding agents write idiomatic Marten, Polecat, and Wolverine code.
Wolverine.HTTP is a first-class HTTP framework for ASP.NET Core built for vertical slice architecture — low ceremony, no Mediator library, built-in transactional outbox, and middleware more powerful than IEndpointFilter.
Wolverine has a strong development and production-time story for EF Core developers — transactional middleware, automatic outbox/inbox, runtime database migrations, test data resets, and declarative persistence.
How to build the most efficient possible HTTP query endpoints in .NET by streaming JSON straight from PostgreSQL with Marten — using Marten.AspNetCore's WriteArray and compiled queries with zero C# allocation.
Polecat is a new JasperFx library that brings Marten's proven Event Sourcing and document database model to SQL Server 2025 — the best technical option for Event Sourcing with SQL Server in .NET.
