How We Help You Succeed
- ✓Consulting & Architecture
Expert guidance on Event Sourcing, CQRS, and asynchronous messaging to help you build resilient, scalable systems.
- ✓Support Plans
An ongoing relationship with the team behind the Critter Stack - questions, advice, fixes, and event enhancements when you need them.
- ✓Workshops & Training
Interactive, customized 1-2 day online workshops on the Critter Stack, event-driven architectures, and automated testing.
- ✓Battle-Hardened Tools
Proven, well-documented .NET libraries optimized for low-friction development, testability, and AI-assisted workflows.
The Critter Stack at a Glance
One family of .NET tools for event sourcing, document storage, and messaging - on the database you already run.
Latest from the Blog
Release notes, deep dives, and what we learned building the Critter Stack - several posts a week.
10th November 2026Clone n' Go with Stateful Resources and WeaselEvery Critter Stack tool that touches a database knows exactly what that database should look like, and can make it so. This is the basics of how that works: the AutoCreate modes, the Weasel migration engine underneath Marten, Polecat, Fisher and Wolverine, the stateful resource model that puts databases and message brokers behind one interface, and the four ways to get a schema into place from a laptop to a DBA-owned production database.MartenWolverineCritterWatch
9th November 2026Our Plan for the Critter Stack on .NET 11JasperFx 3, Weasel 10, Marten 10, Polecat 6, Fisher 2, Wolverine 7 and CritterWatch 2 are all coming together on .NET 10 and .NET 11, and the headline is not the framework bump. It is the pile of opt-in defaults from the Wolverine 6.x and Marten 9.x lines that finally get to become the defaults, each with a single one-line opt-out. Here is what flips, why, what else is in the train, and how we are running the whole thing as one Stoat plan to dogfood Stoat before its 1.0.WolverineMartenPolecat
8th November 2026Improving Wolverine through Chaos TestingWolverine's durable inbox and outbox promise that a message is handled once even when processes die, databases go away and the network lies to you. Over the last couple of months we have been trying very hard to break that promise, with an out-of-process chaos rig that kills, pauses and starves real Wolverine nodes. Here is how the testing works, the message loss and duplication bugs it found, and what we did about every one of them.WolverineWhat Our Users Are Saying
Critter Stack libraries are some of the most mature libraries I've ever used and their feature set and integration is perfectly tailored for real world problems to solve.
- Alexander Zeitler, PDMLab
The ease of implementing event driven and nosql support is what I value the most. Not having the struggle of making different frameworks play well together to get the same functionality is both time, and therefore, cost saving.
- Daniel Toivonen
I love the simplicity you get in the end. There is a learning curve as you need to unlearn things and change your way of thinking, but in the end you will get very low ceremony code that is easy to reason about. You can read the business intention. The [AggregateHandler] as both a Decider implementation and an example of A-Frame is just beautiful!
- Major Martin, MADIS Consulting Kft
I started small - a bit of Alba for testing, a little Marten for documents, Wolverine as a mediator, and as the complexity of my applications have grown, I've only leaned in more on the Critter Stack. The developer experience of these tools is amongst the best in the industry. My code is better than it has ever been - clearer, easier to reason about, and with the excellent support for event sourcing, I'm amazed how often my customers sheepishly ask for something they anticipate will be challenging, and I actually have to reassure them it won't be - nice change! I never feel backed into a corner with these tools. My code grows and adapts in pace with the businesses I support.
- Jeff Gonzalez, Owner, Hypertheory